Re: Beagle can't mount rootfs from MMC after regulator updates
Hi, On Tue, 24 Mar 2009, Paul Walmsley wrote: > The BeagleBoard rev B4 here can't mount its root filesystem from MMC after > 3fe326511c66ab842ef0a09a1f4c564b1a8beecf, "mmc-twl4030 uses regulator > framework". This is with omap3_beagle_defconfig and rootwait in the > kernel command line. Kernel hangs after: > > Waiting for root device /dev/mmcblk0p2... Turns out this is due to missing CONFIG_REGULATOR, CONFIG_REGULATOR_TWL4030 in the defconfigs; patch coming shortly. - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Beagle can't mount rootfs from MMC after regulator updates
Hi, The BeagleBoard rev B4 here can't mount its root filesystem from MMC after 3fe326511c66ab842ef0a09a1f4c564b1a8beecf, "mmc-twl4030 uses regulator framework". This is with omap3_beagle_defconfig and rootwait in the kernel command line. Kernel hangs after: Waiting for root device /dev/mmcblk0p2... Will look at this in a few hours unless Dave beats me to it ;-) - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html