From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-arm@nongnu.org
Subject: Re: [PATCH 1/2] hw/misc/bcm2835_property: Fix framebuffer with recent RPi kernels
Date: Mon, 18 Oct 2021 21:27:50 +1100 [thread overview]
Message-ID: <a55f82099075eeaaa544f6f7fc7575b90d051caa.camel@kernel.crashing.org> (raw)
In-Reply-To: <353c1b30-7621-54c5-5294-ebf1d8b3f8b8@amsat.org>
On Mon, 2021-10-18 at 11:47 +0200, Philippe Mathieu-Daudé wrote:
>
> > I've just checked the rpi-5.15.y branch and it's the same.
>
> Indeed. I stopped testing recent kernels because they use too many
> features QEMU don't implement.
>
> Our model should generate the DTB blob of devices implemented, instead
> of giving false expectations to the guest by passing an unmodified dtb.
>
> This is on my TODO, I might give it a try next WE.
Indeed. That said, we do implement the fb, so we probably want that
fix. The fix for the virtual gpios is probably unnecessary however if
we do what you want.
That being said, with those two fixes, I can boot the latest 5.10 I get
from raspbian.
Cheers,
Ben.
next prev parent reply other threads:[~2021-10-18 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 7:48 [PATCH 1/2] hw/misc/bcm2835_property: Fix framebuffer with recent RPi kernels Benjamin Herrenschmidt
2021-10-17 15:08 ` Philippe Mathieu-Daudé
2021-10-18 0:41 ` Benjamin Herrenschmidt
2021-10-18 9:47 ` Philippe Mathieu-Daudé
2021-10-18 10:27 ` Benjamin Herrenschmidt [this message]
2021-10-18 10:41 ` Philippe Mathieu-Daudé
2021-11-18 15:05 ` [PATCH-for-6.2 " Philippe Mathieu-Daudé
2022-01-17 12:13 ` Philippe Mathieu-Daudé via
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=a55f82099075eeaaa544f6f7fc7575b90d051caa.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).