Re: mISDN2 supported hardware

Jānis Rukšāns <[email protected]>
Newsgroups gmane.linux.isdn.i4l.user
Message-ID <CABJfmudOwgqyWb1A99BmJ9430oqCfU6qB37fvXmRZZtuGGBZzg@mail.gmail.com>
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.


As for the original question, the list of supported hardware can be
found here: https://www.misdn.eu/wiki/MISDN_v2_Hardware/ In general,
anything based on the HFC chipset should work. Personally I've used
Junghanns duoBRI and ATCOM AX4S. I had to add PCI ID for the duoBRI,
but I don't recommend the ATCOM (in some sense it's one of those "old
devices not available on the market").

If you have an HFC card that is not recognized, see if you can get it
working and submit a patch (=


Cheers,
Jānis

_______________________________________________
isdn4linux mailing list
[email protected]
https://www.isdn4linux.de/mailman/listinfo/isdn4linux
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.