From: Gregory Nietsky <gregory@networksentry.co.za>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andi Kleen <andi@firstfloor.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: Tue, 19 Feb 2008 11:25:06 +0200 [thread overview]
Message-ID: <47BAA072.9050601@networksentry.co.za> (raw)
In-Reply-To: <20080219085033.GA1775@uranus.ravnborg.org>
ive been hackin away at mISDN for a while and use it with recent kernels
2.6.2X and have a patch for 2.6.24 (move from semaphore to complition)
the distro we built is heavily reliant on mISDN (voip) i dont use the
isdn kernel drivers at all any longer.
im all for mISDN been mainlined into the kernel and the old stuff been
removed there could be users still it is marked as depricated and the
plan was with 2.6 to use mISDN from the start.
Greg
Sam Ravnborg wrote:
> On Mon, Feb 18, 2008 at 01:08:33PM +0100, Andi Kleen wrote:
>> Greg KH <greg@kroah.com> writes:
>>> If Jeff does that, I still can't drop those PCI functions from the PCI
>>> core, which I desperatly want to do as they do not play nice with modern
>>> systems (meaning hotplug...).
>>>
>>> So either way, I think his patches should go in.
>> Merging essentially untested patches does not seem like a good strategy.
>> And there is definitely still a large ISDN user base too.
> Only issue seems that this large ISDN user base is not very active
> in respect to Linux driver development.
> Or at least not judging from the missing responses to their
> mailing list and the limited traffic on said mailing list.
>
> Reading the isdn4linux it is obvious that the way forward are the
> mISDN code base so maybe that explains why noone steps up and
> test the patches of Jeff's.
>
> If noone in the isdn community step up and take some responsibility
> for the current isdn drivers in Linux then we should just delete them.
> If anyone cares they can always be forwardported or even better we can
> integrate the much more flexible mISDN solution.
>
>> My personal guess is that there are far more ISDN users than (non cardbus)
>> PCI/PCI-e hotplug users.
>
> My guess is that very very few uses ISDN in combination with a recent kernel.
> Hmm, wonder if it is more fun hacking isdn drivers than kbuild
> stuff and section mismatches ;-)
>
> Sam
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
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-19 9:50 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 [this message]
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 ` Plans for mISDN? Was: [PATCH 00/14] [ISDN] Gregory Nietsky
2008-02-20 22:47 ` Plans for mISDN? 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=47BAA072.9050601@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 \
/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