[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 1 of 6] Add an ACPI device exposing a package called ADDR, evaluating to two
On 29/11/2011 16:29, "Ross Philipson" <Ross.Philipson@xxxxxxxxxx> wrote: >> I have no problem choosing a different _HID. I just don't have a good >> reference for what name is not going to clash with something else. Looks >> like ACPI0001 was a bad guess. Any better suggestions? What are the >> 'generic PNP device IDs'? >> >> Paul > > Well I actually brought it up as a discussion point. I have the same sort of > issue - I have a generic device for a virtualized environment. I don't really > want it to be recognized as anything specific. I guess I see three options: > > - Use an unassigned APCIXXXX string. I believe the _HID string values of the > form "ACPIXXXX" are defined by the ACPI specs themselves so this may not work > in the long run. > - Use one of the predefined generic container EisaId PNP values. By that I > meant using EisaId(PNP0A05) or EisaId(PNP0A06). Looking at the Linux generic > container driver, it doesn't do very much with these devices so that might be > OK. This option sounds reasonable. We have freedom to change it in future if it turns out to be a bad choice, not that I can see why it would be. -- Keir > - Acquire a vendor specific EisaId range for Xen (e.g. EisaId(XENABCD)). Then > we could carve up the product number part of the ID as we see fit. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |