Once Booted from MMC, eMMC not found

[Glen Barber]

In theory, no.  Once mmc0 is recognized, any additional mmc devices
should also be available.  :(

Glen

On Thu, Jul 02, 2015 at 07:35:36AM -0400, Andrew Gervase wrote:
> Thank  you for your reply, Glen:  To me, the script is optional.  All it does is partition and newfs a slice on mmc1, and then copies everything via tar from mmc0 to mmc1.  
> 
> My problem is, mmc1 doesn’t exist once the kernel loads.  I was wondering if there is a module that needs to be loaded or compiled into the kernel to make sure the eMMC (mmc1) is recognized.  
> 
> Andy ideas?
> 
> —Andy
> 
> > On Jul 2, 2015, at 01:06, Glen Barber <gjb at FreeBSD.org> wrote:
> > 
> > On Thu, Jul 02, 2015 at 05:03:06AM +0000, Glen Barber wrote:
> >> On Wed, Jul 01, 2015 at 09:47:51PM -0700, agervase wrote:
> >>> I was finally able to get my Beaglebone Black to boot from FreeBSD
> >>> 10.1-RELEASE, however the copy-to-emmc.sh script fails because mmc1 is not
> >>> found.  I'd very much like my BBB to boot automatically, preferably from the
> >>> eMMC, however I'll take what I can!
> >>> 
> >>> Please forgive me in advance if this question has already been addressed, as
> >>> my searches have yielded nothing helpful thus far.
> >>> 
> >>> My greatest appreciation in advance,
> >> 
> >> Please wait until next week when several changes/fixes are committed to
> >> the stable/10 branch that can help with this.
> >> 
> >> Unless you do not have a particular reason to run 10-STABLE, you can try
> >> the 11-CURRENT snapshots.  See the mailing list archives for
> >> freebsd-snapshots@ for details.
> >> 
> > 
> > Bah, actually I think what I suggested is orthogonal to your issue,
> > since I just realized you mentioned a script I am unaware of.
> > 
> > Sorry for any confusion.
> > 
> > Glen
> > 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-arm/attachments/20150702/7bb1bc9c/attachment.bin>