NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
07144093d4
kumquat-buildroot/configs/minnowboard_max_defconfig

37 lines
941 B
Plaintext
Raw Normal View History

board: add support for Minnowboard MAX Very similar to the older Minnowboard, except that it works with mainline Linux, uses 64bit firmware and a realtek NIC needing firmware. The Linux configuration is based on the configuration fragment on elinux: http://elinux.org/Minnowboard:MinnowMaxLinuxKernel Many thanks to Circuitco for sponsoring a board. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-11-02 21:59:47 +01:00
# Architecture
BR2_x86_64=y
BR2_x86_atom=y
# Misc
BR2_TARGET_GENERIC_GETTY_PORT="ttyS0"
configs/minnowboard_max: configure eth0 through dhcp The minnowboard max board has an ethernet port, so configure it at startup. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-04-15 09:50:08 +02:00
BR2_SYSTEM_DHCP="eth0"
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>
2016-04-15 17:56:05 +02:00
BR2_ROOTFS_POST_BUILD_SCRIPT="board/minnowboard/post-build.sh"
BR2_ROOTFS_POST_IMAGE_SCRIPT="board/minnowboard/post-image.sh"
BR2_ROOTFS_POST_SCRIPT_ARGS="minnowboard-max"
board: add support for Minnowboard MAX Very similar to the older Minnowboard, except that it works with mainline Linux, uses 64bit firmware and a realtek NIC needing firmware. The Linux configuration is based on the configuration fragment on elinux: http://elinux.org/Minnowboard:MinnowMaxLinuxKernel Many thanks to Circuitco for sponsoring a board. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-11-02 21:59:47 +01:00
defconfigs: all use the headers from the kernel For most defconfigs, it was trivial to deduce the kernel version, by just reading the version string, which could be: - a standard upstream version string vX.Y.Z - a non-standard version string, but still containg the standard X.Y.Z Those for which it was not so trivial were those hosted on git tree. Since most were already using a custom linux-headers version, it could be easily deduced from that. It was confirmed by browsing said git trees and check the version there. There are a few cases were there was a mismatch: - microzed: uses a 3.18 kernel, but 3.8 headers; fixed. - xilinx_zc706: uses a 3.14 kernel, but 3.8 headers; fixed. - zedboard: uses a 3.18 kernel, but 3.8 headers; fixed. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-06 00:06:18 +01:00
# Linux headers same as kernel, a 4.4 series
configs/minnowboard_max: bump kernel to version 4.4 And point the readme to wiki.minnowboard.org instead of the legacy elinux.org page. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-01-14 21:40:26 +01:00
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_4=y
board/minnowboard-max: Rework to generate SD card image Let's rework the board and config files to use genimage to generate the SD card image directly. [Peter: add host-mtools for genimage vfat handling] Signed-off-by: Ezequiel García <ezequiel@vanguardiasur.com.ar> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-04-12 07:29:22 +02:00
BR2_PACKAGE_HOST_DOSFSTOOLS=y
BR2_PACKAGE_HOST_GENIMAGE=y
BR2_PACKAGE_HOST_MTOOLS=y
board: add support for Minnowboard MAX Very similar to the older Minnowboard, except that it works with mainline Linux, uses 64bit firmware and a realtek NIC needing firmware. The Linux configuration is based on the configuration fragment on elinux: http://elinux.org/Minnowboard:MinnowMaxLinuxKernel Many thanks to Circuitco for sponsoring a board. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-11-02 21:59:47 +01:00
# Needed for ethernet
BR2_PACKAGE_LINUX_FIRMWARE=y
BR2_PACKAGE_LINUX_FIRMWARE_RTL_8169=y
# Linux kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
configs/minnowboard_max: bump kernel to version 4.4 And point the readme to wiki.minnowboard.org instead of the legacy elinux.org page. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-01-14 21:40:26 +01:00
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.4"
board: add support for Minnowboard MAX Very similar to the older Minnowboard, except that it works with mainline Linux, uses 64bit firmware and a realtek NIC needing firmware. The Linux configuration is based on the configuration fragment on elinux: http://elinux.org/Minnowboard:MinnowMaxLinuxKernel Many thanks to Circuitco for sponsoring a board. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-11-02 21:59:47 +01:00
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
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>
2016-04-15 17:56:05 +02:00
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/minnowboard/linux-4.4.config"
board: add support for Minnowboard MAX Very similar to the older Minnowboard, except that it works with mainline Linux, uses 64bit firmware and a realtek NIC needing firmware. The Linux configuration is based on the configuration fragment on elinux: http://elinux.org/Minnowboard:MinnowMaxLinuxKernel Many thanks to Circuitco for sponsoring a board. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-11-02 21:59:47 +01:00
# Bootloader
BR2_TARGET_GRUB2=y
BR2_TARGET_GRUB2_X86_64_EFI=y
board/minnowboard-max: Rework to generate SD card image Let's rework the board and config files to use genimage to generate the SD card image directly. [Peter: add host-mtools for genimage vfat handling] Signed-off-by: Ezequiel García <ezequiel@vanguardiasur.com.ar> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-04-12 07:29:22 +02:00
# Filesystem image
BR2_TARGET_ROOTFS_EXT2=y
BR2_TARGET_ROOTFS_EXT2_4=y
# BR2_TARGET_ROOTFS_TAR is not set
Reference in New Issue Copy Permalink