From: Shyam Saini <shyam.saini@amarulasolutions.com>
To: buildroot@busybox.net
Subject: [Buildroot] [V2 1/7] configs: pine64_sopine: Bump to the linux 5.0 and u-boot 2019.01
Date: Tue, 9 Apr 2019 21:14:57 +0530 [thread overview]
Message-ID: <20190409154503.7598-2-shyam.saini@amarulasolutions.com> (raw)
In-Reply-To: <20190409154503.7598-1-shyam.saini@amarulasolutions.com>
This bumps to linux/linux-headers 5.0 and u-boot version 2019.01
Signed-off-by: Shyam Saini <shyam.saini@amarulasolutions.com>
---
configs/pine64_sopine_defconfig | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/configs/pine64_sopine_defconfig b/configs/pine64_sopine_defconfig
index b076681a98..3dcd907a7e 100644
--- a/configs/pine64_sopine_defconfig
+++ b/configs/pine64_sopine_defconfig
@@ -2,8 +2,8 @@ BR2_aarch64=y
BR2_cortex_a53=y
BR2_ARM_FPU_VFPV4=y
-# Linux headers same as kernel, a 4.14 series
-BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_14=y
+# Linux headers same as kernel, a 5.0 series
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_0=y
# Firmware
BR2_TARGET_ARM_TRUSTED_FIRMWARE=y
@@ -17,7 +17,7 @@ BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL31=y
BR2_TARGET_UBOOT=y
BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
BR2_TARGET_UBOOT_CUSTOM_VERSION=y
-BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.11"
+BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2019.01"
BR2_TARGET_UBOOT_BOARD_DEFCONFIG="sopine_baseboard"
BR2_TARGET_UBOOT_NEEDS_DTC=y
BR2_TARGET_UBOOT_NEEDS_ATF_BL31=y
@@ -31,7 +31,7 @@ BR2_TARGET_UBOOT_BOOT_SCRIPT_SOURCE="board/pine64/sopine/boot.cmd"
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
-BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.14"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.0"
BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG=y
BR2_LINUX_KERNEL_DTS_SUPPORT=y
BR2_LINUX_KERNEL_INTREE_DTS_NAME="allwinner/sun50i-a64-sopine-baseboard"
--
2.11.0
next prev parent reply other threads:[~2019-04-09 15:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 15:44 [Buildroot] [V2 0/7] linux and uboot version bumps and cleanup Shyam Saini
2019-04-09 15:44 ` Shyam Saini [this message]
2019-04-09 15:44 ` [Buildroot] [V2 2/7] configs: orangepi_prime: Bump to the linux 5.0 and u-boot 2019.01 Shyam Saini
2019-04-09 15:44 ` [Buildroot] [V2 3/7] configs: olimex_a64_olinuxino: " Shyam Saini
2019-04-09 15:45 ` [Buildroot] [V2 4/7] configs: orangepi_plus: " Shyam Saini
2019-04-09 15:45 ` [Buildroot] [V2 5/7] configs: nanopi_m1: " Shyam Saini
2019-04-09 15:45 ` [Buildroot] [V2 6/7] configs: nanopi_m1_plus: " Shyam Saini
2019-04-09 15:45 ` [Buildroot] [V2 7/7] board: friendlyarm: nanopi-m1-plus: patches: Remove linux patch Shyam Saini
2019-04-10 11:41 ` [Buildroot] [V2 0/7] linux and uboot version bumps and cleanup Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190409154503.7598-2-shyam.saini@amarulasolutions.com \
--to=shyam.saini@amarulasolutions.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.