| 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, 7 Feb 2007 11:43:46 +0100 From: Michael Leun <ml@...ton.leun.net> To: Matthew Garrett <mjg59@...f.ucam.org> Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>, mitr@...ny.cz, linux-kernel@...r.kernel.org Subject: Re: [PATCH] wistron button support for fujitsu-siemens Amilo D88x0 On Wed, 7 Feb 2007 09:58:07 +0000 Matthew Garrett <mjg59@...f.ucam.org> wrote: > On Wed, Feb 07, 2007 at 07:23:47AM +0100, Michael Leun wrote: > > Matthew Garrett <mjg59@...f.ucam.org> wrote: > > > Hm. Is there really no PNP id that tends to be associated with > > > this wistron hardware? Fujitsu (at least) seem to be quite good at > > > exposing a lot of their magic hardware that way. > > > > Sorry, I do not know and I do not know how to find out. If there is > > any testing I should do on my machine I will happily do that, but > > you would have to tell me what to do. > > cat /sys/bus/pnp/devices/*/id should give a list of the available IDs. ml@...ia:~> cat /sys/bus/pnp/devices/*/id PNP0a03 PNP0200 PNP0b00 PNP0800 PNP0c02 PNP0c04 PNP0303 PNP0f13 PNP0700 PNP0400 PNP0501 OK, it does, but what to do with them? Looking around there shows that some of them cover kbd, psaux, parport, and serial. ml@...ia:/sys/bus/pnp/devices> for i in *; do ls -l $i/; done insgesamt 0 -r--r--r-- 1 root root 4096 7. Feb 11:27 id -r--r--r-- 1 root root 4096 7. Feb 11:27 options drwxr-xr-x 2 root root 0 7. Feb 11:28 power -rw-r--r-- 1 root root 4096 7. Feb 11:27 resources lrwxrwxrwx 1 root root 0 7. Feb 11:27 subsystem -> ../../../bus/pnp --w------- 1 root root 4096 7. Feb 11:27 uevent insgesamt 0 -r--r--r-- 1 root root 4096 7. Feb 11:27 id -r--r--r-- 1 root root 4096 7. Feb 11:28 options drwxr-xr-x 2 root root 0 7. Feb 11:28 power -rw-r--r-- 1 root root 4096 7. Feb 11:28 resources lrwxrwxrwx 1 root root 0 7. Feb 11:28 subsystem -> ../../../bus/pnp --w------- 1 root root 4096 7. Feb 11:28 uevent insgesamt 0 -r--r--r-- 1 root root 4096 7. Feb 11:27 id -r--r--r-- 1 root root 4096 7. Feb 11:28 options drwxr-xr-x 2 root root 0 7. Feb 11:28 power -rw-r--r-- 1 root root 4096 7. Feb 11:28 resources lrwxrwxrwx 1 root root 0 7. Feb 11:28 subsystem -> ../../../bus/pnp --w------- 1 root root 4096 7. Feb 11:28 uevent insgesamt 0 -r--r--r-- 1 root root 4096 7. Feb 11:27 id -r--r--r-- 1 root root 4096 7. Feb 11:28 options drwxr-xr-x 2 root root 0 7. Feb 11:28 power -rw-r--r-- 1 root root 4096 7. Feb 11:28 resources lrwxrwxrwx 1 root root 0 7. Feb 11:28 subsystem -> ../../../bus/pnp --w------- 1 root root 4096 7. Feb 11:28 uevent insgesamt 0 lrwxrwxrwx 1 root root 0 7. Feb 11:28 driver -> ../../../bus/pnp/drivers/system -r--r--r-- 1 root root 4096 7. Feb 11:27 id -r--r--r-- 1 root root 4096 7. Feb 11:28 options drwxr-xr-x 2 root root 0 7. Feb 11:28 power -rw-r--r-- 1 root root 4096 7. Feb 11:28 resources lrwxrwxrwx 1 root root 0 7. Feb 11:28 subsystem -> ../../../bus/pnp --w------- 1 root root 4096 7. Feb 11:28 uevent insgesamt 0 -r--r--r-- 1 root root 4096 7. Feb 11:27 id -r--r--r-- 1 root root 4096 7. Feb 11:28 options drwxr-xr-x 2 root root 0 7. Feb 11:28 power -rw-r--r-- 1 root root 4096 7. Feb 11:28 resources lrwxrwxrwx 1 root root 0 7. Feb 11:28 subsystem -> ../../../bus/pnp --w------- 1 root root 4096 7. Feb 11:28 uevent insgesamt 0 lrwxrwxrwx 1 root root 0 7. Feb 11:28 driver -> ../../../bus/pnp/drivers/i8042 kbd -r--r--r-- 1 root root 4096 7. Feb 11:27 id -r--r--r-- 1 root root 4096 7. Feb 11:28 options drwxr-xr-x 2 root root 0 7. Feb 11:28 power -rw-r--r-- 1 root root 4096 7. Feb 11:28 resources lrwxrwxrwx 1 root root 0 7. Feb 11:28 subsystem -> ../../../bus/pnp --w------- 1 root root 4096 7. Feb 11:28 uevent insgesamt 0 lrwxrwxrwx 1 root root 0 7. Feb 11:28 driver -> ../../../bus/pnp/drivers/i8042 aux -r--r--r-- 1 root root 4096 7. Feb 11:27 id -r--r--r-- 1 root root 4096 7. Feb 11:28 options drwxr-xr-x 2 root root 0 7. Feb 11:28 power -rw-r--r-- 1 root root 4096 7. Feb 11:28 resources lrwxrwxrwx 1 root root 0 7. Feb 11:28 subsystem -> ../../../bus/pnp --w------- 1 root root 4096 7. Feb 11:28 uevent insgesamt 0 -r--r--r-- 1 root root 4096 7. Feb 11:27 id -r--r--r-- 1 root root 4096 7. Feb 11:28 options drwxr-xr-x 2 root root 0 7. Feb 11:28 power -rw-r--r-- 1 root root 4096 7. Feb 11:28 resources lrwxrwxrwx 1 root root 0 7. Feb 11:28 subsystem -> ../../../bus/pnp --w------- 1 root root 4096 7. Feb 11:28 uevent insgesamt 0 lrwxrwxrwx 1 root root 0 7. Feb 11:28 driver -> ../../../bus/pnp/drivers/parport_pc -r--r--r-- 1 root root 4096 7. Feb 11:27 id -r--r--r-- 1 root root 4096 7. Feb 11:28 options drwxr-xr-x 2 root root 0 7. Feb 11:28 power -rw-r--r-- 1 root root 4096 7. Feb 11:28 resources lrwxrwxrwx 1 root root 0 7. Feb 11:28 subsystem -> ../../../bus/pnp --w------- 1 root root 4096 7. Feb 11:28 uevent insgesamt 0 lrwxrwxrwx 1 root root 0 7. Feb 11:28 driver -> ../../../bus/pnp/drivers/serial -r--r--r-- 1 root root 4096 7. Feb 11:27 id -r--r--r-- 1 root root 4096 7. Feb 11:28 options drwxr-xr-x 2 root root 0 7. Feb 11:28 power -rw-r--r-- 1 root root 4096 7. Feb 11:28 resources lrwxrwxrwx 1 root root 0 7. Feb 11:28 subsystem -> ../../../bus/pnp drwxr-xr-x 3 root root 0 7. Feb 11:28 ttyS0 --w------- 1 root root 4096 7. Feb 11:28 uevent -- MfG, Michael Leun - 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