summaryrefslogtreecommitdiffstats
path: root/package/gcc/gcc-initial/gcc-initial.hash
diff options
context:
space:
mode:
authorEzequiel GarcĂ­a <ezequiel@vanguardiasur.com.ar>2016-04-15 12:56:05 -0300
committerPeter Korsgaard <peter@korsgaard.com>2016-04-18 23:19:25 +0200
commit5c084e951989ca18db4c36b32021727601cf8422 (patch)
tree99451c1a1cbefd88ea215c57a1709382986ddc1c /package/gcc/gcc-initial/gcc-initial.hash
parent54ec0e2a74a0e3b0f5e5780bca142dfa937f9a99 (diff)
downloadbuildroot-5c084e951989ca18db4c36b32021727601cf8422.tar.gz
buildroot-5c084e951989ca18db4c36b32021727601cf8422.zip
board/minnowboard: Unify Minnowboard and Minnowboard MAX boards
Given Minnowboard and Minnowboard MAX boards are very similar, it's desirable to unify the support for them. This commit does the following: 1) Remove Minnowboard MAX's genimage.cfg, post-build.sh and post-image.sh. These are identical to Minnowboard's. 2) Move Minnowboard MAX's linux config, and rename it. It would be lovely to have a single kernel config file. The kernel size penalty involved in adding support for all the peripherals on both boards is small enough to justify this. However, the original Minnowboard has some GPIO buttons that need to be registered by the kernel. This is not upstreamed, and hence we need to use the yocto v3.8 kernel to have this support. 3) Rename each grub config to grub-{board}.cfg. 4) Modify (the now unique) post-build script to use a different grub config, according to the board. 5) Update both defconfigs, as per the above changes. 6) Finally, update the readme.txt. [Peter: mention MAX in readme title] Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Diffstat (limited to 'package/gcc/gcc-initial/gcc-initial.hash')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud