On Thu, 1 Jul 2004, David Brownell wrote: > > Just last week I sent in a bunch of patches that make device resets work > > correctly in all circumstances. They haven't been accepted yet, and when > > they are it might not be in time for 2.6.8. But eventually they should > > get into the kernel. If you're interested in trying them out in the > > meantime, I can tell you what BK respository to start with and what > > patches to apply. > > Could you clarify which patches you mean? I'd guess as329 and as330, > they're the most significant ones in my "review this soon!" patch.
Yes. All the important ones preceding those two have been merged by Greg, although I don't know how far up the chain they've migrated yet. (as327 and as328 -- the usb_kill_urb() patches -- are more or less orthogonal; without them you'll get some offset warnings but things should still work.) > I don't think I noticed any patch enabling the code that reports > changed config descriptors (which Joerg will need). Would he be > able to add as329 and as330 to the current Linus/Andrew BK, and > then have usb_reset_device() trigger re-enumeration after DFU? Well, if he adds them to the gregkh-2.6 tree then yes, usb_reset_device() with a changed interface or whatever descriptor should trigger re-enumeration. If it doesn't there's something wrong with as322; that's the patch which actually enabled re-enumeration. But like I said, I'm not sure which patches are in which BK trees. Alan Stern ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
