![]() | |||||||||||||
Messages in this thread |
Alan Stern wrote: > The real issue here is the way ieee1394 sets up children of devices with > no driver. On the face of it that is quite illogical: If a device has no > driver, then who can interrogate it to find out about its children? Perhaps I should turn this dummy driver into an actual representation of ieee1394 or ieee1394's nodemgr. > USB faces a similar situation. In a USB device, all the real work is > actually done by "interfaces". So we set up a device structure for the > USB device itself, plus device structures for each of its interfaces. The > parent structure is bound to a (more or less) dummy driver, which insures > that the child structures are deleted whenever it gets unbound. I will eventually more thoroughly look at how USB and other subsystems with device hierarchies do it. > Still, maybe some compromise can be reached. Perhaps Dmitry's idea, or > something like it, can be adopted. Thanks for the input of both of you. -- Stefan Richter -=====-=-==- =-== =-=-= http://arcgraph.de/sr/ - 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/ | ||||||||||||
| Last update: 2006-11-21 08:09 [from the cache] ©2003-2008 | |||||||||||||