| 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
| ||
|
Message-ID: <4AC4EB2E.4050907@s5r6.in-berlin.de> Date: Thu, 01 Oct 2009 19:47:26 +0200 From: Stefan Richter <stefanr@...6.in-berlin.de> To: Nathaniel McCallum <nathaniel@...emccallum.com> CC: linux-kernel@...r.kernel.org, greg@...ah.com Subject: Re: Exposing device ids and driver names Nathaniel McCallum wrote: > Please CC me on any responses as I'm not subscribed to lkml. > > I have the aim at creating two tools helpful to linux. The first tool > is a driver regression test of sorts. I want to be able to create > essentially a time line of hardware support as they appear in distros. > The second tool, related to the first, is a program which runs on > Windows and scans for a user's hardware and tells them which distro will > best support their hardware. I already have a working prototype of > these two tools. It currently uses the data exported by modinfo. This > however does not provide transparency for drivers compiled into the kernel. Hardware support also depends on userland: Udev rules, libraries, application programs. Even if you ignore that for now and only look at the kernel part of hardware support: Beyond "doesn't have a matching driver" and "does have", there is a large and impossible to track grey area of "has a poorly working driver" and "has a perfectly working driver". -- Stefan Richter -=====-==--= =-=- ----= http://arcgraph.de/sr/ -- 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