On Tue, Jun 15, 2004 at 03:29:10PM -0700, Johannes Erdfelt wrote: > > * How should this relate to "udev"? One implementation > > strategy would make "usbfs2" endpoint files be regular > > character devices. There are other strategies too, > > including not coupling them at all. > > Perhaps a sockets interface would be more appropriate?
From my point of view, a socket interface would definitely resemble USB better. After all, it is a packet oriented bus, and you have different devices with adresses. You also have well-understood semantics of 'binding' to an address, including a failure to bind if the address is already in use. But maybe that's just my strange view on the world as coming from a strong networking background. As already discovered in a recent thread here, USB snooping is very analogous to what tcpdump [or other pcap based software] dpes. The socket level could then determine whether you're intereted in sniffing/sending raw usb packets at the HCD (RAW usb socket) or whether you're interested in communicating with a specific device/interface/endpoint. > JE -- - Harald Welte <[EMAIL PROTECTED]> http://www.gnumonks.org/ ============================================================================ Programming is like sex: One mistake and you have to support it your lifetime
signature.asc
Description: Digital signature
