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

33 lines
922 B
Plaintext
Raw Normal View History

board: simplify atngw100 support Minimize atngw100_defconfig, remove atngw100-base_defconfig, and remove the target skeleton and device table. Instead of having complete copies of new target skeletons (making them hard to maintain), we should just have a post-build script that adds/removes/tweaks the existing target skeleton. Moreover, most of the tweaks in this target skeleton were for specific packages, but the policy now is that board defconfig should just build a basic root filesystem with Busybox, and let the user select whichever set of packages (s)he wants. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-12-05 21:53:01 +01:00
# Architecture
Add stk1002 target
2007-07-29 09:15:35 +02:00
BR2_avr32=y
configs: lock kernel version for atngw100_defconfig The 3.10.x kernels fail to build with the following message: vsprintf.c:(.text+0x17e0): relocation truncated to fit: R_AVR32_16N_PCREL against symbol `_ctype' defined in .text section in lib/lib.a(ctype.o) While this is most likely a toolchain issue, but since AVR32 isn't a well-maintained architecture, there's not much we can do. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2013-08-07 11:54:14 +02:00
# Lock down kernel headers version, to match the kernel version used
# below.
atngw100_defconfig: use BR2_KERNEL_HEADERS_VERSION to specify kernel headers No functional change, but the HEADERS_3_9 option will go away by the time 3.9 is no longer supported, possibly leading to breakage. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-10-04 22:06:52 +02:00
BR2_KERNEL_HEADERS_VERSION=y
BR2_DEFAULT_KERNEL_VERSION="3.9.11"
defconfigs: add the _AT_LEAST_X_Y headers options Since commit 2a5cf5e (check kernel headers version), we also need to specify the series of the custom kernel headers version. The defconfigs file that define such a custom kernel headers version now fail to build. Add the required _AT_LEAST_X_Y options to those config files. Done with this (convoluted but very fast, uch faster ythan manual editing!) rule: for f in $( git grep -l BR2_DEFAULT_KERNEL_VERSION=\"3 ); do grep -E '^BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_' "${f}" >/dev/null && continue sed -r -e '/^(BR2_DEFAULT_KERNEL_VERSION="3\.([[:digit:]]+).*")$/s//\1\nBR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_\2=y/' "${f}" done Only kernels >= 3.0 need those options in the defconfig, since the default for 2.6.x kernels is correct (selects _AT_LEAST_2_6), and the default is not saved in a defconfig. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-03-08 00:25:06 +01:00
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_9=y
configs: lock kernel version for atngw100_defconfig The 3.10.x kernels fail to build with the following message: vsprintf.c:(.text+0x17e0): relocation truncated to fit: R_AVR32_16N_PCREL against symbol `_ctype' defined in .text section in lib/lib.a(ctype.o) While this is most likely a toolchain issue, but since AVR32 isn't a well-maintained architecture, there's not much we can do. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2013-08-07 11:54:14 +02:00
board: simplify atngw100 support Minimize atngw100_defconfig, remove atngw100-base_defconfig, and remove the target skeleton and device table. Instead of having complete copies of new target skeletons (making them hard to maintain), we should just have a post-build script that adds/removes/tweaks the existing target skeleton. Moreover, most of the tweaks in this target skeleton were for specific packages, but the policy now is that board defconfig should just build a basic root filesystem with Busybox, and let the user select whichever set of packages (s)he wants. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-12-05 21:53:01 +01:00
# Filesystems
updates and additions for avr32 arch
2008-03-06 19:59:14 +01:00
BR2_TARGET_ROOTFS_JFFS2=y
BR2_TARGET_ROOTFS_JFFS2_FLASH_128=y
BR2_TARGET_ROOTFS_JFFS2_PAGESIZE=0x1000
BR2_TARGET_ROOTFS_JFFS2_EBSIZE=0x20000
BR2_TARGET_ROOTFS_JFFS2_NOCLEANMARKER=y
BR2_TARGET_ROOTFS_JFFS2_BE=y
Add stk1002 target
2007-07-29 09:15:35 +02:00
BR2_TARGET_ROOTFS_TAR=y
updates and additions for avr32 arch
2008-03-06 19:59:14 +01:00
BR2_TARGET_ROOTFS_TAR_NONE=y
Add stk1002 target
2007-07-29 09:15:35 +02:00
board: simplify atngw100 support Minimize atngw100_defconfig, remove atngw100-base_defconfig, and remove the target skeleton and device table. Instead of having complete copies of new target skeletons (making them hard to maintain), we should just have a post-build script that adds/removes/tweaks the existing target skeleton. Moreover, most of the tweaks in this target skeleton were for specific packages, but the policy now is that board defconfig should just build a basic root filesystem with Busybox, and let the user select whichever set of packages (s)he wants. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-12-05 21:53:01 +01:00
# Bootloader
Add some robustness to linux configuration
2008-03-29 15:09:22 +01:00
BR2_TARGET_UBOOT=y
BR2_TARGET_UBOOT_BOARDNAME="atngw100"
configs: update boards to u-boot custom version option Some board configs where left out of the u-boot custom version migration, so do it otherwise they'll just pull the latest version which might not work and brick the device. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-05-07 02:34:49 +02:00
BR2_TARGET_UBOOT_CUSTOM_VERSION=y
BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2010.09"
Add stk1002 target
2007-07-29 09:15:35 +02:00
configs: lock kernel version for atngw100_defconfig The 3.10.x kernels fail to build with the following message: vsprintf.c:(.text+0x17e0): relocation truncated to fit: R_AVR32_16N_PCREL against symbol `_ctype' defined in .text section in lib/lib.a(ctype.o) While this is most likely a toolchain issue, but since AVR32 isn't a well-maintained architecture, there's not much we can do. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2013-08-07 11:54:14 +02:00
# Kernel. Locked to 3.9.x, because 3.10.x fails to build with
# relocation truncated to fit: R_AVR32_16N_PCREL against symbol
# `_ctype'
board: simplify atngw100 support Minimize atngw100_defconfig, remove atngw100-base_defconfig, and remove the target skeleton and device table. Instead of having complete copies of new target skeletons (making them hard to maintain), we should just have a post-build script that adds/removes/tweaks the existing target skeleton. Moreover, most of the tweaks in this target skeleton were for specific packages, but the policy now is that board defconfig should just build a basic root filesystem with Busybox, and let the user select whichever set of packages (s)he wants. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-12-05 21:53:01 +01:00
BR2_LINUX_KERNEL=y
configs: lock kernel version for atngw100_defconfig The 3.10.x kernels fail to build with the following message: vsprintf.c:(.text+0x17e0): relocation truncated to fit: R_AVR32_16N_PCREL against symbol `_ctype' defined in .text section in lib/lib.a(ctype.o) While this is most likely a toolchain issue, but since AVR32 isn't a well-maintained architecture, there's not much we can do. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2013-08-07 11:54:14 +02:00
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.9.11"
board: simplify atngw100 support Minimize atngw100_defconfig, remove atngw100-base_defconfig, and remove the target skeleton and device table. Instead of having complete copies of new target skeletons (making them hard to maintain), we should just have a post-build script that adds/removes/tweaks the existing target skeleton. Moreover, most of the tweaks in this target skeleton were for specific packages, but the policy now is that board defconfig should just build a basic root filesystem with Busybox, and let the user select whichever set of packages (s)he wants. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-12-05 21:53:01 +01:00
BR2_LINUX_KERNEL_DEFCONFIG="atngw100"
Reference in New Issue Copy Permalink