On Mon, Jul 21, 2014 at 11:38 AM, Michael Welling <mwelling@xxxxxxxxxxx> wrote: > On Mon, Jul 21, 2014 at 12:09:13AM -0700, Tony Lindgren wrote: >> * Michael Welling <mwelling@xxxxxxxxxxx> [140718 07:42]: >> > On Fri, Jul 18, 2014 at 1:38 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: >> > > >> > > Hmm maybe double check your're booting device tree based kernel >> > > instead of legacy machine ID based kernel? The legacy booting should >> > > still work just fine and no changes has been made to it, but it will >> > > get removed shortly. >> > >> > I downloaded the version from the test results and it did boot. >> >> OK that's good to hear. >> >> > These are combining the uImage and dtb. How do you accomplish this? >> >> You need to make sure you have the appended DTB support enabled like >> we do in omap2plus_defconfig: >> >> CONFIG_ARM_APPENDED_DTB=y >> CONFIG_ARM_ATAG_DTB_COMPAT=y >> CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y >> >> Then just cat zImage board.dtb > /tmp/zImage-dtba and run >> mkimage to convert it to a uImage: >> >> $ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 \ >> -n "Linux" -d /tmp/zImage-dtba /tmp/uImage >> > > I actually discovered this and got LCD video working. Now USB host is > not working. The only thing that registers is the OHCI/EHCI hosts. > > root@som3517:~# lsusb > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > > Not sure what the problem is. The USB devices that are plugged in are > powered but never detected. > > Any hints? So I got the USB host to work on boot with additional entries in the devicetree. Documentation/devicetree/bindings/omap-usb-host.txt Though the devices work if plugged in at boot, any time a device is hotplugged then the device is not detected. It is powered very briefly and then off without any kernel messages. So hints from this point would be good. > >> Regards, >> >> Tony -- 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
