Re: [Buildroot] [PATCH] configs/qemu: Update defconfigs to Linux 6.6.32

From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] configs/qemu: Update defconfigs to Linux 6.6.32
Date: Sat, 22 Jun 2024 19:34:07 +0200	[thread overview]
Message-ID: <20240622193407.1981d92d@windsurf> (raw)
In-Reply-To: <Zm/ksIQncNtMkBcv@waldemar-brodkorb.de>

Hello Waldemar,

On Mon, 17 Jun 2024 09:24:32 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:

> Linux version are changed to 6.6.32 (LTS) for all qemu defconfigs,
> 
> Qemu 9.0.0/9.0.1 has introduced a Bug in sh4/sh4eb emulation so
> that the system doesn't boot anymore.
> The issue is already reported by Guenter Roeck:
> https://lists.nongnu.org/archive/html/qemu-devel/2024-05/msg00606.html

So this is not a regression introduced by this patch, right?

> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> Should we switch sh4/sh4eb to initramfs?

I guess it would be good to have those defconfigs working yes.

> diff --git a/package/binutils/binutils.hash b/package/binutils/binutils.hash
> index ac724d5c15..d332445779 100644
> --- a/package/binutils/binutils.hash
> +++ b/package/binutils/binutils.hash
> @@ -9,3 +9,6 @@ sha512  3518b47d5c11d1fb478ee152bde1719363f9391db73f3b9f5491217c17742bef8ebca6a5
>  # locally computed
>  sha256  8ceb4b9ee5adedde47b31e975c1d90c73ad27b6b165a1dcd80c7c545eb65b903  COPYING3
>  sha256  56bdea73b6145ef6ac5259b3da390b981d840c24cb03b8e1cbc678de7ecfa18d  COPYING.LIB
> +
> +# locally computed
> +sha256  a76052c0c71d4025b117dcfc18ca7e189ac495a7645fa98c1bdaddca15cce815  xtensa_dc233c.tar.gz
> diff --git a/package/gcc/gcc.hash b/package/gcc/gcc.hash
> index 0b48a1acdd..0dbcd82ed1 100644
> --- a/package/gcc/gcc.hash
> +++ b/package/gcc/gcc.hash
> @@ -20,3 +20,6 @@ sha256  8ceb4b9ee5adedde47b31e975c1d90c73ad27b6b165a1dcd80c7c545eb65b903  COPYIN
>  sha256  a853c2ffec17057872340eee242ae4d96cbf2b520ae27d903e1b2fef1a5f9d1c  COPYING3.LIB
>  sha256  a9bdde5616ecdd1e980b44f360600ee8783b1f99b8cc83a2beb163a0a390e861  COPYING.LIB
>  sha256  9d6b43ce4d8de0c878bf16b54d8e7a10d9bd42b75178153e3af6a815bdc90f74  COPYING.RUNTIME
> +
> +# Locally calculated
> +sha256  a76052c0c71d4025b117dcfc18ca7e189ac495a7645fa98c1bdaddca15cce815  xtensa_dc233c.tar.gz

I believe those hashes should not be in package/binutils/binutils.hash
and package/gcc/gcc.hash, because they are specific to the Qemu Xtensa
defconfigs. Instead, they should go in board/qemu/patches/gcc/gcc.hash
and board/qemu/patches/binutils/binutils.hash. My understanding of the
hash checking code is that hashes are looked *both* into the main hash
file (package/gcc/gcc.hash) and into any existing hash file provided in
the BR2_GLOBAL_PATCH_DIR directory.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot