From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qemu_riscv32_virt: Update to mainline glibc and kernel 5.4
Date: Thu, 3 Sep 2020 23:55:15 +0200 [thread overview]
Message-ID: <20200903235515.7b95e485@windsurf.home> (raw)
In-Reply-To: <20200831232051.2303515-1-alistair.francis@wdc.com>
On Mon, 31 Aug 2020 16:20:51 -0700
Alistair Francis <alistair.francis@wdc.com> wrote:
> Now that RISC-V 32-bit (RV32) support has been merged into mainilne
> glibc we can us upstream glibc and the 5.4 kernel.
>
> This patch removes the old files for the RV32 glibc fork and replaces
> them with new files for the latest SHA from upstream glibc. We also need
> to update the kernel as RV32 requires a 5.4+ kernel.
>
> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
> ---
> ...ert-riscv-Use-latest-system-call-ABI.patch | 66 -------------------
> board/qemu/riscv32-virt/readme.txt | 2 +-
> configs/qemu_riscv32_virt_defconfig | 7 +-
> ...001-riscv-Do-not-use-__has_include__.patch | 28 --------
> .../glibc.hash | 2 +-
> package/glibc/glibc.mk | 6 +-
> 6 files changed, 9 insertions(+), 102 deletions(-)
> delete mode 100644 board/qemu/riscv32-virt/patches/linux/0001-Revert-riscv-Use-latest-system-call-ABI.patch
> delete mode 100644 package/glibc/06983fe52cfe8e4779035c27e8cc5d2caab31531/0001-riscv-Do-not-use-__has_include__.patch
> rename package/glibc/{06983fe52cfe8e4779035c27e8cc5d2caab31531 => 2.32.9000-69-gbd394d131c10c9ec22c6424197b79410042eed99}/glibc.hash (69%)
Even though I understand they are related, I split the patch into two,
one for the glibc update, one for the defconfig change. Both applied.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-09-03 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 23:20 [Buildroot] [PATCH] qemu_riscv32_virt: Update to mainline glibc and kernel 5.4 Alistair Francis
2020-09-03 21:55 ` Thomas Petazzoni [this message]
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=20200903235515.7b95e485@windsurf.home \
--to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox