Re: [PATCH linux-acpi] Correct wakeup set error and append a new column PCI ID

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Pavel Machek <pavel@...>
Cc: <linux-acpi@...>, <linux-kernel@...>, <lenb@...>, <acpi-bugzilla@...>
Date: Wednesday, January 2, 2008 - 10:02 pm

On Wed, 2008-01-02 at 17:09 +0100, Pavel Machek wrote:
This is just for users' convenience, i believe you must think 0xff and
0xFF are the same.

Assume you are a user of /proc/acpi/wakeup, when you
cat /proc/acpi/wakeup, you only get PCI bus id, then you need use PCI
bus id to get the device info, that is platform-specific, if you want to
use this PCI bus id to get the device info from another machines, that
is absolutely impossible, but it is ok if it is PCI ID.

Moreover, you can very easily get the device info
from /usr/share/hwdata/pci.ids.

grep <PCI ID> /usr/share/hwdata/pci.ids

That is more convenient than PCI bus id.

If we can provide PCI ID in /proc/acpi/wakeup, why we let users get that
from /sys/devices/pci...?


--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH linux-acpi] Correct wakeup set error and append a..., Yi Yang, (Wed Jan 2, 10:02 pm)
Re: [PATCH] ACPI: Add sysfs interface for acpi device wakeup, Thomas Renninger, (Wed Mar 19, 9:06 am)
Re: [PATCH] ACPI: Add sysfs interface for acpi device wakeup, Matthew Garrett, (Thu Jan 10, 6:30 am)
[PATCH] ACPI: fix processor limit set error, Yi Yang, (Mon Jan 7, 11:21 pm)