From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Thomas Zimmermann" <tzimmermann@suse.de>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Michal Suchánek" <msuchanek@suse.de>
Cc: Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
Michael Ellerman <mpe@ellerman.id.au>,
Helge Deller <deller@gmx.de>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Javier Martinez Canillas <javierm@redhat.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
Paul Mackerras <paulus@samba.org>,
Maxime Ripard <maxime@cerno.tech>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH 2/2] drm/tiny: Add ofdrm for Open Firmware framebuffers
Date: Fri, 27 May 2022 10:17:50 +1000 [thread overview]
Message-ID: <23740c1edd7b080133ab852cd8e3de89fd7c9aae.camel@kernel.crashing.org> (raw)
In-Reply-To: <a077bc25-03b3-f8bd-0138-a175a2864943@suse.de>
On Wed, 2022-05-25 at 18:45 +0200, Thomas Zimmermann wrote:
>
> > The palette handling is useful when using a real Open Firmware
> > implementation which tends to boot in 8-bit mode, so without palette
> > things will look ... bad.
> >
> > It's not necessary when using 16/32 bpp framebuffers which is typically
> > ... what BootX provides :-)
>
> Maybe the odd color formats can be tested via qemu.
>
> I don't mind adding DRM support for BootX displays, but getting the
> necessary test HW with a suitable Linux seems to be laborious. Would a
> G4 Powerbook work?
My point was that it's the non-BootX case that cares about the palette
hacks :-)
Cheers,
Ben.
next prev parent reply other threads:[~2022-05-27 0:26 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 [this message]
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
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=23740c1edd7b080133ab852cd8e3de89fd7c9aae.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=airlied@linux.ie \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.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).