Hi Dave, Bingo!
On Monday 31 Jan 2005 20:36, David Brownell wrote: <snip> > > If you want to poke around at that, BitKeeper is your friend. You can > look at the revision history of "ohci-q.c", both on the web (the website > being http://linux.bkbits.net/linux-2.5) or by running BK locally. > > - Dave I figured out that at 2.6.3 (under which my devices do work), ohci-q.c was at revision 1.47 whereas at 2.6.4 (under which my devices time out) it was at revision 1.50. So I progressively reverted revisions until I found that on reverting to 1.47, my devices work again. So the "offending" patch is the one that took ohci-q.c to revision 1.48. Would it help if I tried to work out which hunk, or hunks, of that patch cause me the problem? Or is it not possible to have part(s) of the patch without the rest? I'm afraid I simply don't have the knowledge to answer that. Thanks for your help so far. Chris ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
