Messages in this thread | | | Date | Tue, 13 Nov 2007 16:14:58 -0700 | From | Alex Chiang <> | Subject | Re: [PATCH 0/5][RFC] Physical PCI slot objects |
| |
Hi Greg,
* Greg KH <greg@kroah.com>: > On Tue, Nov 13, 2007 at 02:31:08PM -0700, Alex Chiang wrote: > > > > FWIW, the ACPI 2.0 spec did not require uniqueness for _SUN. > > (although there is a strange table that refers to _SUN as the > > slot-unique ID (table 6-1 in spec v2.0b), the actual definition > > of _SUN does not mention uniqueness). > > Does your code handle if these are not unique?
I hate to punt on this, but I'm not doing anything that acpiphp is not doing. If we get back non-unique values for _SUN, I'm pretty sure both acpiphp and my pci_slot driver will both continue along as far as they can, until they get an error back from kobject_register() about trying to register an object with an existing name.
I think I may have a machine that has non-unique values for _SUN. If so, I'll try and hunt it down and do some testing.
Thanks for the suggestion.
/ac
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |