Wrong, the development goes in the other direction, make all in software,
because it's cheaper and the CPU's have enought power to handle it.
Also newer external ISDN devices with serial (standard or USB) are
quit simple and have no D-channel stack on it. Most USB ISDN TA simple map
register access to USB frames.
> the OS driver side: now it's a hardware certification issue). So only a
> rather small subset of the ISDN code is actually affected by these rules,
> and its' fairly easy to say something like "for these cards, it is illegal
> to connect the machine to the phone line if this part of the code has been
> changed".
>
Agree, and this is done so.
> I think it's basically just one or two drivers, and a subset of the driver
> at that.
>
> And quite frankly, let the people vote with their feet. Civil disobedience
> is not always a bad thing, as shown by people like Gandhi. Bringing down
> bad phone monopolies may not ever count as highly as getting the British
> Empire out of India, but let people decide on their own whether they
> should just bend over and take bad rules.
But I think, that some basically rules are necessary for a worldwide
operating net.
>
> SuSE may as a company decide that it cannot legally ship untested drivers,
> for example. They probably don't want to open themselves up to being sued
> by Deutche Telekom or whatever it is called. But even Germans are
> individuals - all the folklore to the contrary notwithstanding, and should
> be allowed to make their own informed judgement.
>
But again, how I said before too:
Your are right, the ISDN development according kernel development gone the
wrong way in the past and I and all other I4L developers like to change it
now.
Karsten
-
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/