Created
October 31, 2016 22:16
-
-
Save RobertCNelson/f137dee9139f954bbf0a187127b2e5db to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| debian@beaglebone:~$ uname -r | |
| 4.8.5-bone2 | |
| debian@beaglebone:~$ dmesg | grep mmc | |
| [ 3.964503] omap_hsmmc 48060000.mmc: Got CD GPIO | |
| [ 4.156124] mmc1: new high speed MMC card at address 0001 | |
| [ 4.156819] mmcblk1: mmc1:0001 S10004 3.56 GiB | |
| [ 4.157080] mmcblk1boot0: mmc1:0001 S10004 partition 1 4.00 MiB | |
| [ 4.157299] mmcblk1boot1: mmc1:0001 S10004 partition 2 4.00 MiB | |
| [ 4.158309] mmcblk1: p1 | |
| [ 15.672661] EXT4-fs (mmcblk1p1): mounted filesystem with ordered data mode. Opts: (null) | |
| [ 16.724173] EXT4-fs (mmcblk1p1): re-mounted. Opts: errors=remount-ro |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Like I said, this is what I noticed too and for a while assumed that we finally had stable mmc (host and blkdev) numbering. However, when I looked into the driver I didn't — and still don't — see anything suggesting this is true. I'm not sure what's going on here but since I didn't want to risk random breakage I fixed it properly™ ;-)
You can find patch for that here, along with a really trivial one that fixes the same for SPI, and DT patches to actually assign the ids.