> -----Original Message----- > From: Felipe Balbi [mailto:felipe.balbi@xxxxxxxxx] > On Fri, Aug 29, 2008 at 02:06:45PM +0530, ext Gadiyar, Anand wrote: > > > On Fri, Aug 29, 2008 at 10:11:00AM +0530, ext Gupta, Ajay Kumar wrote: > > > > > > > > I tested MUSB controller on OMAP35xx EVM > > > (omap3_evm_defconfig) for g_ether gadget and it works fine > > > with Windows XP. I am using v2.6.26-omap2 tag. > > > > > > ehehe, cool. So looks like the problem is either on tusb6010 or in > > > g_ether itself. > > > > > > I'll bisect since I know 2.6.24-omap1 was working. > > > > > > -- > > > balbi > > > > Er... I didn't get this. > > > > Q1. Why tusb6010? > > Q2. Given v2.6.26-omap2 is working, isn't 2.6.24-omap1 older > > and by default working? > > Hmm... you got it working with v2.6.26... I'll bisect between that and > HEAD so. > I'm guessing you didn't see my previous mail [1]. Last known good commit is 509f205d6. That'll save you an iteration at least. You can go from there, but there's nothing that's changed in the musb folder. Strongly suggest you look in drivers/usb/gadget/*. Lots of changes there. And you may not be able to bisect unless you have hardware that's in mainline or you take the changes manually each time - the usb/gadget/* stuff came in from that way. - Anand [1] <http://marc.info/?l=linux-omap&m=121998543230746&w=2>-- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
