Roger, On 07/12/2013 11:15 AM, Roger Quadros wrote: >>> Good idea. I'm currently using a "dirty" local version. I'll try to >>> switch to an officially available version tomorrow. And send you the >>> version/git id. >> >> I updated my U-Boot to the following version: Based on mainline git >> commit ID 225fd8c. Only this patch added: >> >> http://patchwork.ozlabs.org/patch/256702/ >> >> This is needed for USB to work in U-Boot. Otherwise my external USB >> SMSC95xx will not be detected in U-Boot. > > I can only test on beagle-xm (which is also rev. C2) with integrated SMSC ethernet chip > as I don't have an external USB-ethernet adapter. Too bad. This difference in boards makes the tests a bit less meaningful. Is there really no USB-ethernet adapter somewhere in your department (perhaps a non-SMSC95xx might serve as well?)? I might send/order you one if necessary. ;) > The above commit doesn't work well for beagle-xm, Why is this? What does happen? Does U-Boot not boot up to the prompt? Please send me a log. > so my u-boot is on tag v2013.04 > and you don't need that additional patch. > > Can you please retest on it? Thanks. Done, please see below. > You will need to set "usbethaddr" before starting USB else SMSC will not work. > e.g. > setenv usbethaddr A6:66:4D:B0:69:04 I don't have a beagle-xm, only my beable. And my U-Boot network setup is already working, thanks. > Also could you please increase the Linux console message verbosity to debug (8), so that > all kernel messages are visible in the log? If it spits out something more than what you > sent last time then do send it to me. I added "ignore_loglevel" to the cmdline. But I cannot see anything interesting that has not been there before with "debug" as well. > Let's first sort out the beagle-xm problem, then we can see about old beagle. Okay, I tested again with U-Boot v2013.01 plus my SMSC patch. Same problem. NFS booting/mounting hangs at some time. Thanks, Stefan -- 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
