On Wed, 25 Sep 2002 Matt_Domsch@Dell.com wrote:
> > But what do you do with the usb_bus_type? Why would your code use
> > anything that is private to the driver core?
>
> Fair enough. I actually only need the 64-bit unique ID that the USB device
> provides, and its parent PCI device. EDD provides this info as x86 BIOS
> sees it, so my code compares the two, and will make a symlink between the
> two. This lets the OS know which device BIOS thinks it is (i.e. to know
> what disk you're booting from).
>
> True, I don't (today) see a unique ID in struct usb_device. Hopefully
> that's something that can be added in the future. Functions which expose
> this info separate from exporting the bus type would be great.
UUIDs are something that many people have asked for in struct device. I've
put it off because they're used in only a few places today, because it's
impossible to standardize them across different device types, and it's
difficult to extract one from devices that don't inherently support them.
It's a valid request though. What we've talked about is:
- making it struct device::char * uuid;
- the bus that discovers the device is responsible for allocating and
freeing the field.
- It must be a NULL-terminated ASCII string.
- It will be exported in the device's drivefs directory in a file 'uuid'.
Anything else?
-pat
-
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/
This archive was generated by hypermail 2b29 : Mon Sep 30 2002 - 22:00:48 EST