From: Gregory Nietsky <gregory@networksentry.co.za>
To: Andi Kleen <andi@firstfloor.org>
Cc: Tilman Schmidt <tilman@imap.cc>, Sam Ravnborg <sam@ravnborg.org>,
Greg KH <greg@kroah.com>,
kkeil@suse.de, isdn4linux@listserv.isdn4linux.de,
linux-kernel@vger.kernel.org, Jeff Garzik <jeff@garzik.org>
Subject: Re: Plans for mISDN? Was: [PATCH 00/14] [ISDN] ...
Date: Wed, 20 Feb 2008 21:04:41 +0200 [thread overview]
Message-ID: <47BC79C9.8010102@networksentry.co.za> (raw)
In-Reply-To: <47BC5B5B.90308@firstfloor.org>
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.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.remember mISDN is just the kernel bits there is a user lib that
takes care of userland bits.
>
>> 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 ...
over all the most common devices are better supported under mISDN than
isdn4linux.
and as with OSS/ALSA both can coexist on the system as modules (only one
can be loaded at a time or else they dont play nice).
i really think this is a storm in a tea cup been blown into a hurricane
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.the reality is that isdn4linux is dead idealy unsuported
drivers need to be ported to mISDN or kept on life support.
--
This message has been scanned for viruses and
dangerous content by Superset Technology, and
is believed to be clean.
http://www.superset.co.za
next prev parent reply other threads:[~2008-02-20 19:05 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 4:41 [PATCH 00/14] [ISDN] convert HiSax to hotplug APIs Jeff Garzik
2008-02-16 4:41 ` [PATCH 01/14] [ISDN] HiSax: modularization prep Jeff Garzik
2007-07-18 3:46 ` [PATCH 04/14] [ISDN] HiSax bkm_a4t: convert to PCI hotplug API Jeff Garzik
2007-07-18 3:49 ` [PATCH 05/14] [ISDN] HiSax enternow: " Jeff Garzik
2007-07-18 3:54 ` [PATCH 06/14] [ISDN] HiSax hfc_pci, w6692: " Jeff Garzik
2007-07-18 3:59 ` [PATCH 07/14] [ISDN] HiSax nj_s, nj_u: " Jeff Garzik
2007-07-18 4:02 ` [PATCH 08/14] [ISDN] HiSax telespci: " Jeff Garzik
2007-07-24 12:26 ` [PATCH 11/14] [ISDN] HiSax niccy: convert to modern ISA/PNP/PCI probing Jeff Garzik
2007-08-02 12:37 ` [PATCH 14/14] [ISDN] HiSax bkm_a8: convert to PCI hotplug API Jeff Garzik
2007-10-31 5:10 ` [PATCH 03/14] [ISDN] Ready HiSax driver for modularization Jeff Garzik
2007-10-31 5:11 ` [PATCH 09/14] [ISDN] HiSax avm_pci: convert to modern PCI/ISA/PNP probing Jeff Garzik
2007-10-31 5:12 ` [PATCH 10/14] [ISDN] HiSax gazel: convert to modern ISA/PCI probing Jeff Garzik
2007-10-31 5:13 ` [PATCH 13/14] [ISDN] HiSax diva: convert to modern ISA/PNP/PCI probing Jeff Garzik
2007-10-31 7:42 ` [PATCH 02/14] [ISDN] Hisax: eliminate many unnecessary references to CardType[] Jeff Garzik
2008-02-16 19:17 ` [PATCH 12/14] [ISDN] HiSax avm_pci, niccy: minor PNP fixes and cleanups Jeff Garzik
2008-02-17 19:52 ` Plans for mISDN? Was: [PATCH 00/14] [ISDN] Sam Ravnborg
2008-02-18 4:52 ` Greg KH
2008-02-18 12:08 ` Andi Kleen
2008-02-18 12:04 ` Alan Cox
2008-02-18 12:36 ` Jeff Garzik
2008-02-18 13:29 ` Andi Kleen
2008-02-19 8:50 ` Sam Ravnborg
2008-02-19 9:25 ` Gregory Nietsky
2008-02-19 9:54 ` Sam Ravnborg
2008-02-20 14:19 ` Tilman Schmidt
2008-02-20 14:23 ` Alan Cox
2008-02-20 16:54 ` Andi Kleen
2008-02-20 18:23 ` Plans for mISDN? Tilman Schmidt
2008-02-20 19:04 ` Gregory Nietsky [this message]
2008-02-20 22:47 ` Tilman Schmidt
2008-02-21 10:33 ` Plans for mISDN? Was: [PATCH 00/14] [ISDN] Simon Richter
2008-02-21 19:38 ` Gregory Nietsky
2008-02-21 19:46 ` Marcel Holtmann
2008-02-21 23:19 ` Andi Kleen
2008-02-21 23:30 ` Marcel Holtmann
2008-02-21 23:40 ` Andi Kleen
2008-02-22 12:04 ` Karsten Keil
2008-02-23 19:39 ` Sam Ravnborg
2008-02-25 14:39 ` Plans for mISDN? Tilman Schmidt
2008-03-03 17:32 ` Karsten Keil
2008-02-19 9:40 ` Plans for mISDN? Was: [PATCH 00/14] [ISDN] Andi Kleen
2008-02-19 9:56 ` Sam Ravnborg
2008-02-19 9:58 ` Andi Kleen
2008-02-19 10:51 ` Armin Schindler
2008-02-19 11:55 ` Sam Ravnborg
2008-02-19 16:12 ` Gregory Nietsky
2008-02-19 16:14 ` Marcel Holtmann
2008-02-20 14:24 ` Tilman Schmidt
[not found] <9XBPP-6LJ-23@gated-at.bofh.it>
[not found] ` <9XXQl-7or-3@gated-at.bofh.it>
[not found] ` <9Y67a-3ta-9@gated-at.bofh.it>
[not found] ` <9YcYY-63L-25@gated-at.bofh.it>
[not found] ` <9YwuJ-3a7-17@gated-at.bofh.it>
[not found] ` <9YxqU-4Ge-11@gated-at.bofh.it>
[not found] ` <9YY7F-5bH-13@gated-at.bofh.it>
[not found] ` <9ZhtN-2cL-51@gated-at.bofh.it>
[not found] ` <9ZpAK-6CQ-25@gated-at.bofh.it>
[not found] ` <9ZsS5-3zh-21@gated-at.bofh.it>
[not found] ` <9Ztbm-3XZ-1@gated-at.bofh.it>
[not found] ` <9Ztbq-3XZ-9@gated-at.bofh.it>
2008-02-25 15:45 ` Bodo Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47BC79C9.8010102@networksentry.co.za \
--to=gregory@networksentry.co.za \
--cc=andi@firstfloor.org \
--cc=greg@kroah.com \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=jeff@garzik.org \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tilman@imap.cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox