On Tue, Sep 28, 2004 at 04:59:04PM -0400, Alan Stern wrote: > On Tue, 28 Sep 2004, David Brownell wrote: > > > > > I suspect that it [PME#] goes to some > > > > ACPI "embedded controller", which either... > > > > > > Have you tried asking about this on the ACPI mailing list? > > > > Yes, no information was forthcoming. It's maybe > > more of a PCI PM issue. And in any case, it's clear that > > from the PCI perspective it's just another signal ... heck, > > you could even just poll the PME# status of PCI devices > > in some timer thread, if ACPI (or whatever) wasn't happy > > providing more efficient notifications. > > Maybe someone who knows more about the PCI core can help. Hmmm... > Looking at MAINTAINERS, I see that the person in charge of the PCI > subsystem is ... Greg Kroah-Hartman! Maybe he can tell us where to go for > more information. > > Greg?
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. And no, you can't poll for PME#, the hardware doesn't allow it. So go bug the firmware/acpi people about adding support for this, it's up to them to implement it (or not.) thanks, greg k-h ------------------------------------------------------- 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
