I would like to precise that it's a SETUP packet for a CONTROL message -----Original Message----- From: Stephane Cerveau [mailto:scerveau@xxxxxxxx] Sent: mercredi 4 mars 2009 11:05 To: Gupta, Ajay Kumar Cc: davinci-linux-open-source@xxxxxxxxxxxxxxxxxxxx; linux-usb@xxxxxxxxxxxxxxx Subject: RE: USB host Issue: scsi command abort Hi, By analyzing the packets exchanged on the USB bus, I noticed that sometimes the SETUP packet can have a length inferior to 8, by example 4. Did anybody ever notice this case ? Best regards. Stéphane Cerveau -----Original Message----- From: Stephane Cerveau Sent: mardi 24 février 2009 16:04 To: Gupta, Ajay Kumar Cc: davinci-linux-open-source@xxxxxxxxxxxxxxxxxxxx; linux-usb@xxxxxxxxxxxxxxx Subject: RE: USB host Issue: scsi command abort Hello, I'm using a 2.6.18 kernel on a specific davinci platform and I tried to backport the last GIT MUSB driver. Unfortunately too much changes in the usb core stack. So I tried to compile the GIT kernel for EVM board, but I did not find any davinci defconfig. Do you know where I can find it? BR Stephane. -----Original Message----- From: David Brownell [mailto:david-b@xxxxxxxxxxx] Sent: lundi 23 février 2009 20:11 To: Stephane Cerveau Cc: davinci-linux-open-source@xxxxxxxxxxxxxxxxxxxx; Gupta, Ajay Kumar; linux-usb@xxxxxxxxxxxxxxx Subject: Re: USB host Issue: scsi command abort On Monday 23 February 2009, Stephane Cerveau wrote: > Do you know where can I find the last official version of > musb driver where the two patch, you sent me, are integrated. They're not yet merged in any kernel I know of, outside of (presumably) TI development trees. Those two patches are candidates for 2.6.30 merge, pending review and testing ... if they resolve this problem for you, please tell us. Confirmation that a patch works will help that process. > It seems that my driver misses a lot of patches. The current plan is to integrate through mainline, and maybe pre-merge patches queued for the next merge window into the DaVinci (or OMAP) trees. One way to look at that is aiming to have the MM or -next staging trees work for DaVinci (or OMAP) in the "normal" way. We want to get away from having DaVinci-specific patches languish in the DaVinci tree ... ditto the OMAP tree. Specific to DaVinci there are a few patches that can't yet queue to mainline, since they depend on support for new SoC chips (notably DM355) which hasn't yet been queued for mainline merge yet. I recently signed off on ten low-risk patches that I hope will be merged for 2.6.29-final ... and have about as many (including the two Ajay noted) which would be candidates for 2.6.30 (some are shoo-ins, others not). - Dave _______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@xxxxxxxxxxxxxxxxxxxx http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
