linux-kernel - Re: Plans for mISDN? Was: [PATCH 00/14] [ISDN] ...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 19 Feb 2008 11:25:06 +0200
From:	Gregory Nietsky <gregory@...worksentry.co.za>
To:	Sam Ravnborg <sam@...nborg.org>
CC:	Andi Kleen <andi@...stfloor.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? Was: [PATCH 00/14] [ISDN] ...

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@...ah.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@...r.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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/