Thanks Alan, It is good to get some feedback on how the buffer manipulation should work. I appreciate you taking the time.
> > Did you take care about checking byte-endian issues? > Yep, I didn't take enough care. I thought I had, but I have just found the URB transfer buffer is fragmented into QTDs but the buffer pointer used as LE format. Once this was changed the driver started to work without system crashes and would explain some of the behaviour I saw as random memory addreses (typically low ones) would be the source or target destinations for the ISP1761 driver. The Philips example driver had a few other BE-LE issues which I got caught on earlier in the development. > Yes, you have missed something. If you look more > carefully, you'll see > that transfer_buffer is not equal to us->iobuf when > transfer_length is > > 64. > Thanks... didn't notice that. > > The changes are explained when they are submitted into > the kernel. Look > through the email archives for the USB Mass Storage > driver (look it up in > the MAINTAINERS file in the kernel source). > Thanks for the info. Mike. ____________________________________________________________________________________ Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q&A. http://answers.yahoo.com/dir/?link=list&sid=396545367 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
