From: Daniel Vetter <daniel@ffwll.ch>
To: Leandro Ribeiro <leandro.ribeiro@collabora.com>
Cc: Haneen Mohammed <hamohammed.sa@gmail.com>,
Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Melissa Wen <melissa.srw@gmail.com>
Subject: Re: [BUG] drm/vkms: Failure when using drmGetConnectorCurrent()
Date: Tue, 24 Nov 2020 15:39:47 +0100 [thread overview]
Message-ID: <20201124143947.GP401619@phenom.ffwll.local> (raw)
In-Reply-To: <d589025b-76b2-1826-1798-60f61000b14a@collabora.com>
On Fri, Nov 20, 2020 at 01:19:04PM -0300, Leandro Ribeiro wrote:
> Hello,
>
> We have a patch in Weston to replace drmGetConnector() calls with
> drmGetConnectorCurrent():
>
> https://gitlab.freedesktop.org/wayland/weston/-/issues/437
> https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/518
>
> Unfortunately this is not working when we use VKMS (upstream version
> tested). Please see
>
> https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/518#note_700345
I guess this is without fbdev configured on vkms? That's what usually
papers over this problem for most drivers.
> for more information, and feel free to jump into the discussion. If there's
> more helpful information that I can share, please let me know.
Like Simon suggested, please submit that patch you have for discussion.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-11-24 14:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 16:19 [BUG] drm/vkms: Failure when using drmGetConnectorCurrent() Leandro Ribeiro
2020-11-24 14:39 ` Daniel Vetter [this message]
2020-11-27 20:31 ` Leandro Ribeiro
2020-11-27 21:10 ` [PATCH] drm/vkms: detect modes during output initialization Leandro Ribeiro
2020-11-27 21:16 ` Leandro Ribeiro
2020-11-30 10:23 ` Simon Ser
2020-11-30 11:13 ` Pekka Paalanen
2020-11-30 11:16 ` Simon Ser
2020-11-30 11:24 ` Pekka Paalanen
2020-11-30 12:20 ` Simon Ser
2020-12-01 8:46 ` Pekka Paalanen
2020-12-01 8:55 ` Simon Ser
2020-12-01 2:24 ` [drm/vkms] b6c9ddb8c4: WARNING:at_drivers/gpu/drm/drm_probe_helper.c:#drm_helper_probe_single_connector_modes kernel test robot
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=20201124143947.GP401619@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=leandro.ribeiro@collabora.com \
--cc=melissa.srw@gmail.com \
--cc=rodrigosiqueiramelo@gmail.com \
/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