From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
David Airlie <airlied@redhat.com>,
Gurchetan Singh <gurchetansingh@chromium.org>,
Chia-I Wu <olvaffe@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Thomas Zimmermann <tzimmermann@suse.de>,
Laurent Vivier <lvivier@redhat.com>,
Javier Martinez Canillas <javierm@redhat.com>,
Hamza Mahfooz <hamza.mahfooz@amd.com>,
linux-m68k@lists.linux-m68k.org, dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, "R.T.Dickinson" <rtd2@xtra.co.nz>,
mad skateman <madskateman@gmail.com>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: [PATCH v2] drm/virtio: Add suppport for non-native buffer formats
Date: Sat, 25 Nov 2023 13:35:54 +0100 [thread overview]
Message-ID: <1bd6d2c8-007b-46f7-85b4-9793ec650f94@xenosoft.de> (raw)
In-Reply-To: <9e8d2abd-94a1-4fb6-b30a-c6e4c52af011@xenosoft.de>
On 25 November 2023 at 01:22 pm, Christian Zigotzky wrote:
> On 25 November 2023 at 12:09 pm, John Paul Adrian Glaubitz wrote:
>> On Sat, 2023-11-25 at 11:06 +0100, Christian Zigotzky wrote:
>>> Could you please revert the v2 patch because of the issue with the
>>> virtio-mouse-pci cursor? I will try to use the v1 patch for the RC3 of
>>> kernel 6.7.
>> I don't understand why the v2 patch should yield any different
>> results as
>> the only change compared to v1 is the fixed patch subject. There are no
>> functional differences, I just diffed the patches against each other:
>>
>> --- geert-patch-v1.patch 2023-11-25 12:09:19.122936658 +0100
>> +++ geert-patch-v2.patch 2023-11-25 12:09:36.313039085 +0100
>> @@ -34,6 +34,9 @@
>> Suggested-by: Gerd Hoffmann <kraxel@redhat.com>
>> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
>> ---
>> +v2:
>> + - Fix truncated one-line summary.
>> +---
>> drivers/gpu/drm/virtio/virtgpu_display.c | 11 +++++++++--
>> drivers/gpu/drm/virtio/virtgpu_plane.c | 6 ++++--
>> 2 files changed, 13 insertions(+), 4 deletions(-)
>>
>> Adrian
>>
> Hi Adrian,
>
> Thank you for the hint. I think you are right. I use the following patch.
>
> --- a/drivers/gpu/drm/drm_client.c 2023-11-13 01:19:07.000000000 +0100
> +++ b/drivers/gpu/drm/drm_client.c 2023-11-14 09:45:44.964199272 +0100
> @@ -400,6 +400,16 @@ static int drm_client_buffer_addfb(struc
>
> fb_req.width = width;
> fb_req.height = height;
> + if
> (client->dev->mode_config.quirk_addfb_prefer_host_byte_order) {
> + if (format == DRM_FORMAT_XRGB8888)
> + format = DRM_FORMAT_HOST_XRGB8888;
> + if (format == DRM_FORMAT_ARGB8888)
> + format = DRM_FORMAT_HOST_ARGB8888;
> + if (format == DRM_FORMAT_RGB565)
> + format = DRM_FORMAT_HOST_RGB565;
> + if (format == DRM_FORMAT_XRGB1555)
> + format = DRM_FORMAT_HOST_XRGB1555;
> + }
> fb_req.pixel_format = format;
> fb_req.handles[0] = handle;
> fb_req.pitches[0] = buffer->pitch;
>
> This patch solved the issue.
>
> Christian
This was the first solution and it works without any problems.
Christian
next prev parent reply other threads:[~2023-11-25 12:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 13:16 [PATCH v2] drm/virtio: Add suppport for non-native buffer formats Geert Uytterhoeven
2023-11-16 13:22 ` Javier Martinez Canillas
2023-11-16 14:44 ` Gerd Hoffmann
2023-11-19 16:27 ` Christian Zigotzky
2023-11-19 18:33 ` Geert Uytterhoeven
2023-11-25 10:06 ` Christian Zigotzky
2023-11-25 11:09 ` John Paul Adrian Glaubitz
2023-11-25 12:22 ` Christian Zigotzky
2023-11-25 12:35 ` Christian Zigotzky [this message]
2023-12-08 10:52 ` Christian Zigotzky
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=1bd6d2c8-007b-46f7-85b4-9793ec650f94@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=gurchetansingh@chromium.org \
--cc=hamza.mahfooz@amd.com \
--cc=info@xenosoft.de \
--cc=javierm@redhat.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=lvivier@redhat.com \
--cc=madskateman@gmail.com \
--cc=olvaffe@gmail.com \
--cc=rtd2@xtra.co.nz \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux-foundation.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