On 2016-11-03 14:58, Robert Nelson wrote:
On Thu, Nov 3, 2016 at 8:55 AM, Gary Thomas <[email protected]> wrote:
On 2016-11-03 14:38, Robert Nelson wrote:
On Thu, Nov 3, 2016 at 7:26 AM, Gary Thomas <[email protected]> wrote:
On my BeagleBoneBlack with a system installed in eMMC, I get
different device names for the MMC devices, depending on whether
or not there is a SD card installed at boot time.
With SD card installed:
MMC/SD slot = mmcblk0
eMMC = mmcblk1
Without SD card installed (at boot):
MMC/SD slot = mmcblk1 if inserted after boot
eMMC = mmcblk0
Is there some way to configure this to be consistent? i.e.
MMC/SD slot = mmcblk0 (regardless of the presence of an SD card)
eMMC = mmcblk1
which matches the device enumeration in U-Boot?
If not, what's the rationale behind the madness?
First valid device probed is mmc0...
This changed in v4.5.x/v4.6.x timeframe and we backported it to v4.4.x.
Do you recall the changeset, in case I'd like to undo it? I'm trying
to make the BBB behave like all the other platforms I support.
Thanks for any pointers
For our "v4.4.x-ti" just revert:
https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-4.4.y/patches/x15/fixes/0004-mmc-block-Use-the-mmc-host-device-index-as-the-mmcbl.patch
On mainline (v4.5.x+): either get use to it, or revert:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/mmc/core?id=520bd7a8b4152aacfbd34eb7f7a447354b631039
&
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/mmc?id=9aaf3437aa72ed5370bf32c99580a3fa2c330e3d
Thanks, I'll investigate these changes.
Based on the comment "first valid device probed", is there any way to
force the eMMC to be the first valid device (I might be able to live with
the fact that U-Boot sees the eMMC as dev 1 but Linux as dev 0 if it was
always consistent).
Again, thanks for any ideas/pointers
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/9fefd26b-9372-c87c-e26b-1139d4c690a3%40mlbassoc.com.
For more options, visit https://groups.google.com/d/optout.