From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sebastian Reichel <sre@kernel.org>
Cc: Merlijn Wajer <merlijn@wizzup.org>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
ruleh <ruleh@gmx.de>,
dri-devel@lists.freedesktop.org, linux-omap@vger.kernel.org
Subject: [RFC] drm/omap: Create only one primary plane for CRTC
Date: Fri, 28 Feb 2020 12:05:34 -0800 [thread overview]
Message-ID: <20200228200534.GO37466@atomide.com> (raw)
Hi,
Looks like sway and wlroots won't work with omaprdrm because of
the following error:
backend/drm/drm.c:86: add_plane: Assertion
!(type == DRM_PLANE_TYPE_PRIMARY && crtc->primary)
Looks like there should only be one primary plane per CRTC?
There's some discussion about that for a wlroots bug at:
https://github.com/swaywm/wlroots/issues/1943
And there's a link pointing to the kms docs:
https://01.org/linuxgraphics/gfx-docs/drm/gpu/drm-kms.html#plane-abstraction
Below is a quick hack fix I used to get sway started.
Not sure how the primary plane should be picked? I just
used 0 as the primary plane to get things working :)
I can start xterm on sway, but so far no fonts only the
borders.
Regards,
Tony
8< ----------------------
diff --git a/drivers/gpu/drm/omapdrm/omap_drv.c b/drivers/gpu/drm/omapdrm/omap_drv.c
index d2750f60f519..122f8c4cf45b 100644
--- a/drivers/gpu/drm/omapdrm/omap_drv.c
+++ b/drivers/gpu/drm/omapdrm/omap_drv.c
@@ -268,7 +268,7 @@ static int omap_modeset_init(struct drm_device *dev)
plane_crtc_mask = (1 << priv->num_pipes) - 1;
for (i = 0; i < num_ovls; i++) {
- enum drm_plane_type type = i < priv->num_pipes
+ enum drm_plane_type type = i == 0
? DRM_PLANE_TYPE_PRIMARY
: DRM_PLANE_TYPE_OVERLAY;
struct drm_plane *plane;
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2020-02-29 10:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200228200534.GO37466@atomide.com \
--to=tony@atomide.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=ruleh@gmx.de \
--cc=sre@kernel.org \
--cc=tomi.valkeinen@ti.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