On Sun, 25 Feb 2007, Jon Smirl wrote: > I seem to be in an unstable race between the ehci and uhci buses for > assigning bus #1.
That shouldn't happen unless you have enabled the config option for for parallel PCI probing. If you have, you might as well turn it off -- it has caused a number of problems. > What does this do? > #define USB_ENDPOINT_MAX_ADJUSTABLE 0x80 I have no idea. It must be part of some extension, like wireless USB. > Are 0x02 and 0x04 supposed to be missing? > #define USB_REQ_GET_STATUS 0x00 > #define USB_REQ_CLEAR_FEATURE 0x01 > #define USB_REQ_SET_FEATURE 0x03 > #define USB_REQ_SET_ADDRESS 0x05 > #define USB_REQ_GET_DESCRIPTOR 0x06 > #define USB_REQ_SET_DESCRIPTOR 0x07 > ..... Yes. They are listed as "Reserved for future use" in Table 9-4 of the USB spec. > Yes, but you don't need the remote host DNS data to fully decode the > stream protocol. I can't fully decode my protocol if I don't know the > USB device ID of the device that generated it. That's the problem with > all of the vendor specific data formats. You'd be in similar trouble if you encountered an Ethernet stream where the protocol was determined in the first stages of a connection. However I can't think offhand of any protocols like that. Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
