https://bugzilla.kernel.org/show_bug.cgi?id=19162
--- Comment #3 from Thomas Renninger <[email protected]> 2010-10-01 05:20:13 --- The problem is that there are a lot PCI devices which are defined/assigned via _ADR to their PCI bus:slot.func. I am not sure they should get exposed via ACPI at this place, better would be if acpi attributes show up in a pci specific sysfs device tree. IMO it's not worth to at some time link from PCI dev dir to ACPI dev dir and vice versa. There also seem to be some orphaned ACPI objects without _ADR and HID/CID, but they seem to have a _STA func which tells the device is working/active. I'll send out 2 patches to the list. I could not resist to try/do some further cleanups, maybe I should not have started with the trying to get the HID stuff const... Next cleanup step could be to not call: acpi_device_register(..) if the device has no HID/CID, there won't bind a ACPI driver to this object anyway. But...: - I got a NULL pointer in acpi_add_single_object(..) - some stuff still needed for other devices needs to go up one func there: wakeup list, etc. - Whatabout objects that exported a _EJX via sysfs files -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are watching the assignee of the bug. ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ acpi-bugzilla mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
