diff options
| author | Noe Rubinstein <nrubinstein@proformatique.com> | 2010-08-25 16:41:06 +0200 |
|---|---|---|
| committer | Noe Rubinstein <nrubinstein@proformatique.com> | 2010-08-25 16:41:06 +0200 |
| commit | d8654b2409bc80c2e832b49df6e57bcf60d6f052 (patch) | |
| tree | 759186dc7e5fd6dec80db069a52e3917faf38425 /xhfc/TODO | |
| parent | 70c459545852ad454e236a2b21586c53f959e18c (diff) | |
other cosmetic changes
Diffstat (limited to 'xhfc/TODO')
| -rw-r--r-- | xhfc/TODO | 15 |
1 files changed, 3 insertions, 12 deletions
@@ -1,18 +1,9 @@ - the code is a bloody mess, clean it up - XXX & TODO - remove any commented-out code - + keep better track of where everything is allocated and initialized - + is the deinit correct? prolly not! - - harmonize traces -- The alarm should be initialized to DAHDI_ALARM_RED. Redo S/T init/reset code. - the B chan and PCM stuff is not implemented at all - shouldn't part of what is done in the interrupt handler be done later in a tasklet? -- the drivers from which this one was adapted assumed that the D chan was the - last one in the span. For simplicity regarding the configuration of the XHFC, - this driver takes the third chan (which index is therefore 2) of the span as - the D chan. Verify that there is no part of the current code that contradicts - this, and that DAHDI itself doesn't make such assumptions. -- the module relies on the fact that it can't be interrupted by himself to - ensure that there is no sync problem. However, there may be problems in the - user part. Add a (or several) mutex for access to the hardware. +- keep in mind that there is no sync. I think it's not a problem, but in case + a tasklet is used it could become one. + |