From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dmitriy Chestnykh <dm.chestnykh@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/uclibc: Fix ARC build with 4.x kernel headers
Date: Tue, 30 Jul 2024 22:17:08 +0200 [thread overview]
Message-ID: <20240730221708.155d6fc9@windsurf> (raw)
In-Reply-To: <CA+RUeSpHZdf5uMFQi37xum67Ro7w6TJZRF-oeYc1ma8CtWfwWg@mail.gmail.com>
On Mon, 29 Jul 2024 07:38:12 +0300
Dmitriy Chestnykh <dm.chestnykh@gmail.com> wrote:
> Which version of QEMU do you use? Recently Waldemar sent a patch where he
> noticed that QEMU 9.x has an issue with SH4 emulation and the system
> doesn't boot
I do have the fix from Waldemar that brings the rootfs as an initramfs
in SuperH configurations, to workaround the Qemu 9.x bug.
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
next prev parent reply other threads:[~2024-07-30 20:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 11:58 [Buildroot] [PATCH] package/uclibc: Fix ARC build with 4.x kernel headers Dmitry Chestnykh
2024-07-28 16:00 ` Thomas Petazzoni via buildroot
2024-07-28 16:21 ` Dmitriy Chestnykh
2024-07-28 20:11 ` Thomas Petazzoni via buildroot
2024-07-29 4:00 ` Dmitriy Chestnykh
2024-07-29 4:38 ` Dmitriy Chestnykh
2024-07-30 20:17 ` Thomas Petazzoni via buildroot [this message]
2024-07-29 4:51 ` Waldemar Brodkorb
2024-07-29 5:00 ` Dmitriy Chestnykh
2024-07-30 20:16 ` Thomas Petazzoni via buildroot
2024-07-30 20:38 ` [Buildroot] [PATCH] SuperH qemu issues Thomas Petazzoni via buildroot
2024-08-03 6:34 ` [Buildroot] [PATCH] package/uclibc: Fix ARC build with 4.x kernel headers Waldemar Brodkorb
2024-08-12 19:27 ` Thomas Petazzoni via buildroot
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=20240730221708.155d6fc9@windsurf \
--to=buildroot@buildroot.org \
--cc=dm.chestnykh@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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