From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Gerd Hoffmann <kraxel@redhat.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: 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>,
Darren Stevens <darren@stevens-zone.net>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: [PATCH v2] drm/virtio: Add suppport for non-native buffer formats
Date: Sun, 19 Nov 2023 17:27:49 +0100 [thread overview]
Message-ID: <a9ade305-f90e-4250-a795-49ef4e29e0ac@xenosoft.de> (raw)
In-Reply-To: <77c6gkquzq4sdtmrlko3lkxvcnipm2zfjem3kvhgslcellkefh@man7pbbzud47>
On 16 November 2023 at 03:44 pm, Gerd Hoffmann wrote:
> On Thu, Nov 16, 2023 at 02:16:54PM +0100, Geert Uytterhoeven wrote:
>> When using virtgpu on a big-endian machine, e.g. powerpc QEMU:
>>
>> virtio-pci 0000:00:02.0: [drm] *ERROR* fbdev: Failed to setup generic emulation (ret=-2)
>>
>> or m68k/virt:
>>
>> virtio-mmio virtio-mmio.125: [drm] *ERROR* fbdev: Failed to setup generic emulation (ret=-2)
>>
>> and the graphical display fails to come up.
>>
>> Before, the call to drm_mode_addfb() caused a translation from a fourcc
>> format (XR24) to a bpp/depth pair (32/24) to a potentially different fourcc
>> format (BX24 on big-endian), due to the quirk processing in
>> drm_driver_legacy_fb_format(). After, the original fourcc format (XR24)
>> is passed unmodified.
>>
>> However, the virtgpu DRM driver supports only a single format for its
>> main plane: DRM_FORMAT_HOST_XRGB8888, which is XR24 on little-endian,
>> and BX24 on big-endian. I.e. on big-endian, virtgpu does not support
>> XR24, which is the default DRM format, and must be supported by all
>> drivers. Before, this was reported, but didn't lead to a failure:
>>
>> virtio-mmio virtio-mmio.125: [drm] bpp/depth value of 32/24 not supported
>> virtio-mmio virtio-mmio.125: [drm] No compatible format found
>>
>> As the core virtgpu driver and device support both XR24 and BX24 on both
>> little-endian and big-endian just fine, fix this extending the list of
>> supported formats for main plane and cursor plane to XR24/BX24 resp.
>> AR24/BA24.
>>
>> Fixes: 6ae2ff23aa43a0c4 ("drm/client: Convert drm_client_buffer_addfb() to drm_mode_addfb2()")
>> Reported-by: Christian Zigotzky <chzigotzky@xenosoft.de>
>> Closes: https://lore.kernel.org/r/c47fba21-3ae9-4021-9f4a-09c2670ebdbc@xenosoft.de
>> Suggested-by: Gerd Hoffmann <kraxel@redhat.com>
>> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
>
Hi All,
The new patch works but I don't see the virtio-mouse-pci pointer
anymore. I see the pointer with -device usb-tablet. Please check the
second patch. I will use the first patch for the RC2 of kernel 6.7.
Thanks,
Christian
next prev parent reply other threads:[~2023-11-19 16:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 13:16 Geert Uytterhoeven
2023-11-16 13:22 ` Javier Martinez Canillas
2023-11-16 14:44 ` Gerd Hoffmann
2023-11-19 16:27 ` Christian Zigotzky [this message]
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
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=a9ade305-f90e-4250-a795-49ef4e29e0ac@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=darren@stevens-zone.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--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
all inboxes | Powered by JetHome®