[U-Boot] [PATCH 0/5] Enhance support for BeagleBone Black

[Justin Waters]

Tom,

On Tue, 2013-07-09 at 15:47 -0400, Tom Rini wrote:
> On Tue, Jul 09, 2013 at 03:00:05PM -0400, Justin Waters wrote:
> 
> > There are a number of differences between the BeagleBone Black
> > and other AM335x boards that require some modification of the
> > default AM335x EVM configuration. In particular, it lacks NAND
> > flash, has multiple MMC interfaces, and can store its environment
> > in an unused eMMC partition.
> > 
> > The following patch set improves the out-of-box experience on the
> > BeagleBone Black without impacting the existing AM335x boards.
> 
> So, I was wondering how to best handle this last week.  The problem is
> that most of what you've done for BeagleBone Black also fits with
> BeagleBone White and EVM SK.  Or all 3 may be best served (depending on
> the use case) with env as a file on FAT.
> 

I tried to factor out the work as best I could. For instance, the Black
is the only board with eMMC (to my knowledge), so I wanted to treat that
similiarly to the SPI flash- if we have the ability to store the
environment in a read/write fashion, I'd like to take advantage of it.

The multiple SD card boot changes are generic, though- they should work
on any of the AM335x boards without any modification. So something like
the EVM will function out of the box. I have one on hand- I can give it
a try.

My personal preference is to provide different targets for each of the
flavors (evm, sk, bone, boneblack). The boards.cfg file provides a
really nice mechanism for supporting similar platforms, so I tried to
separate my changes to allow for that. Then again, I'm not the one
maintaining these boards, and there's already an EEPROM on the board for
differentiating between the different platforms, so perhaps multiple
configurations are overkill.

In any event, let me know if you have any preferences. I'm certainly
open to suggestions, and I have other AM335x platforms to test on as
well.

-Justin