Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
After changing from kernel 3.5 to 3.6, the mmc device is no longer detected.
On kernel 3.5, dmesg usually reports something like:
[ 3.398773] mmc0: host does not support reading read-only switch.
[ 3.400909] mmc0: new high speed SDHC card at address 0007
[ 3.408752] mmcblk0: mmc0:0007 SD16G 14.9 GiB
[ 3.411529] mmcblk0: p1 p2 p3
However, after changing the recipe to get kernel 3.6 from
git://www.sakoman.com/git/linux.git;branch=omap-3.6;protocol=git the mmc
device is no longer detected.
For the kernel 3.6 dmesg output related to mmc is:
[ 2.764434] omap_hsmmc omap_hsmmc.0: Failed to get debounce clk
[ 2.770996] omap_hsmmc omap_hsmmc.0: unable to obtain RX DMA engine
[ 2.779144] omap_hsmmc omap_hsmmc.1: Failed to get debounce clk
[ 2.785461] omap_hsmmc omap_hsmmc.1: unable to obtain RX DMA engine
Does anyone have a workaround for this? Some other posts on the interwebs
suggest it is related to CONFIG_REGULATOR_DUMMY, but I do not see any
regulator failure cases reported in dmesg.
View this message in context: http://gumstix.8.n6.nabble.com/Kernel-3-6-and-SD-card-not-working-tp4966819.html
Sent from the Gumstix mailing list archive at Nabble.com.