linux-kernel - Re: [RFC] New driver information

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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0702161334170.20138@iabervon.org>
Date:	Fri, 16 Feb 2007 13:48:15 -0500 (EST)
From:	Daniel Barkalow <barkalow@...ervon.org>
To:	Heikki Orsila <shdl@...alwe.fi>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] New driver information

On Fri, 16 Feb 2007, Heikki Orsila wrote:

> I just read
> 
> 	http://kerneltrap.org/node/7729
> 
> and it occured to me that it would be informative to have a new device 
> driver macro. The motivation for the new macro would be 4 issues:
> 
> 	* Is it possible to get specifications for the device?
> 	* If yes, under what terms? (nda, public)
> 	* Where to get public specs?
> 	* How many closed and open drivers in the Linux source tree?

This doesn't make any sense as a driver macro, because it's per device, 
not per driver. E.g., the sdhci driver drives a number of devices, 
including both well-documented devices and devices whose only 
documentation is that the PCI ID matches (and they work with only a few 
quirks).

On the other hand, a kconfig-readable table of PCI, USB, etc IDs with this 
information isn't a bad idea, especially if the drivers actually depend on 
it (so that it has to be kept up to date, at least as far as the 
device/driver mapping).
-
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/