diff mbox series

orange-pi-one: bump kernel and uboot versions

Message ID 20171106092602.24565-1-geomatsi@gmail.com
State Accepted
Commit 4f73b91c5be8676637c1349175a797b300f70353
Headers show
Series orange-pi-one: bump kernel and uboot versions | expand

Commit Message

Sergey Matyukevich Nov. 6, 2017, 9:26 a.m. UTC
Bump kernel to 4.13.11 and U-Boot to 2017.09.

Signed-off-by: Sergey Matyukevich <geomatsi@gmail.com>
---
 configs/orangepi_one_defconfig | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

Comments

Peter Korsgaard Nov. 6, 2017, 10:43 a.m. UTC | #1
>>>>> "Sergey" == Sergey Matyukevich <geomatsi@gmail.com> writes:

 > Bump kernel to 4.13.11 and U-Boot to 2017.09.
 > Signed-off-by: Sergey Matyukevich <geomatsi@gmail.com>

Committed, thanks.
Matt Weber Nov. 6, 2017, 6:02 p.m. UTC | #2
Sergey,

On Mon, Nov 6, 2017 at 3:26 AM, Sergey Matyukevich <geomatsi@gmail.com> wrote:
> Bump kernel to 4.13.11 and U-Boot to 2017.09.
>

<snip>

> @@ -18,7 +18,7 @@ BR2_TARGET_ROOTFS_EXT2_4=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.03"
> +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.09"

This bump requires BR2_TARGET_UBOOT_NEEDS_PYLIBFDT=y .  You can't see
the failure if your host machine has swig.

Similar to what was observed with uboot-tools:
https://git.busybox.net/buildroot/commit/?id=0bcd09ffcabbcce74ed00bc38620f71a34a59b45

Matt
Sergey Matyukevich Nov. 6, 2017, 6:31 p.m. UTC | #3
> > Bump kernel to 4.13.11 and U-Boot to 2017.09.
> >
> 
> <snip>
> 
> > @@ -18,7 +18,7 @@ BR2_TARGET_ROOTFS_EXT2_4=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.03"
> > +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.09"
> 
> This bump requires BR2_TARGET_UBOOT_NEEDS_PYLIBFDT=y .  You can't see
> the failure if your host machine has swig.
> 
> Similar to what was observed with uboot-tools:
> https://git.busybox.net/buildroot/commit/?id=0bcd09ffcabbcce74ed00bc38620f71a34a59b45

Thanks a lot ! I noticed this problem on one of my machines, but haven't
yet investigated the root cause. Actually in my case both host-uboot-tools
and u-boot fail unless I modify path to libfdt headers.

I will verify the fix for all my recent board updates and then submit it.

Regards,
Sergey
Matt Weber Nov. 6, 2017, 8:11 p.m. UTC | #4
Sergey,

On Mon, Nov 6, 2017 at 12:31 PM, Sergey Matyukevich <geomatsi@gmail.com> wrote:
>> > Bump kernel to 4.13.11 and U-Boot to 2017.09.
>> >
>>
>> <snip>
>>
>> > @@ -18,7 +18,7 @@ BR2_TARGET_ROOTFS_EXT2_4=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.03"
>> > +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.09"
>>
>> This bump requires BR2_TARGET_UBOOT_NEEDS_PYLIBFDT=y .  You can't see
>> the failure if your host machine has swig.
>>
>> Similar to what was observed with uboot-tools:
>> https://git.busybox.net/buildroot/commit/?id=0bcd09ffcabbcce74ed00bc38620f71a34a59b45
>
> Thanks a lot ! I noticed this problem on one of my machines, but haven't
> yet investigated the root cause. Actually in my case both host-uboot-tools
> and u-boot fail unless I modify path to libfdt headers.
>
> I will verify the fix for all my recent board updates and then submit it.
>

I just sent the fix for the libfdt headers.  I need to do a v2 for an
issue with older uboots but the general idea is there.

Matt
Peter Korsgaard Nov. 6, 2017, 8:27 p.m. UTC | #5
>>>>> "Sergey" == Sergey Matyukevich <geomatsi@gmail.com> writes:

 >> > Bump kernel to 4.13.11 and U-Boot to 2017.09.
 >> >
 >> 
 >> <snip>
 >> 
 >> > @@ -18,7 +18,7 @@ BR2_TARGET_ROOTFS_EXT2_4=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.03"
 >> > +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.09"
 >> 
 >> This bump requires BR2_TARGET_UBOOT_NEEDS_PYLIBFDT=y .  You can't see
 >> the failure if your host machine has swig.
 >> 
 >> Similar to what was observed with uboot-tools:
 >> https://git.busybox.net/buildroot/commit/?id=0bcd09ffcabbcce74ed00bc38620f71a34a59b45

 > Thanks a lot ! I noticed this problem on one of my machines, but haven't
 > yet investigated the root cause. Actually in my case both host-uboot-tools
 > and u-boot fail unless I modify path to libfdt headers.

That is a separate issue. I have just pushed two fixes for this (which
patch the fdtgrep.c include line).
diff mbox series

Patch

diff --git a/configs/orangepi_one_defconfig b/configs/orangepi_one_defconfig
index bc3216389c..507e4deda4 100644
--- a/configs/orangepi_one_defconfig
+++ b/configs/orangepi_one_defconfig
@@ -1,14 +1,14 @@ 
 BR2_arm=y
 BR2_cortex_a7=y
 BR2_ARM_FPU_VFPV4=y
-BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_11=y
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_13=y
 BR2_TARGET_GENERIC_HOSTNAME="OrangePi_One"
 BR2_TARGET_GENERIC_ISSUE="Welcome to Buildroot for the Orange Pi One"
 BR2_ROOTFS_POST_BUILD_SCRIPT="board/orangepi/orangepi-one/post-build.sh"
 BR2_ROOTFS_POST_IMAGE_SCRIPT="board/orangepi/orangepi-one/post-image.sh"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_VERSION=y
-BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.11"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.13.11"
 BR2_LINUX_KERNEL_DEFCONFIG="sunxi"
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
 BR2_LINUX_KERNEL_INTREE_DTS_NAME="sun8i-h3-orangepi-one"
@@ -18,7 +18,7 @@  BR2_TARGET_ROOTFS_EXT2_4=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.03"
+BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2017.09"
 BR2_TARGET_UBOOT_BOARD_DEFCONFIG="orangepi_one"
 BR2_TARGET_UBOOT_NEEDS_DTC=y
 BR2_TARGET_UBOOT_FORMAT_CUSTOM=y