Actions
Feature #4923
closedDAHDI driver for icE1usb
Start date:
12/27/2020
Due date:
% Done:
100%
Spec Reference:
Description
I've been hacking up a DAHDI driver for the icE1usb, which is currently available [only] from https://github.com/osmocom/dahdi-linux/tree/laforge/icE1usb
The current code seems to be working fine- it survives manual USB unplug/replug tests
- it survives hundreds of rmmod/insmod cycles
- it causes no CRC errors when used with e1-prbs-test over multiple hours
- no reporting of errors via DAHDI APIs (alarms, crc erorrs, ...)
- no reporting of link status via DAHDI APIs (RED/YELLOW/BLUE/...)
- no control over local/remote clock usage
Checklist
- host repository on osmocom.org
- RED alarm on LOS
- YELLOW alarm
- BLUE alarm
- error counters/stats via DAHDI APIs
- CRC4 enable/disable
- select local/remote clock source via DAHDI
Related issues
Updated by laforge almost 3 years ago
- Status changed from In Progress to Stalled
Updated by laforge almost 2 years ago
- Related to Bug #5379: DAHDI icE1usb locks up if channel type is changed during runtime added
Updated by laforge almost 2 years ago
- Checklist item RED alarm on LOS set to Done
RED alarm reporting merged:
commit aebacd42e5ba4c183d62d54b39884204f5c87052 (HEAD -> laforge/icE1usb, osmocom/master, osmocom/laforge/icE1usb, apu-left/laforge/icE1usb)
Author: Harald Welte <laforge@osmocom.org>
Date: Fri Dec 31 20:17:07 2021 +0100
icE1usb: Support reporting of RED alarm via DAHDI infrastructure
We get loss-of-framing and loss-of-signal notification via USB interrupt
transfers. Let's make use of this information to tell the DAHDI core
[and ultimately the user] about this.
Updated by laforge almost 2 years ago
- Checklist item error counters/stats via DAHDI APIs set to Done
- Checklist item CRC4 enable/disable set to Done
- Checklist item select local/remote clock source via DAHDI set to Done
Updated by laforge almost 2 years ago
commit 9fdd2e534b8de22e0e36076c8577de7be81690bb (HEAD -> laforge/icE1usb, osmocom/master, osmocom/laforge/icE1usb, apu-left/laforge/icE1usb)
Author: Harald Welte <laforge@osmocom.org>
Date: Sat Jan 1 10:22:29 2022 +0100
icE1usb: support for reporting CRC and alignment errors via DAHDI
commit 68cffb3d8f5bbe5871560629943141a0af13d727
Author: Harald Welte <laforge@osmocom.org>
Date: Sat Jan 1 09:49:01 2022 +0100
icE1usb: Support TX configuration (CRC4 on/off, loopback, timing source)
This adds support of configuring the icE1usb TX configuration via the
standard DAHDI mechanisms.
As for YELLOW alarm, there's a WIP patch for the firmware in https://gerrit.osmocom.org/c/osmo-e1-hardware/+/26706.
Updated by laforge almost 2 years ago
- Status changed from Stalled to In Progress
Updated by laforge almost 2 years ago
- Related to Bug #5381: icE1usb DAHDI driver: generate YELLOW alarm towards peer added
Updated by laforge almost 2 years ago
- Related to Bug #5382: icE1usb: detect all-1 pattern and report as BLUE alarm added
Updated by laforge almost 2 years ago
- Checklist item host repository on osmocom.org set to Done
- Checklist item YELLOW alarm set to Done
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
reporting of remote alarms as YELLOW alarm has been added in https://github.com/osmocom/dahdi-linux/commit/7043d45f77ee8fe633e5181f7f7ae22e4e051071
git repo is now [also] at https://git.osmocom.org/dahdi-linux/
remaining issues have been split into #5382 and #5381, so this ticket can be cloed. The DAHDI driver exists and works reliably, AFAICT.
Actions
