From: Jocelyn Falempe <jfalempe@redhat.com>
To: Javier Martinez Canillas <javierm@redhat.com>,
David Airlie <airlied@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Gurchetan Singh <gurchetansingh@chromium.org>,
Chia-I Wu <olvaffe@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, virtualization@lists.linux.dev
Subject: Re: [PATCH] drm/virtio: Use XRGB8888 also for big endian systems
Date: Mon, 19 Aug 2024 20:29:52 +0200 [thread overview]
Message-ID: <b1e442df-83dd-402f-a9d6-00a7c8c51954@redhat.com> (raw)
In-Reply-To: <874j7gld19.fsf@minerva.mail-host-address-is-not-set>
On 19/08/2024 17:58, Javier Martinez Canillas wrote:
> Jocelyn Falempe <jfalempe@redhat.com> writes:
>
> Helo Jocelyn,
>
> AFAICT your patch is doing two things:
>
>> Mesa doesn't support BGRX8888, that means most wayland compositors
>> doesn't work on big endian guests.
>>
>
> 1) Dropping the BGR{A,X}8888 support.
>
>> Also the colors are inverted when testing a s390x VM on a s390x host.
>> So I fixed the DRM_FORMAT -> VIRTIO_GPU_FORMAT on big endian guests.
>> It may break big-endian guest on little-endian host, but then the
>> fix should be in qemu, because we don't know the host endianess in
>> the guest VM.
>>
>
> 2) Fix the format translation to take into account the guest endianess.
>
> Maybe is better to split the changes in two separate patches ?
Yes, I will send a v2 with 2 patches, that would be better.
>
>> Signed-off-by: Jocelyn Falempe <jfalempe@redhat.com>
>> ---
>
> The patch makes sense to me though from your explanations.
>
> Acked-by: Javier Martinez Canillas <javierm@redhat.com>
>
Thanks for the review.
--
Jocelyn
prev parent reply other threads:[~2024-08-19 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 13:13 [PATCH] drm/virtio: Use XRGB8888 also for big endian systems Jocelyn Falempe
2024-08-19 15:58 ` Javier Martinez Canillas
2024-08-19 18:29 ` Jocelyn Falempe [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=b1e442df-83dd-402f-a9d6-00a7c8c51954@redhat.com \
--to=jfalempe@redhat.com \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.org \
--cc=javierm@redhat.com \
--cc=kraxel@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=olvaffe@gmail.com \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux.dev \
/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