Messages in this thread |  | | Date | 19 Oct 2001 00:10:00 +0200 | From | (Kai Henningsen) | Subject | Re: [RFC] New Driver Model for 2.5 |
| |
mochelp@infinity.powertie.org (Patrick Mochel) wrote on 18.10.01 in <Pine.LNX.4.21.0110180826240.16868-100000@marty.infinity.powertie.org>:
> > I would add to the generic structure device, a "uuid" string field. > > This field would contain a "munged" unique identifier composed of > > the bus type followed which whatever bus-specific unique ID is > > provided by the driver. If the driver don't provide one, it defaults > > to a copy of the busID. > > > > What I have in mind here is to have a common place to look for the > > best possible unique identification for a device. Typical example are > > ieee1394 hard disks which do have a unique ID, and so can be properly > > tracked between insertion removal. > > Hmm. So, this would be a device ID, much like the Vendor/Device ID pair in > PCI space?
Except for the fact that the Vendor/Device ID pair is a device *class* identifier, and the uuid is a device *instance* identifier.
MfG Kai - 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/
|  |