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

28 lines
836 B
Plaintext
Raw Normal View History

configs: add a DT-enabled Raspberry Pi defconfig This is an example of a Device-Tree-enabled Raspberry Pi defconfig. We have to use a 3.18-based kernel for that, but there are a few limitations: - we can not use the minimalist RPi defconfig bundled with the kernel, namely bcmrpi_quick_defconfig, because it is not DT-enabled, and sets CONFIG_ARM_PATCH_PHYS_VIRT to 'n', which prompts a value for CONFIG_PHYS_OFFSET, as it as no default for the bcm familly; - most importantly, the rpi-3.18.y branch is constantly rebased, so there is no guarantee that the sha1 I use today will still be usable in the long term. Using the name of hte branch is not better either. So, we bundle our own DT-enabled linux defconfig that is based on bcmrpi_quick_defconfig, with just CONFIG_ARM_PATCH_PHYS_VIRT set and the Device TRee enabled. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-01-10 14:14:57 +01:00
BR2_arm=y
BR2_arm1176jzf_s=y
configs/raspberrypi_dt: update and fix our defconfig Lock to 3.18 headers; add comment about installing DTBs; bump kernel sha1. Reported-by: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-02-27 23:18:54 +01:00
configs: add a DT-enabled Raspberry Pi defconfig This is an example of a Device-Tree-enabled Raspberry Pi defconfig. We have to use a 3.18-based kernel for that, but there are a few limitations: - we can not use the minimalist RPi defconfig bundled with the kernel, namely bcmrpi_quick_defconfig, because it is not DT-enabled, and sets CONFIG_ARM_PATCH_PHYS_VIRT to 'n', which prompts a value for CONFIG_PHYS_OFFSET, as it as no default for the bcm familly; - most importantly, the rpi-3.18.y branch is constantly rebased, so there is no guarantee that the sha1 I use today will still be usable in the long term. Using the name of hte branch is not better either. So, we bundle our own DT-enabled linux defconfig that is based on bcmrpi_quick_defconfig, with just CONFIG_ARM_PATCH_PHYS_VIRT set and the Device TRee enabled. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-01-10 14:14:57 +01:00
BR2_TARGET_GENERIC_GETTY_PORT="tty1"
configs/raspberrypi_dt: update and fix our defconfig Lock to 3.18 headers; add comment about installing DTBs; bump kernel sha1. Reported-by: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-02-27 23:18:54 +01:00
configs/raspberrypi: update the DT-enabled config Update to the latest stable kernel version; build an in-tree DTB; use a in-tree defconfig; enable C++ (to match what we have in the non-DT variant); do not install DTB overlays (this minimalist config does not make use of them). Generate the DTBs for both the "original" variant (A and B) and the "Plus" variant (A+ and B+). Drop our custom linux defconfig file now we use an in-tree one. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Floris Bos <bos@je-eigen-domein.nl> Cc: Pascal de Bruijn <pmjdebruijn@pcode.nl> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-06-30 00:07:42 +02:00
# Lock to 4.0 headers as the RPi kernel stable tree is
# based off the 4.0 branch
configs/raspberrypi_dt: update and fix our defconfig Lock to 3.18 headers; add comment about installing DTBs; bump kernel sha1. Reported-by: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-02-27 23:18:54 +01:00
BR2_KERNEL_HEADERS_VERSION=y
configs/raspberrypi: update the DT-enabled config Update to the latest stable kernel version; build an in-tree DTB; use a in-tree defconfig; enable C++ (to match what we have in the non-DT variant); do not install DTB overlays (this minimalist config does not make use of them). Generate the DTBs for both the "original" variant (A and B) and the "Plus" variant (A+ and B+). Drop our custom linux defconfig file now we use an in-tree one. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Floris Bos <bos@je-eigen-domein.nl> Cc: Pascal de Bruijn <pmjdebruijn@pcode.nl> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-06-30 00:07:42 +02:00
BR2_DEFAULT_KERNEL_VERSION="4.0.6"
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_0=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
configs/raspberrypi_dt: update and fix our defconfig Lock to 3.18 headers; add comment about installing DTBs; bump kernel sha1. Reported-by: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-02-27 23:18:54 +01:00
configs: add a DT-enabled Raspberry Pi defconfig This is an example of a Device-Tree-enabled Raspberry Pi defconfig. We have to use a 3.18-based kernel for that, but there are a few limitations: - we can not use the minimalist RPi defconfig bundled with the kernel, namely bcmrpi_quick_defconfig, because it is not DT-enabled, and sets CONFIG_ARM_PATCH_PHYS_VIRT to 'n', which prompts a value for CONFIG_PHYS_OFFSET, as it as no default for the bcm familly; - most importantly, the rpi-3.18.y branch is constantly rebased, so there is no guarantee that the sha1 I use today will still be usable in the long term. Using the name of hte branch is not better either. So, we bundle our own DT-enabled linux defconfig that is based on bcmrpi_quick_defconfig, with just CONFIG_ARM_PATCH_PHYS_VIRT set and the Device TRee enabled. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-01-10 14:14:57 +01:00
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_GIT=y
raspberrypi: bump raspberrypi_dt_defconfig kernel This brings the raspberrypi_dt_defconfig up to the same kernel used by the raspberrypi2_defconfig. Also changed the git URL to use HTTP for consistency. Signed-off-by: Frank Hunleth <fhunleth@troodon-software.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-04-29 15:36:44 +02:00
BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/raspberrypi/linux.git"
configs/raspberrypi: update the DT-enabled config Update to the latest stable kernel version; build an in-tree DTB; use a in-tree defconfig; enable C++ (to match what we have in the non-DT variant); do not install DTB overlays (this minimalist config does not make use of them). Generate the DTBs for both the "original" variant (A and B) and the "Plus" variant (A+ and B+). Drop our custom linux defconfig file now we use an in-tree one. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Floris Bos <bos@je-eigen-domein.nl> Cc: Pascal de Bruijn <pmjdebruijn@pcode.nl> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-06-30 00:07:42 +02:00
BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="f90f981770e3ac8506dc84c9cd01471faaa0b0c2"
BR2_LINUX_KERNEL_USE_DEFCONFIG=y
BR2_LINUX_KERNEL_DEFCONFIG="bcmrpi"
configs: add a DT-enabled Raspberry Pi defconfig This is an example of a Device-Tree-enabled Raspberry Pi defconfig. We have to use a 3.18-based kernel for that, but there are a few limitations: - we can not use the minimalist RPi defconfig bundled with the kernel, namely bcmrpi_quick_defconfig, because it is not DT-enabled, and sets CONFIG_ARM_PATCH_PHYS_VIRT to 'n', which prompts a value for CONFIG_PHYS_OFFSET, as it as no default for the bcm familly; - most importantly, the rpi-3.18.y branch is constantly rebased, so there is no guarantee that the sha1 I use today will still be usable in the long term. Using the name of hte branch is not better either. So, we bundle our own DT-enabled linux defconfig that is based on bcmrpi_quick_defconfig, with just CONFIG_ARM_PATCH_PHYS_VIRT set and the Device TRee enabled. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-01-10 14:14:57 +01:00
BR2_LINUX_KERNEL_ZIMAGE=y
configs/raspberrypi_dt: update and fix our defconfig Lock to 3.18 headers; add comment about installing DTBs; bump kernel sha1. Reported-by: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-02-27 23:18:54 +01:00
configs/raspberrypi: update the DT-enabled config Update to the latest stable kernel version; build an in-tree DTB; use a in-tree defconfig; enable C++ (to match what we have in the non-DT variant); do not install DTB overlays (this minimalist config does not make use of them). Generate the DTBs for both the "original" variant (A and B) and the "Plus" variant (A+ and B+). Drop our custom linux defconfig file now we use an in-tree one. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Floris Bos <bos@je-eigen-domein.nl> Cc: Pascal de Bruijn <pmjdebruijn@pcode.nl> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-06-30 00:07:42 +02:00
# Build the DTBs for A/B and A+/B+ from the kernel sources
BR2_LINUX_KERNEL_DTS_SUPPORT=y
BR2_LINUX_KERNEL_INTREE_DTS_NAME="bcm2708-rpi-b bcm2708-rpi-b-plus"
configs: add a DT-enabled Raspberry Pi defconfig This is an example of a Device-Tree-enabled Raspberry Pi defconfig. We have to use a 3.18-based kernel for that, but there are a few limitations: - we can not use the minimalist RPi defconfig bundled with the kernel, namely bcmrpi_quick_defconfig, because it is not DT-enabled, and sets CONFIG_ARM_PATCH_PHYS_VIRT to 'n', which prompts a value for CONFIG_PHYS_OFFSET, as it as no default for the bcm familly; - most importantly, the rpi-3.18.y branch is constantly rebased, so there is no guarantee that the sha1 I use today will still be usable in the long term. Using the name of hte branch is not better either. So, we bundle our own DT-enabled linux defconfig that is based on bcmrpi_quick_defconfig, with just CONFIG_ARM_PATCH_PHYS_VIRT set and the Device TRee enabled. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-01-10 14:14:57 +01:00
BR2_PACKAGE_RPI_FIRMWARE=y
configs/raspberrypi: update the DT-enabled config Update to the latest stable kernel version; build an in-tree DTB; use a in-tree defconfig; enable C++ (to match what we have in the non-DT variant); do not install DTB overlays (this minimalist config does not make use of them). Generate the DTBs for both the "original" variant (A and B) and the "Plus" variant (A+ and B+). Drop our custom linux defconfig file now we use an in-tree one. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Floris Bos <bos@je-eigen-domein.nl> Cc: Pascal de Bruijn <pmjdebruijn@pcode.nl> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-06-30 00:07:42 +02:00
# BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS is not set
Reference in New Issue Copy Permalink