On Tue, Sep 16, 2014 at 05:51:04PM +0200, Stefan Herbrechtsmeier wrote:
At the moment the boot loader use a common configuration for all Gumstix Overo expansion boards. This also includes configuration of all inputs and outputs even if they aren't used by the boot loader. Because the Overo module could be used on foreign expansion boards with different configurations this could lead to problems. Split the configuration into a Overo module and expansion board part. The expansion board configuration is skipped if a foreign expansion board is detected. This enables a foreign expansion board to use the common boot loader without any modifications. It could load a specific device tree by saving the expansion name in the EEPROM.
Additionally fix some errors in the environment configuration and add USB host support.
The series is only tested on a foreign expansion boards. It would be nice if somebody could test it on an expansion board with network support.
Stefan Herbrechtsmeier (5): omap3: overo: Fix fdtfile test omap3: overo: Call bootm only after successful nand read omap3: overo: Move ethernet setup to board_eth_init function omap3: overo: Separate module and expansion board MUX configuration omap3: overo: Add usb host support
board/overo/overo.c | 137 ++++++++++++++++++++++++++++---------- board/overo/overo.h | 150 ++++++++++++++++++++++-------------------- include/configs/omap3_overo.h | 15 ++++- 3 files changed, 195 insertions(+), 107 deletions(-)
For the record, I plan to take 2, 3, 4 and 5 for the next merge but 1/5 is clearly a bugfix. Thanks!