I have a Rev6 BB using a wall wart for power, a powered USB hub and USB
keyboard, mouse, and network dongle.
I've used the guides on the wiki to get started. My first step was to
setup and partition an SD card and install the Angstrom Demo image on
it. I powered up the BB, and everything including USB worked just fine.
After tinkering with that for awhile, I then installed openembedded (on
Ubuntu Hardy) and built the OE console-image. I installed that on the SD
card and everything again worked just fine, including USB.
Feeling pretty confident now, I checked out the most recent kernel I
could find:
git://git2.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6
and used the OE tool chain to build this kernel, starting with "make
CROSS_COMPILE=arm-angstrom-linux-gnueabi- ARCH=arm
omap3_beagle_defconfig". I installed the result as uImage on the SD
card, copied the modules to /lib/modules, booted, and everything worked
just fine, except I had no USB. None.
Ok, too big of a step. I then built what appears to me to be latest
kernel included in OE: "bitbake linux-omap_2.6.29.bb". This downloaded
the same git tree, added some patches, and compiled just fine; I
installed uImage and the modules as before on the SD card and booted it
successfully. But, still no USB.
Dmesg for two kernels that would not bring up USB both had this error:
"
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: ConfigData=0x33 (UTMI-16, HB-ISO Rx (X), SoftConn)
musb_hdrc: MHDRC RTL version 1.400
musb_core_init 1406: reconfigure software for static FIFOs
musb_hdrc musb_hdrc: musb_init_controller failed with status -19
"
But I do not know if it relates to my problem; my build of console-image
and the Angstrom demo did not have this error.
I'm clearly missing or mis-using something. I've tried to compare the
.config files of the various kernels to see if it is a configuration
issue, but there doesn't seem to be anything obvious (to me). It feels
like I'm perhaps missing some patches, but the linux-omap_2.6.29.bb
install included patches, and I sort of thought that the latest git
master would include all necessary patches as of the latest pull.
Googleing the error above hasn't brought up anything that seems useful.
Any hints as to what I am doing wrong?
Thanks,
Peter
You're doing nothing wrong, you're just in a bit of uncharted
territory :) The 2.6.29 kernel is quite new and we don't have
everything working with it yet, that's why it isn't the default yet.
regards,
Koen