>I tried compiling the 2.2.0-pre4 isdn. I can't do real testing
>yet, as I am waiting for the phone company to change my line to
>an ISDN line, but I saw some problems:
>
>1. The module complained about the device being "in use" when it loaded
> the first time. Could be a setup problem though.
Can't comment on this one, I haven't seen it here. I am using the HiSax
driver with a Teles S0 16/3 card.
>2. The euro-isdn protocol isn't supported. I believe that is the one
> I have to use, the protocol used in Germany works, but it is different.
euro-isdn is supported, it's called HiSax support for EURO/DSS1.
This is probably only for the HiSax driver, but the other drivers
should have support in them for DSS1 as well. Germany has switched to
DSS1 as well, so it ought to work.
>I cannot really see the problem with accepting a huge patch for
>the ISDN stuff, even this late before 2.2.0. It can't do worse than
>break ISDN, and that is broken already for me. Those who don't
>use ISDN won't notice, those who use ISDN want the new stuff and
>it is apparently well-tested too.
I can actually live with waiting for 2.2.1 to get the cvs version
in the kernel. The current support works for me, and it is quite
trivial to get the cvs isdn tree if that might be needed.
Bas Vermeulen
-- When I shop for hardware I always look for the "Designed for Windows 95" logo. I really thank Microsoft(TM) for encouraging manufacturers to label their products this way, so I know what to AVOID.I stick to quality software:
Linux 2.0.36 | IBM OS/2 Warp (TM) v4.0
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/