* Pali Rohár <pali.rohar@xxxxxxxxx> [141026 15:24]: > On Sunday 26 October 2014 22:55:48 Pavel Machek wrote: > > > > I have root prepared on /dev/mmcblk0p6. I tried 3.17 with > > > > rx51_defconfig, but no, it refuses to mount it. > > > > > > > > VFS: Cannot open root device "mmcblk0p6" or ....: error > > > > -19. > > > > > > > > And then it proceeds to list mmcblk0p6 as one of available > > > > options > > > > > > > > :-(. > > > > > > > > Ideas welcome. > > > > > > Try to add rootdelay=30 or rootwait to kernel cmdline. > > > > I had rootdelay=3. Will try rootwait... no change. This is > > v3.17 with rx51_defconfig. CONFIG_MACH_NOKIA_RX51=y => device > > tree will not be used AFAICT. > > > > Now I'm back at 3.14 without device tree; same setup works > > there. I tried disabling RX51 support in 3.14 (to make it > > boot using device tree) but that did not work. > > Pavel > > I remember that there was some problem with initializing mmc > device. Sometimes something failed and reading from eMMC was not > possible. Try to boot kernel from uboot. Maybe it can help. Would be nice to have both the USB and the MMC issues sorted out in the mainline kernel naturally and get rid of any bootloader dependencies. I think the USB issue because usb_gadget_probe_driver() bails out with -ENODEV before the USB controller is found. Felipe, got any ideas how to fix this to work with -EPROBE_DEFER? Should this get called only from the USB controller probe? 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
