I agree that they should be decoupled but I have no other explanation as to why the module (mmc0) would cause a filesystem problem when plugged in. I'm able to see the contents of flash (mmc1) when I boot into the initramfs command prompt. -Mike -----Original Message----- From: Andreas Fenkart [mailto:afenkart@xxxxxxxxx] Sent: Friday, June 10, 2016 3:39 PM To: Michael Eskowitz <MichaelE@xxxxxxxxxxxxxxx> Cc: Tony Lindgren <tony@xxxxxxxxxxx>; linux-omap <linux-omap@xxxxxxxxxxxxxxx> Subject: Re: Bringing up the BRCM43362 on Beaglebone Black Hi, 2016-06-10 19:56 GMT+02:00 Michael Eskowitz <MichaelE@xxxxxxxxxxxxxxx>: > Andreas, Tony, > > Thank you for your help. Unfortunately, I tried changing > > compatible = "ti,omap4-hsmmc"; > > to > > compatible = "ti,am33xx-hsmmc"; > > in the dtb, but the modifications didn't change the end result. > > > When I boot with the module in place I end up in initramfs and when I > insert the module into a booted system I get errors at the console and > the error > > -bash: /bin/dmesg: Input/output error > > when I try and run dmesg. That said, ls is working now and I am able > to list the contents of a directory which I couldn't do before. > > > > Any other suggestions? This is from your initial mail: [ 60.994101] mmcblk0: error -110 sending status command, retrying [ 61.028873] mmcblk0: error -110 sending status command, retrying [ 61.068751] mmcblk0: error -110 sending status command, aborting [ 61.074947] blk_update_request: I/O error, dev mmcblk0, sector 537792 [ 61.081506] blk_update_request: I/O error, dev mmcblk0, sector 537800 [ 61.088018] blk_update_request: I/O error, dev mmcblk0, sector 537808 mmcblk0 is probably your rootfs device. I don't think the mmc layer is the problem here, since mmc1(wifi)/mmc0(flash) should be well decoupled. /Andreas -- 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
