2021-11-06 18:29:55 +01:00
|
|
|
BR2_riscv=y
|
|
|
|
BR2_GLOBAL_PATCH_DIR="board/nezha/patches"
|
2022-10-04 21:50:35 +02:00
|
|
|
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_19=y
|
2022-09-06 18:15:57 +02:00
|
|
|
BR2_SYSTEM_DHCP="eth0"
|
2021-11-06 18:29:55 +01:00
|
|
|
BR2_ROOTFS_OVERLAY="board/nezha/overlay"
|
|
|
|
BR2_ROOTFS_POST_IMAGE_SCRIPT="support/scripts/genimage.sh"
|
|
|
|
BR2_ROOTFS_POST_SCRIPT_ARGS="-c board/nezha/genimage.cfg"
|
|
|
|
BR2_LINUX_KERNEL=y
|
|
|
|
BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
|
nezha_defconfig: bump opensbi, u-boot and linux
Opensbi is now based on 1.1, U-Boot on 2022.07-rc3 and Linux on 5.19-rc1.
We don't yet support 5.19 kernel headers, so use 5.17 instead.
The incompatibility between opensbi and u-boot is now fixed, so drop
0001-arch-riscv-dts-sun20i-d1.dtsi-adjust-plic-compatible.patch.
The updated device tree in the kernel tree no longer specifies a memory
node (and the board exists in 512M/1G/2G variants, so instead use the
(otherwise identical) device tree provided by u-boot, where the memory
node is fixed up based on the detected memory size.
On riscv, the linux kernel unconditionally wants to build its bundled
dtc, so it needs flex and bison, even if it is not going to build any
DTB. We can get flex and bison either via the system ones, or we get
them as they are in LINUX_KCONFIG_DEPENDENCIES. However, relying on this
is a bit fragile, so we keep asking the kernel to build a DTB, so that
we do ensure that our host-{flex,bison} are built and in the dependency
chain of the kernel (for PPD).
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
[yann.morin.1998@free.fr:
- extend on why we keep building a DTB from the kernel
]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-09-06 18:15:56 +02:00
|
|
|
BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,smaeul,linux,fe178cf0153d98b71cb01a46c8cc050826a17e77)/linux-fe178cf0153d98b71cb01a46c8cc050826a17e77.tar.gz"
|
2021-11-06 18:29:55 +01:00
|
|
|
BR2_LINUX_KERNEL_DEFCONFIG="nezha"
|
|
|
|
BR2_LINUX_KERNEL_DTS_SUPPORT=y
|
|
|
|
BR2_LINUX_KERNEL_INTREE_DTS_NAME="allwinner/sun20i-d1-nezha"
|
|
|
|
BR2_LINUX_KERNEL_INSTALL_TARGET=y
|
|
|
|
BR2_TARGET_ROOTFS_EXT2=y
|
|
|
|
BR2_TARGET_ROOTFS_EXT2_4=y
|
|
|
|
# BR2_TARGET_ROOTFS_TAR is not set
|
|
|
|
BR2_TARGET_OPENSBI=y
|
|
|
|
BR2_TARGET_OPENSBI_CUSTOM_TARBALL=y
|
nezha_defconfig: bump opensbi, u-boot and linux
Opensbi is now based on 1.1, U-Boot on 2022.07-rc3 and Linux on 5.19-rc1.
We don't yet support 5.19 kernel headers, so use 5.17 instead.
The incompatibility between opensbi and u-boot is now fixed, so drop
0001-arch-riscv-dts-sun20i-d1.dtsi-adjust-plic-compatible.patch.
The updated device tree in the kernel tree no longer specifies a memory
node (and the board exists in 512M/1G/2G variants, so instead use the
(otherwise identical) device tree provided by u-boot, where the memory
node is fixed up based on the detected memory size.
On riscv, the linux kernel unconditionally wants to build its bundled
dtc, so it needs flex and bison, even if it is not going to build any
DTB. We can get flex and bison either via the system ones, or we get
them as they are in LINUX_KCONFIG_DEPENDENCIES. However, relying on this
is a bit fragile, so we keep asking the kernel to build a DTB, so that
we do ensure that our host-{flex,bison} are built and in the dependency
chain of the kernel (for PPD).
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
[yann.morin.1998@free.fr:
- extend on why we keep building a DTB from the kernel
]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-09-06 18:15:56 +02:00
|
|
|
BR2_TARGET_OPENSBI_CUSTOM_TARBALL_LOCATION="$(call github,smaeul,opensbi,e6793dc36a71537023f078034fe795c64a9992a3)/opensbi-e6793dc36a71537023f078034fe795c64a9992a3.tar.gz"
|
2021-11-06 18:29:55 +01:00
|
|
|
BR2_TARGET_OPENSBI_PLAT="generic"
|
|
|
|
# BR2_TARGET_OPENSBI_INSTALL_JUMP_IMG is not set
|
|
|
|
BR2_TARGET_SUN20I_D1_SPL=y
|
|
|
|
BR2_TARGET_UBOOT=y
|
|
|
|
BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
|
|
|
|
BR2_TARGET_UBOOT_CUSTOM_TARBALL=y
|
nezha_defconfig: bump opensbi, u-boot and linux
Opensbi is now based on 1.1, U-Boot on 2022.07-rc3 and Linux on 5.19-rc1.
We don't yet support 5.19 kernel headers, so use 5.17 instead.
The incompatibility between opensbi and u-boot is now fixed, so drop
0001-arch-riscv-dts-sun20i-d1.dtsi-adjust-plic-compatible.patch.
The updated device tree in the kernel tree no longer specifies a memory
node (and the board exists in 512M/1G/2G variants, so instead use the
(otherwise identical) device tree provided by u-boot, where the memory
node is fixed up based on the detected memory size.
On riscv, the linux kernel unconditionally wants to build its bundled
dtc, so it needs flex and bison, even if it is not going to build any
DTB. We can get flex and bison either via the system ones, or we get
them as they are in LINUX_KCONFIG_DEPENDENCIES. However, relying on this
is a bit fragile, so we keep asking the kernel to build a DTB, so that
we do ensure that our host-{flex,bison} are built and in the dependency
chain of the kernel (for PPD).
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
[yann.morin.1998@free.fr:
- extend on why we keep building a DTB from the kernel
]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-09-06 18:15:56 +02:00
|
|
|
BR2_TARGET_UBOOT_CUSTOM_TARBALL_LOCATION="$(call github,smaeul,u-boot,d1-2022-05-26)/uboot-d1-2022-05-26.tar.gz"
|
2021-11-06 18:29:55 +01:00
|
|
|
BR2_TARGET_UBOOT_BOARD_DEFCONFIG="nezha"
|
|
|
|
BR2_TARGET_UBOOT_NEEDS_DTC=y
|
2021-11-12 10:54:29 +01:00
|
|
|
BR2_TARGET_UBOOT_NEEDS_PYTHON3=y
|
|
|
|
BR2_TARGET_UBOOT_NEEDS_PYLIBFDT=y
|
|
|
|
BR2_TARGET_UBOOT_NEEDS_OPENSSL=y
|
2021-11-06 18:29:55 +01:00
|
|
|
BR2_TARGET_UBOOT_NEEDS_OPENSBI=y
|
|
|
|
# BR2_TARGET_UBOOT_FORMAT_BIN is not set
|
|
|
|
BR2_TARGET_UBOOT_FORMAT_CUSTOM=y
|
|
|
|
BR2_TARGET_UBOOT_FORMAT_CUSTOM_NAME="u-boot.toc1"
|
|
|
|
BR2_PACKAGE_HOST_GENIMAGE=y
|