Roger, On 04/15/2013 01:20 PM, Roger Quadros wrote: > On Beagle xM Rev. Ax/Bx, the USB power enable GPIO logic is > reversed when compared to other revisions i.e. it is > active high instead of active low. > > Use the beagle_config.usb_pwr_level flag correctly so that > the power regulator can be configured at runtime. > > Signed-off-by: Roger Quadros <rogerq@xxxxxx> I'm currently trying to use an SMSC95xx USB ethernet adapter on the OMAP3 Beagleboard (old one "Beagle Rev C1/C2/C3") via the OMAP EHCI controller. And am testing this by trying to mount the rootfs via NFS. What I see is that the NFS mounting stalls/hangs most of the time quite early in the mount process: [ 6.425689] VFS: Mounted root (nfs filesystem) on device 0:12. [ 6.435485] devtmpfs: mounted [ 6.440002] Freeing unused kernel memory: 384K (c077a000 - c07da000) INIT: version 2.88 booting Starting udev [ 188.311309] nfs: server 10.0.0.152 not responding, still trying [ 188.317687] nfs: server 10.0.0.152 not responding, still trying ... Only very seldom the rootfs can be mounted successfully to the prompt. I'm using latest kernel.org for this (git ID d2b4a646 also tested with v3.10 release). This is with DT-enabled booting and without-DT (same problem). I also tested some older Linux kernel versions and it fails there as well. Only v3.2.40 seems to be able to mount this rootfs via NFS reliably (approx. 10 times success). Is this a known issue on the Beagleboard? Do you have any ideas what might cause such an issue (unreliable USB connection, hangup of NFS mounting)? Any hints/links appretiated. 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
