On Tue, Mar 19, 2002 at 12:32:56AM +0100, Nemosoft Unv. wrote: > Hello, > > On Monday 18 March 2002 04:12, David Brownell wrote: > > > thus no ioctl(). > > > > There's this thing called JNI, which solves that. If they're doing stuff > > like memory mapping the video memory, it's being used already. > > If not, no big deal since the code is Linux-specific in the first place. > > Ah, I didn't know that. Unfortunately, not all USB drivers have an /proc/ > interface like CPiA.
Ok, sorry for jumping in late here, but no ioctl(). I hate the current usbfs ioctl interface and do not want to see that spread at all. usbfs could (and will) change to be representation of the usb tree in which no ioctls are needed. But that's in the future, and not much help right now, sorry :) > > That gets to virtues of having a standard "FOO" structure. > > Having a "user friendly" text access to that data would seem > > reasonable to me ... though I still won't expect programs to > > be parsing those text files. > > If it's available as "user friendly" text its parsable by scripts... > > > Another potential "standard FOO" virtue, yes. > > *nod* > > > > > 3) How should this information be presented in textual form in > > > /proc/bus/usb/*? > > > > I thought you were suggesting lines in "devices"? > > That, or entries in the subdirectories. "device" would, from a user point > of view, probably make most sense (only one place to look) Something like U: would be nice, but there are some problems, as detailed below. > > For example, > > each interface that was bound might have a "U:" line, which could > > have "char 180/32" (and if devfs were in use, the name it uses) > > Remember there could be multiple U: lines (does anybody know offhand of a > USB device that has multiple physical devices on one USB interface?) USB to serial devices do. I have a 8 port converter around here that only has 1 interface, yet as 8 minor numbers assigned to it. > As to the /devfs name... Could be done, but I would like to put the > amount of logic that is needed ina user program to a minimum, so 'old' > style /dev should be listed as well. Major/minor is all that is really needed. If you're using devfs you can manipulate devfsd to let you know that a new device has shown up, and what its name is. Actually the hotplug interface is almost all you need, just add a major/minor number announcement and you have everything (hint, hint...) > > or "net eth2" (ideally with a more fundamental ID too, since as I > > recall those names can be reassigned ... worth looking at what > > ethtool does, as Brad suggested). > > Please explain "more fundamental ID" ? "net eth2" sounds fine (or perhaps, > "net:eth2"). It's either something like that or a node starting with a / . Yes, network devices do not have a major/minor. But they are announced by /sbin/hotplug so you don't really need anything added for it. thanks, greg k-h _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
