Re: [U-Boot] ulpi patch in uboot

2013-05-16 Thread Michael Trimarchi
Hi On Thu, May 16, 2013 at 04:35:57PM +0200, Stefano Babic wrote: > On 16/05/2013 15:19, Michael Trimarchi wrote: > > > Hi Michael, > > > From 7e99dcbe83e26fff3a0168105eec99003650b744 Mon Sep 17 00:00:00 2001 > > From: Michael Trimarchi > > Date: Thu, 16 May 2013 15:16:17 +0200 > > Subject: [P

Re: [U-Boot] ulpi patch in uboot

2013-05-16 Thread Stefano Babic
On 16/05/2013 15:19, Michael Trimarchi wrote: Hi Michael, > From 7e99dcbe83e26fff3a0168105eec99003650b744 Mon Sep 17 00:00:00 2001 > From: Michael Trimarchi > Date: Thu, 16 May 2013 15:16:17 +0200 > Subject: [PATCH] omap-ulpi: Fix the omap3/4 access function to the bus > > Signed-off-by: Micha

Re: [U-Boot] ulpi patch in uboot

2013-05-16 Thread Igor Grinberg
Cc'ed Marek and Govindraj. On 05/16/13 16:19, Michael Trimarchi wrote: > Hi [...] Thanks for the patch, it looks like a correct fix. I'd like to hear that it works on an actual hardware. > >>From 7e99dcbe83e26fff3a0168105eec99003650b744 Mon Sep 17 00:00:00 2001 > From: Michael Trimarchi > Dat

Re: [U-Boot] ulpi patch in uboot

2013-05-16 Thread Michael Trimarchi
Hi On Thu, May 16, 2013 at 12:34:39PM +0200, Stefano Babic wrote: > On 16/05/2013 11:42, Michael Trimarchi wrote: > > Hi a;;, > > > > Hi Michael, > > (I posted also to u-boot ML to check if someone else had issues) > > > I think that this patch could be wrong for omap4 and omap3. The opcode sh

Re: [U-Boot] ulpi patch in uboot

2013-05-16 Thread Michael Trimarchi
Hi Stefano On 16/05/13 12:34, Stefano Babic wrote: > On 16/05/2013 11:42, Michael Trimarchi wrote: >> Hi a;;, >> > > Hi Michael, > > (I posted also to u-boot ML to check if someone else had issues) > >> I think that this patch could be wrong for omap4 and omap3. The opcode shift >> shuld be 22

Re: [U-Boot] ulpi patch in uboot

2013-05-16 Thread Stefano Babic
On 16/05/2013 11:42, Michael Trimarchi wrote: > Hi a;;, > Hi Michael, (I posted also to u-boot ML to check if someone else had issues) > I think that this patch could be wrong for omap4 and omap3. The opcode shift > shuld be 22 and not 21. And are you sure that are you using the bit 31 > in the