On 2016-11-03 15:22, Robert Nelson wrote:
On Thu, Nov 3, 2016 at 9:18 AM, Gary Thomas <[email protected]> wrote:
On 2016-11-03 15:11, Robert Nelson wrote:
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
Going forward, it will be consistent..
microSD = ti mmc1 port -> mmc0 kernel
eMMC = ti mmc2 port -> mmc1 kernel
What does "going forward" mean? I'm not seeing this, using
the latest Debian+U-Boot
What you've outlined above would be ideal, I'm just curious
how to get it.
Well let's see:
I merged it into our tree on Jul 19, 2016, at tag: 4.4.15-ti-r37
If your running something older then just:
cd /opt/scripts/tools/ ; git pull ; sudo ./update_kernel.sh
That's fine and good, but I can't test it running eMMC only (no SD)
as the image can't be flashed to my (revA) board that only
has 2GB eMMC, so I can't really test anything using these
tools :-(
Reverting the previously mentioned change does make things
work for me though.
--
------------------------------------------------------------
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/b6cfbb49-aab4-6f4d-d0c5-3be600d09ae3%40mlbassoc.com.
For more options, visit https://groups.google.com/d/optout.
