David Brownell ([EMAIL PROTECTED]) said: > > But the layers *are* related. Network devices are, one way or > > another, directly connected to *some* underlying hardware. > > Sure. And the bus_info provides a cookie that identifies > that hardware.
Which, if you can't relate that cookie *to* the hardware, isn't that useful. > > > and the place where it's *easy* in 2.5 to make that > > association you're telling me I shouldn't rely on. > > That is, the "name" field? But as I said, you've been > overlooking the true definition of that field, as a > "user friendly" name. That's been sysfs, from day one > (back when it was "driverfs"). Were you trying to > use the "name" field for PCI devices? No? Then why > were you trying to do that for USB? Because it's not exported anywhere else. Bill ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
