From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>, SamJakob <me@samjakob.com>
Cc: qemu-trivial@nongnu.org,
"open list:Raspberry Pi" <qemu-arm@nongnu.org>,
"open list:All patches CC here" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] hw/display/bcm2835_fb: fix fb_use_offsets condition
Date: Tue, 16 Jul 2024 16:37:32 +0200 [thread overview]
Message-ID: <3e35a80c-fa0f-41f5-8a63-30a873fb3bad@linaro.org> (raw)
In-Reply-To: <CAFEAcA82m+8K8rWDMBehPp=NGUezHZPn1LVoyU3DJ3LWq+ZnAw@mail.gmail.com>
On 16/7/24 12:35, Peter Maydell wrote:
> On Sat, 13 Jul 2024 at 17:04, SamJakob <me@samjakob.com> wrote:
>>
>> It is common practice when implementing double-buffering
>> on VideoCore to do so by multiplying the height of the
>> virtual buffer by the number of virtual screens desired
>> (i.e., two - in the case of double-bufferring).
>>
>> At present, this won't work in QEMU because the logic in
>> fb_use_offsets require that both the virtual width and
>> height exceed their physical counterparts.
>>
>> This appears to be unintentional/a typo and indeed the
>> comment states; "Experimentally, the hardware seems to
>> do this only if the viewport size is larger than the
>> physical screen". The viewport/virtual size would be
>> larger than the physical size if either virtual dimension
>> were larger than their physical counterparts and not
>> necessarily both.
>>
>> Signed-off-by: SamJakob <me@samjakob.com>
>
> Thanks for this bugfix; I've applied it to my target-arm.next
> queue and it should get upstream within a week or so.
Since I'm seeing 2 times the same patch, adding R-b again on
this one:
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
(BTW Peter the commit description is mis-aligned, if you
don't mind, correcting it while applying would be appreciated!)
Thanks,
Phil.
next prev parent reply other threads:[~2024-07-16 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 16:03 [PATCH] hw/display/bcm2835_fb: fix fb_use_offsets condition SamJakob
2024-07-16 10:35 ` Peter Maydell
2024-07-16 14:37 ` Philippe Mathieu-Daudé [this message]
2024-07-16 14:44 ` Peter Maydell
2024-07-16 16:10 ` Sam M.
-- strict thread matches above, loose matches on Subject: below --
2024-07-13 15:56 SamJakob
2024-07-13 21:08 ` Philippe Mathieu-Daudé
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=3e35a80c-fa0f-41f5-8a63-30a873fb3bad@linaro.org \
--to=philmd@linaro.org \
--cc=me@samjakob.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).