Messages in this thread |  | | Date | Fri, 19 Oct 2001 10:21:36 -0500 | From | Taral <> | Subject | Re: [RFC] New Driver Model for 2.5 |
| |
On Thu, Oct 18, 2001 at 02:13:18PM +0200, Benjamin Herrenschmidt wrote: > 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.
Actually, if this field were to be added, I think it would be far better to have it be NULL in the case where there is no ID which can be expected to remain the same on insert/remove. Otherwise we might have people getting very confused when someone removes device A and adds device B and they end up with the same "unique id" because neither one has a real unique id.
-- Taral <taral@taral.net> This message is digitally signed. Please PGP encrypt mail to me. "Any technology, no matter how primitive, is magic to those who don't understand it." -- Florence Ambrose - 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/
|  |