Message-ID: <47BCAE1B.70407@imap.cc>
Date:	Wed, 20 Feb 2008 23:47:55 +0100
From:	Tilman Schmidt <tilman@...p.cc>
To:	Gregory Nietsky <gregory@...worksentry.co.za>
CC:	Andi Kleen <andi@...stfloor.org>, Tilman Schmidt <tilman@...p.cc>,
	Sam Ravnborg <sam@...nborg.org>, Greg KH <greg@...ah.com>,
	kkeil@...e.de, isdn4linux@...tserv.isdn4linux.de,
	linux-kernel@...r.kernel.org, Jeff Garzik <jeff@...zik.org>
Subject: Re: Plans for mISDN?

Am 20.02.2008 20:04 schrieb Gregory Nietsky:
> did someone say interface/API documentation ooops ... <DUCK> seriously
> this is lacking and im sure as time goes on some volenteer (sucker) will
> get it up and running.this is not a show stoper but a nice to have.

It's an enabler for getting a move forward towards replacing the old
isdn4linux subsystem, which has really outlived its time by now.

> ill 
> perhaps even help out a bit with things, i have some comments on useage 
> and module parameters that could be usefull to the would be 
> users.

Great. I'm looking forward to that.

> remember mISDN is just the kernel bits there is a user lib that 
> takes care of userland bits.

But it's the kernel bits which are essential for porting existing
isdn4linux hardware drivers to CAPI/mISDN!

Btw, could you perhaps clear up the terminology while you're at it?
Last time I looked, mISDN was advertised as a framework for writing
CAPI drivers for passive ISDN adapters, in turn using CAPI4Linux,
the Linux CAPI subsystem. Nowadays the picture is rather less
clearcut.

>  >> b) still doesn't support all the hardware isdn4linux supports.
>  >
>  > That's a show stopper of course.
> 
> of course not all hardware is supported and in some cases more hardware 
> is supported ... there is a precident for this OSS/ALSA where the one is 
>   marked as DEPRICATED and the other promoted initialy as EXPERMENTAL ...

I'm all for following that precedent: support both frameworks in
parallel, mark the old one as deprecated, give help in porting
hardware support to the new one, and when all the hardware that's
actually still in use in the field is supported by the new one,
remove the old one.

> after all if it were mainlined (in -mm even) the result would be better 
> support and more choice there are far worse supported drivers than the 
> mISDN stack.

Absolutely. It's high time mISDN found it's way into the main tree,
otherwise it's in danger of degenerating into a niche solution.

> the reality is that isdn4linux is dead

Reality check, please. Have a look in the field how many systems
still use isdn4linux. Or do a simple experiment: Take a distribution
which has been known for good ISDN support in the past (I think you
know the one) and set it up for Internet access via a typical cheap
ISDN card. Then look which ISDN subsystem you end up with. You may
be surprised.

> idealy unsuported 
> drivers need to be ported to mISDN or kept on life support.

Exactly. But there are two preconditions for porting an in-tree
isdn4linux driver to mISDN: First, mISDN must also be in-tree,
otherwise an in-tree driver cannot rely on it. And second, someone
must understand both the old driver and the mISDN framework in
order to be able to actually do the porting. The maintainer of the
old driver can provide the first part, but knowledge about mISDN
will need to come from the mISDN collective.

HTH
T.

-- 
Tilman Schmidt                          E-Mail: tilman@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


Download attachment "signature.asc" of type "application/pgp-signature" (254 bytes)

Powered by blists - more mailing lists