On Thu, May 3, 2012 at 6:56 PM, Pete Batard <p...@akeo.ie> wrote: > On 2012.05.03 02:47, Xiaofan Chen wrote: >> Also Tim's view on this topic in the OSR mailing list / forum. >> http://www.osronline.com/showthread.cfm?link=223812 >> +++++++ >> One can also argue that this is a security measure. The USB spec >> requires that the low byte of wIndex be set to the interface number when >> the recipient is set to "interface". Devices that use that field for >> other purposes are broken. >> ++++++++ > > Yup, I saw it and I agree with Tim. > > The issue was that I thought Microsoft mandated the use of an arbitrary > wIndex with an "interface" recipient when reading the WCID properties, > and thus were breaking this recommendation. That's how this limitation > was highlighted in the first place. As long as this isn't the case, and > WinUSB only overrides wIndex for interface recipients, which it does (a > request to a device recipient lets you use any wIndex you want), there's > no problem. I think I'll remove this limitation from the Windows > Banckend page, as it isn't really one.
I see you have done that for the libusbx Mediawiki. I intend to do the same thing for libusb.org Trac Wiki but libusb.org is down now... -- Xiaofan ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
