U-Boot OMAP3 (EVM) MUSB patches

67 views
Skip to first unread message

Dirk Behme

unread,
Jan 4, 2009, 3:52:20 AM1/4/09
to beagl...@googlegroups.com

TI sent some U-Boot OMAP3 patches to U-Boot mailing list:

http://lists.denx.de/pipermail/u-boot/2009-January/045304.html

As mentioned there, they are for EVM, but should easily (?) be
adaptable to other OMAP3 boards, too. (by copying stuff from patch
08_musb.txt in attachment to beagle config?)

I put the 8 patches mentioned in that mail into a quilt patch series
(see attachment), maybe it helps you to adapt them for Beagle ;)

Patch series is against Steve's git [1].

I got one reject [2] I fixed manually. There is no

COBJS-$(CONFIG_USB_EHCI_FSL) += usb_ehci_fsl.o

in Steve's git (which should be in sync with mainline). Maybe it comes
from some U-Boot USB branch merge (?).

So patch series in attachment compiles fine with

omap3_evm_config
make

but I don't know if it works ;)

Regards

Dirk

[1]
http://www.sakoman.net/cgi-bin/gitweb.cgi?p=u-boot-omap3.git;a=shortlog;h=refs/heads/omap3-dev

[2] Reject:

-- cut --
> cat drivers/usb/Makefile.rej

*************** COBJS-$(CONFIG_USB_ISP116X_HCD) += isp116x-hcd.o
*** 35,40 ****
COBJS-$(CONFIG_USB_R8A66597_HCD) += r8a66597-hcd.o
COBJS-$(CONFIG_USB_SL811HS) += sl811_usb.o
COBJS-$(CONFIG_USB_EHCI_FSL) += usb_ehci_fsl.o

# device
ifdef CONFIG_USB_DEVICE
--- 35,41 ----
COBJS-$(CONFIG_USB_R8A66597_HCD) += r8a66597-hcd.o
COBJS-$(CONFIG_USB_SL811HS) += sl811_usb.o
COBJS-$(CONFIG_USB_EHCI_FSL) += usb_ehci_fsl.o
+ COBJS-$(CONFIG_MUSB_HCD) += musb_hcd.o musb_core.o

# device
ifdef CONFIG_USB_DEVICE
-- cut --

u-boot-omap3-musb.tar.bz2

Steve Sakoman

unread,
Jan 5, 2009, 12:01:22 PM1/5/09
to beagl...@googlegroups.com, Dirk Behme
On Sun, Jan 4, 2009 at 12:52 AM, Dirk Behme <dirk....@googlemail.com> wrote:
>
> TI sent some U-Boot OMAP3 patches to U-Boot mailing list:
>
> http://lists.denx.de/pipermail/u-boot/2009-January/045304.html
>
> As mentioned there, they are for EVM, but should easily (?) be
> adaptable to other OMAP3 boards, too. (by copying stuff from patch
> 08_musb.txt in attachment to beagle config?)
>
> I put the 8 patches mentioned in that mail into a quilt patch series
> (see attachment), maybe it helps you to adapt them for Beagle ;)
>
> Patch series is against Steve's git [1].
>
> I got one reject [2] I fixed manually. There is no
>
> COBJS-$(CONFIG_USB_EHCI_FSL) += usb_ehci_fsl.o
>
> in Steve's git (which should be in sync with mainline). Maybe it comes
> from some U-Boot USB branch merge (?).
>
> So patch series in attachment compiles fine with
>
> omap3_evm_config
> make
>
> but I don't know if it works ;)

I created a branch (omap3-dev-usb) for those who might want to track this:

http://www.sakoman.net/cgi-bin/gitweb.cgi?p=u-boot-omap3.git;a=shortlog;h=refs/heads/omap3-dev-usb

Steve

Atin

unread,
Jan 12, 2009, 4:31:55 PM1/12/09
to Beagle Board
Can we apply the U-boot musb gadget support patch[1] from
http://elinux.org/U-boot_musb_gadget_support to the u-boot-dev-usb
branch? It would be an improvement over what we have right now
(nothing). We still need to make the TWL4030 initialization code
common between host and gadget modes, but that would be easier to do
once all the patches are in one place.

Thanks,

-Atin

[1] http://elinux.org/upload/f/fb/Musb-gadget-beagle.patch

Atin

unread,
Jan 12, 2009, 4:33:26 PM1/12/09
to Beagle Board
I meant the omap3-dev-usb branch of course.

-Atin

On Jan 12, 4:31 pm, Atin <atin.malav...@gmail.com> wrote:
> Can we apply the U-boot musb gadget support patch[1] fromhttp://elinux.org/U-boot_musb_gadget_supportto the u-boot-dev-usb

Steve Sakoman

unread,
Jan 13, 2009, 12:33:26 PM1/13/09
to beagl...@googlegroups.com
On Mon, Jan 12, 2009 at 1:31 PM, Atin <atin.m...@gmail.com> wrote:
>
> Can we apply the U-boot musb gadget support patch[1] from
> http://elinux.org/U-boot_musb_gadget_support to the u-boot-dev-usb
> branch? It would be an improvement over what we have right now
> (nothing). We still need to make the TWL4030 initialization code
> common between host and gadget modes, but that would be easier to do
> once all the patches are in one place.

Pushed this morning:

Reply all
Reply to author
Forward
0 new messages