[U-Boot] [PATCH] omap3: overo: Select fdtfile for expansion board

[Tom Rini]

On Sat, Jun 07, 2014 at 04:29:27PM +0200, Stefan Herbrechtsmeier wrote:
> Am 06.06.2014 20:37, schrieb Ash Charles:
> >The u-boot Overo board actually supports both Overo (OMAP35xx)
> >and Overo Storm (AM/DM37xx) COMs with a range of different expansion
> >boards.  This provides a mechanism to select the an appropriate device
> >tree file based on the processor version and, if available, the
> >expansion board ID written on the expansion board EEPROM. To match the
> >3.15+ kernels, fdtfile names have this format:
> >  "omap3-overo[-storm]-<expansion board name>.dtb"
[snip]
> >+        snprintf(fdtname, ARRAY_SIZE(fdtname),  "omap3-overo%s-%s.dtb",
> >+                 is_storm ? "-storm" : "", expansion_name);
> >+        setenv("fdtfile", fdtname);
> This makes it impossible to save the fdtfile in the environment.
> 
> Why you don't use an command from the environment and add a
> boardname as you do on the duovero?

In this case it might be harder to do this in a shell cmd.  But we
_must_ check for fdtfile being unset and only setenv if not already set.
And then drop fdtfile from the config file.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140607/33a532bc/attachment.pgp>