On Thu, 8 Jan 2004, Duncan Sands wrote:
> Any idea where the usb interface's device's kobject's name is setup?
> I'm talking about kobject_name(&intf->dev->kobj).
Well, the device's kobject's name is set in
drivers/base/core.c:device_add() by this line of code:
kobject_set_name(&dev->kobj,dev->bus_id);
device_add(), in turn, is called by usb_set_configuration (or maybe in
your version of the code it's device_register(), which calls
device_add()).
That just pushes the problem back to where intf->dev->bus_id is set. It's
also set in usb_set_configuration(), although there's no reason it
couldn't be done earlier in config.c.
Alan Stern
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
