> > I suppose that for network interface names, some convention for
> > interface ioctls would suffice to solve that "identify" step.  PCI
> > devices would return the slot_name, USB devices need something
> > like a patch I posted to linux-usb-devel a few months back.
> 
> This is crap.

Only the ioctl part, though I confess to trolling for a better proposal ... :)


> If you want to do it - do it right. Accessing /dev/eth/<n>/MAC
> is trivial. Wanking with ioctls is not. And populating such tree
> is as simple as it gets.

For links without a stable MAC, /.../net/<ifname>/{pci-slot,usb-path,...}
is more like it, but I think that class of solution should be fine.

Now ... what should be the roles of "regular" file ops, devfs, usbdevfs,
procfs, and "devreg" ?  That's the part that doesn't seem simple yet.
I'd expect a few rounds of code/design changes.

- Dave




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to