From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Michal Simek <michal.simek@amd.com>,
Bill Mills <bill.mills@linaro.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: Re: [PATCH 0/2] drm: xlnx: zynqmp_kms: 16 bpp fixes for Xorg startup on AMD KV260
Date: Mon, 22 Dec 2025 10:58:42 +0200 [thread overview]
Message-ID: <aUkIQjKpd3MhNHjk@nuoska> (raw)
In-Reply-To: <aUVFUx55XTjb_2nO@nuoska>
Hi,
On Fri, Dec 19, 2025 at 02:30:11PM +0200, Mikko Rapeli wrote:
> On Fri, Dec 19, 2025 at 01:59:14PM +0200, Tomi Valkeinen wrote:
> > On 05/12/2025 14:37, Mikko Rapeli wrote:
> > > Currently on default yocto images Xorg fails to start on AMD KV260
> > > because 24/32 color depth gets detected but does not actually work.
> > >
> > > These two patches fix the issue and now 16 bpp gets detected
> > > and Xorg starts and draws on external HDMI display using
> > > kernel.org based linux-yocto kernel.
> > >
> > > Anatoliy Klymenko (1):
> > > drm: xlnx: zynqmp_kms: Init fbdev with 16 bit color
> > >
> > > Mikko Rapeli (1):
> > > drm: xlnx: zynqmp_kms: set preferred_depth to 16 bpp
> > >
> > > drivers/gpu/drm/xlnx/zynqmp_kms.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> >
> > Did you notice the few already sent serieses on the list where the topic
> > has been discussed?
>
> > [PATCH] drm: xlnx: zynqmp_dp: Support DRM_FORMAT_XRGB8888
> > [PATCH 0/3] drm: zynqmp: Make the video plane primary
>
> Oh I wasn't aware of these.
>
> > Or is there something else on KV260 that messes up the 24 bit color?
>
> These look very similar and likely fix the X11 startup. I will give them
> a try.
Right, now I've tested:
* these patches from Anatoliy and me to help X11 use 16bpp mode by default
and removes the need to manually setup Xorg for 16bpp
* "drm: xlnx: zynqmp_dp: Support DRM_FORMAT_XRGB8888" which enables the X11 default
24bpp to work, no need to set Xorg config to 16bpp
* "drm: zynqmp: Make the video plane primary" which also fixes the X11 default
24bpp to work, no need to set Xorg config to 16bpp
All of these fix HDMI graphics output on AMD KV260 board with yocto genericarm64 machine
and core-image-sato image which includes Xorg. The graphics rendering is still
very slow but I think that is a different problem.
I guess the last series from Sean Anderson is moving forward so I'll
reply to that thread separately.
Tested-by: Mikko Rapeli <mikko.rapeli@linaro.org>
Cheers,
-Mikko
next prev parent reply other threads:[~2025-12-22 8:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 12:37 [PATCH 0/2] drm: xlnx: zynqmp_kms: 16 bpp fixes for Xorg startup on AMD KV260 Mikko Rapeli
2025-12-05 12:37 ` [PATCH 1/2] drm: xlnx: zynqmp_kms: Init fbdev with 16 bit color Mikko Rapeli
2026-01-06 7:35 ` Thomas Zimmermann
2025-12-05 12:37 ` [PATCH 2/2] drm: xlnx: zynqmp_kms: set preferred_depth to 16 bpp Mikko Rapeli
2026-01-06 7:38 ` Thomas Zimmermann
2025-12-19 11:59 ` [PATCH 0/2] drm: xlnx: zynqmp_kms: 16 bpp fixes for Xorg startup on AMD KV260 Tomi Valkeinen
2025-12-19 12:30 ` Mikko Rapeli
2025-12-22 8:58 ` Mikko Rapeli [this message]
2026-01-06 7:41 ` Thomas Zimmermann
2026-01-06 8:29 ` Tomi Valkeinen
2026-01-06 8:42 ` Thomas Zimmermann
2026-01-07 8:00 ` Mikko Rapeli
2026-01-07 8:32 ` Thomas Zimmermann
2026-01-07 8:49 ` Mikko Rapeli
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=aUkIQjKpd3MhNHjk@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=airlied@gmail.com \
--cc=bill.mills@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ilias.apalodimas@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=michal.simek@amd.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tzimmermann@suse.de \
/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