Re: mISDN2 supported hardware
Jacek Konieczny <[email protected]>
| Newsgroups | gmane.linux.isdn.i4l.user |
|---|---|
| Message-ID | <[email protected]> |
On Sun, Dec 02, 2012 at 07:59:40PM +0200, Jānis Rukšāns wrote: > On Sun, Dec 2, 2012 at 5:13 PM, Patrick Lists > <[email protected]> wrote: > >> 2. hardware information is discoverable from userspace (Zaptel/DAHDi > >> drivers required hardware settings known and configured before the > >> modules have been loaded). > > > > > > Maybe I misunderstood but I always had to configure both DAHDI (zaptel is > > EOL), Sangoma and mISDN so don't see the advantage. > > > > > >> 3. easy, mostly hardware-independent, configuration (vendor-specific > >> drivers and many DADHDi drivers need special coding for specific device) > > I think Jacek is referring to the fact that for many (if not all) > DAHDI/Zaptel drivers require the configuration to be passed to the > driver when the kernel module is loaded. For one particular PRI card, > I even had to recompile the kernel module each time I wanted to change > it's options. Compared to that, configuring LCR is a walk in a park. That is exactly what I meant. > As for the original question, the list of supported hardware can be > found here: https://www.misdn.eu/wiki/MISDN_v2_Hardware/ I am afraid this list is a bit outdated and those devices may be hard to find these days. > If you have an HFC card that is not recognized, see if you can get it > working and submit a patch (= yeah… I have tried that with OpenVox, but it is hard to do this right without any specification or, at least, readable/well-commented code from the hardware vendor… Greets, Jacek _______________________________________________ isdn4linux mailing list [email protected] https://www.isdn4linux.de/mailman/listinfo/isdn4linux