On Wed, Jul 30, 2003 at 09:58:18AM +0200, Clemens Ladisch wrote: > Martin Langer wrote: > > looking into usbquirks.h I saw that audio endpoints follow the rule: > > 0x0... for output > > 0x8... for input > > I think that's absolutely ok! > > This is for the endpoint field of the audioformat structure. > > > And now: If I jump into the usb-midi world and try a similar quirk: > > .out_ep = 0x06, > > .in_ep = 0x86, > > it will end with an "usb_submit_urb: -22" :-( > > > > OTOH the use of > > .out_ep = 0x06, > > .in_ep = 0x06, > > will be accepted! :-) > > And I believe the USB MIDI device definition use 0x8.. values for inputs. > > The USB protocol defines an endpoint number as a 4-bit integer. > Additionally, input and output endpoints are distinct, and are > distinguished, when necessary, with bit 7 (0x80). > > The audioformat structure is the same for both input and output, > therefore it requires the "input" flag. The MIDI quirk structure has > separate fields for input and output endpoints, so you must not use > 0x80 in this case.
must not??? It doesn't work with the 0x80 flag!!! Only the 0x00 flag works! That was the point I've tried to explain. But I agree that the "must not" way would be a nice solution. .......................maybe in the future? martin ------------------------------------------------------- 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/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
