Hi, On Wed, Apr 09, 2008 at 04:12:01PM +0200, Pau Tallada Crespí wrote:
> > Hmm, are there any real changes to the codebase in that release? I > > remember something like only userspace changing. > I don't know. A diff shows something about isdn_compat and some code to > convert to ulaw/alaw o something. Ah okay, then a new version makes sense indeed. From the comments on the I4L mailing list during the last weeks it was clear that this branch had been abandoned, and all changes were taking place in a new branch that so far only had two different cards working. > Uhm, I understand. I read that misdn is a rewrite of the old isdn4linux, for > 2.6 kernels. But misdn was not ready and isdn4linux was ported also to 2.6. > So, what is the correct way to handle isdn cards on linux 2.6? For instance, > with asterisk. If you only need TE functionality, then i4l and CAPI is the way to go. For NT mode, mISDN is the only real option, but it cannot be properly supported by a distribution yet, as the ABI keeps on changing, and package dependencies cannot express this properly, so we will leave users with broken systems a lot. > > Fortunately mISDN is already being rewritten so it doesn't need that > > system anymore. > Another rewrite? Yes, at least partially. The biggest changes are: - Hardware drivers will be loaded by hotplug - The app is responsible for setting up the entire ISDN stack, so it is no longer necessary to pass protocol and layermask parameters - The userspace interface is likely to drop access to the lower layers because the only user so far was NT mode, and we can move that code to the kernel as well. Simon
