On Tue, 2 Dec 2003 [EMAIL PROTECTED] wrote: > Greg, > > My apologies for dragging this back to life after this long. I was > prepared to live with the specific kernel patches. However the > current code appears to be heading to more than 1 system, and there > is some concern that hacks we put will not suffice, as it may break > other systems. > > The only access I have to hardware is the JS20 with the ship level > hardware. I don't have any history (or access at this point) with > the other systems.
Is this still about the TEAC floppy drives? As I recall, you had two different drives, one labelled -159 which only worked with the CB transport, and the other labelled -259 which only worked with the CBI transport. Otherwise the drives were the same -- in particular, they had the same USB descriptors. Back in September I asked you to set the unusual_devs.h entry to CB, configure on usb-storage debugging, attach the -259 drive, and post the resulting debugging system log. Seeing that might help us figure out why the -259 drive doesn't work with our implementation of the CB transport (which it ought to do since CB is a subset of CBI). But you never did this. If you will run the test and post the results we might be able to help. Alan Stern P.S.: Is it possible that your particular -259 drive is defective in some way and that other drives of the same model will work okay with CB? ------------------------------------------------------- This SF.net email is sponsored by OSDN's Audience Survey. Help shape OSDN's sites and tell us what you think. Take this five minute survey and you could win a $250 Gift Certificate. http://www.wrgsurveys.com/2003/osdntech03.php?site=8 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
