From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Thomas Zimmermann <tzimmermann@suse.de>,
Javier Martinez Canillas <javierm@redhat.com>,
airlied@linux.ie, daniel@ffwll.ch, deller@gmx.de,
maxime@cerno.tech, sam@ravnborg.org, msuchanek@suse.de,
mpe@ellerman.id.au, paulus@samba.org
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/2] drm/tiny: Add ofdrm for Open Firmware framebuffers
Date: Wed, 25 May 2022 13:15:31 +1000 [thread overview]
Message-ID: <ede15a37b9e854a50c9d67b890bdebb25642a003.camel@kernel.crashing.org> (raw)
In-Reply-To: <8cd53439-46f1-117c-7aae-7630a6466ab8@suse.de>
On Sun, 2022-05-22 at 21:35 +0200, Thomas Zimmermann wrote:
> > Interesting. Did you find some formats that were not supported ?
>
> We still don't support XRGB1555. If the native buffer uses this format,
> we'd have no conversion helper. In this case, we rely on userspace/fbcon
> to use the native format exclusively. (BTW, I asked one of my coworkers
> to implement XRGB1555 to make her familiar with DRM. That's why I
> haven't sent a patch yet.)
>
Various old macs do 1555 ...
Cheers,
Ben.
prev parent reply other threads:[~2022-05-25 3:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 18:30 [PATCH 0/2] drm: Add driverof PowerPC OF displays Thomas Zimmermann
2022-05-18 18:30 ` [PATCH 1/2] MAINTAINERS: Broaden scope of simpledrm entry Thomas Zimmermann
2022-05-20 5:18 ` Javier Martinez Canillas
2022-05-18 18:30 ` [PATCH 2/2] drm/tiny: Add ofdrm for Open Firmware framebuffers Thomas Zimmermann
2022-05-18 18:51 ` Michal Suchánek
2022-05-19 7:11 ` Geert Uytterhoeven
2022-05-19 7:27 ` Thomas Zimmermann
2022-05-21 2:49 ` Benjamin Herrenschmidt
2022-05-25 16:45 ` Thomas Zimmermann
2022-05-27 0:17 ` Benjamin Herrenschmidt
2022-05-27 0:19 ` Benjamin Herrenschmidt
2022-05-21 1:35 ` Benjamin Herrenschmidt
2022-05-18 21:11 ` Mark Cave-Ayland
2022-05-19 6:34 ` Michal Suchánek
2022-05-19 7:39 ` Thomas Zimmermann
2022-05-20 6:19 ` Javier Martinez Canillas
2022-05-22 19:35 ` Thomas Zimmermann
2022-05-25 3:15 ` Benjamin Herrenschmidt [this message]
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=ede15a37b9e854a50c9d67b890bdebb25642a003.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maxime@cerno.tech \
--cc=mpe@ellerman.id.au \
--cc=msuchanek@suse.de \
--cc=paulus@samba.org \
--cc=sam@ravnborg.org \
--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;
as well as URLs for NNTP newsgroup(s).