On 12/07/12 18:00, Pete Batard wrote: >> The attached patch fixes this by not adding the same interface path >> twice. It also adds a check for the interface table getting full. > Ideally I don't think we want to call set_hid_interface() more than we > need to, which is what happens here. So while your patch looks OK, and I > think checking for an out of bound array is probably something we want > to keep, there may be an alternate way we can use that avoids checking > strings. I'll see if I can come up with something.
Would keeping a list of the registered device handles (dev_info_data.DevInst) with each device and compare against that list be better? It then would at least avoid multiple string comparisons. Regards, Toby ------------------------------------------------------------------------------ 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
