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 21:14:57 +08:00
|
|
|
BR2_arm=y
|
|
|
|
BR2_arm1176jzf_s=y
|
2015-08-23 04:01:25 +08:00
|
|
|
BR2_ARM_EABIHF=y
|
2015-02-28 06:18:54 +08: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 21:14:57 +08:00
|
|
|
BR2_TARGET_GENERIC_GETTY_PORT="tty1"
|
2016-04-15 16:05:58 +08:00
|
|
|
BR2_SYSTEM_DHCP="eth0"
|
2015-02-28 06:18:54 +08:00
|
|
|
|
2016-02-06 07:06:18 +08:00
|
|
|
# Linux headers same as kernel, a 4.1 series
|
2015-08-14 00:22:49 +08:00
|
|
|
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_1=y
|
2015-06-30 06:07:42 +08:00
|
|
|
|
|
|
|
BR2_TOOLCHAIN_BUILDROOT_CXX=y
|
2015-02-28 06:18:54 +08: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 21:14:57 +08:00
|
|
|
BR2_LINUX_KERNEL=y
|
|
|
|
BR2_LINUX_KERNEL_CUSTOM_GIT=y
|
2015-04-29 21:36:44 +08:00
|
|
|
BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/raspberrypi/linux.git"
|
2016-01-08 04:07:04 +08:00
|
|
|
BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="d33d0293e245badc4ca6ede3984d8bb8ea63cb1a"
|
2015-06-30 06:07:42 +08:00
|
|
|
BR2_LINUX_KERNEL_DEFCONFIG="bcmrpi"
|
2015-02-28 06:18:54 +08:00
|
|
|
|
2016-01-08 04:07:06 +08:00
|
|
|
# Build the DTBs for A/B, A+/B+ and compute module from the kernel sources
|
2015-06-30 06:07:42 +08:00
|
|
|
BR2_LINUX_KERNEL_DTS_SUPPORT=y
|
2016-01-08 04:07:06 +08:00
|
|
|
BR2_LINUX_KERNEL_INTREE_DTS_NAME="bcm2708-rpi-b bcm2708-rpi-b-plus bcm2708-rpi-cm"
|
2015-06-30 06:07:42 +08: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 21:14:57 +08:00
|
|
|
BR2_PACKAGE_RPI_FIRMWARE=y
|
2015-06-30 06:07:42 +08:00
|
|
|
# BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS is not set
|
2015-12-31 21:28:08 +08:00
|
|
|
|
|
|
|
# Required tools to create the SD image
|
|
|
|
BR2_PACKAGE_HOST_DOSFSTOOLS=y
|
|
|
|
BR2_PACKAGE_HOST_GENIMAGE=y
|
|
|
|
BR2_PACKAGE_HOST_MTOOLS=y
|
|
|
|
|
|
|
|
# Filesystem / image
|
|
|
|
BR2_TARGET_ROOTFS_EXT2=y
|
|
|
|
BR2_TARGET_ROOTFS_EXT2_4=y
|
|
|
|
# BR2_TARGET_ROOTFS_TAR is not set
|
|
|
|
BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi/post-image.sh"
|