| 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
| ||
|
Date: Wed, 20 Feb 2008 17:54:51 +0100 From: Andi Kleen <andi@...stfloor.org> To: Tilman Schmidt <tilman@...p.cc> CC: Gregory Nietsky <gregory@...worksentry.co.za>, 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? Was: [PATCH 00/14] [ISDN] ... > mISDN has two problems, which are of course interrelated: > > a) complete lack of documentation for the in-kernel driver interface > (equivalent of Documentation/isdn/INTERFACE) Most subsystems in the kernel would disqualify under that rule Did you ever look for full documentation on how to write Ethernet drivers for example? Some bits are documented, but far from all I'm not defending that, but it's how it is. > > b) still doesn't support all the hardware isdn4linux supports. That's a show stopper of course. > (maintainer of an isdn4linux driver, waiting desperately for > documentation on how to convert to the new CAPI/mISDN world > but tired of asking for it in vain) My advice is that you just read the source of some existing drivers for examples and copy them and of the subsystem itself if anything is unclear. That is how Linux drivers are usually written. -Andi -- 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/
Powered by blists - more mailing lists