Re: [U-Boot] [Patch v2] omap3: overo: Select fdtfile for expansion board

2014-06-10 Thread Ash Charles
On Tue, Jun 10, 2014 at 11:06 AM, Stefan Herbrechtsmeier wrote: > You could use an environment file next to the u-boot image. Good point. ... > Ok, but please use the GUMSTIX_NO_EEPROM case and leave the default empty or > at least check the vendor id. This allows foreign vendors to use the > upst

Re: [U-Boot] [Patch v2] omap3: overo: Select fdtfile for expansion board

2014-06-10 Thread Stefan Herbrechtsmeier
Am 10.06.2014 19:17, schrieb Ash Charles: On Tue, Jun 10, 2014 at 12:30 AM, Stefan Herbrechtsmeier wrote: Why you set the 'expansionname' to 'tobi' for unknown (maybe foreign) expansion boards? 1. We need some sort of default otherwise people's boards that either don't have an eeprom or don't

Re: [U-Boot] [Patch v2] omap3: overo: Select fdtfile for expansion board

2014-06-10 Thread Ash Charles
On Tue, Jun 10, 2014 at 12:30 AM, Stefan Herbrechtsmeier wrote: > Why you set the 'expansionname' to 'tobi' for unknown (maybe foreign) > expansion boards? 1. We need some sort of default otherwise people's boards that either don't have an eeprom or don't have board data set in the eeprom will sto

Re: [U-Boot] [Patch v2] omap3: overo: Select fdtfile for expansion board

2014-06-10 Thread Stefan Herbrechtsmeier
Am 09.06.2014 22:47, 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 ava

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

2014-06-09 Thread 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 th