On Tuesday 28 September 2004 2:55 pm, Greg KH wrote: > Read the PCI spec, or better yet, the MindShare PCI book. In it, it > explains that PME# generates a SCI to the processor which is handled by > ACPI. It's then up to the acpi code to walk the list of pci devices and > notifying the proper ones that PME# happened.
That's what I expected ... > And no, you can't poll for PME#, the hardware doesn't allow it. Actually the PCI PM struct, in config space, does expose a bit saying whether that device is currently signaling PME#. That's the bit that the ACPI code (or whatever) would check, to decide what to resume(). > So go bug the firmware/acpi people about adding support for this, it's > up to them to implement it (or not.) That'd probably go easier after the current "brand spankin' new" ACPI wakeup code gets shaken out a bit more. Though maybe making that work would be what shakes it out! When I see USB1, USB2, USB3, and USB4 listed as wakeup devices in /proc/acpi/wakeup, on a system with only three USB controllers, I have a hard time sorting out how to make 0000:02:0f.3 issue wakeups ... ;) - Dave ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
