For legacy reasons, keystone2 had kind of stayed completely seperated from the rest of the TI SoC families. This makes no sense since there are a lot of common definitions that can be reused between all SoC configuration allowing for a consistent user experience.
So make keystone2 follow the rest of the TI SoCs based on OMAP architecture as well. Test log: K2H: http://pastebin.ubuntu.com/11888160/ (using https://patchwork.ozlabs.org/patch/440665/) I have no other platform to verify on. Series based on master 4905dfc65d9a Merge branch 'master' of git://git.denx.de/u-boot-spi Nishanth Menon (3): configs: split ti_armv7_common into a omap generic header configs: rename ks2_evm into ti_armv7_keystone2 configs: ti_armv7_keystone2: start using armv7_common include/configs/am43xx_evm.h | 2 +- include/configs/k2e_evm.h | 4 +- include/configs/k2hk_evm.h | 4 +- include/configs/k2l_evm.h | 4 +- include/configs/ti_am335x_common.h | 2 +- include/configs/ti_armv7_common.h | 31 ++++---------- .../configs/{ks2_evm.h => ti_armv7_keystone2.h} | 50 +++++++--------------- include/configs/ti_armv7_omap.h | 49 +++++++++++++++++++++ include/configs/ti_omap3_common.h | 2 +- include/configs/ti_omap4_common.h | 2 +- include/configs/ti_omap5_common.h | 2 +- 11 files changed, 81 insertions(+), 71 deletions(-) rename include/configs/{ks2_evm.h => ti_armv7_keystone2.h} (90%) create mode 100644 include/configs/ti_armv7_omap.h -- 2.1.4 _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot