From: Gerd Hoffmann <kraxel@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Linux Fbdev development list" <linux-fbdev@vger.kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Michel Dänzer" <michel.daenzer@mailbox.org>,
"David Airlie" <airlied@linux.ie>,
Linux/m68k <linux-m68k@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Noralf Trønnes" <noralf@tronnes.org>,
"DRI Development" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/3] drm/fourcc: Add missing big-endian XRGB1555 and RGB565 formats
Date: Tue, 12 Jul 2022 10:31:57 +0200 [thread overview]
Message-ID: <20220712083157.wtujadjcyboerxcl@sirius.home.kraxel.org> (raw)
In-Reply-To: <20220712074715.kopstlvz4q6npaye@sirius.home.kraxel.org>
Hi,
> So adding support for bigendian formats to the driver shouldn't be
> much of a problem. The vram will continue to run in little endian
> RGB565, the shadow will be big endian RGB565, and the driver must
> byteswap when copying.
For completeness: The other obvious option (for fbcon) would be to
handle the byteswapping in the generic drm fbdev emulation, which
would have the advantage that it would be more generic and would
not depend on the drm driver supporting the bigendian rgb565
formats ...
take care,
Gerd
WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Linux Fbdev development list" <linux-fbdev@vger.kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Michel Dänzer" <michel.daenzer@mailbox.org>,
"David Airlie" <airlied@linux.ie>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"DRI Development" <dri-devel@lists.freedesktop.org>,
"Noralf Trønnes" <noralf@tronnes.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH 1/3] drm/fourcc: Add missing big-endian XRGB1555 and RGB565 formats
Date: Tue, 12 Jul 2022 10:31:57 +0200 [thread overview]
Message-ID: <20220712083157.wtujadjcyboerxcl@sirius.home.kraxel.org> (raw)
In-Reply-To: <20220712074715.kopstlvz4q6npaye@sirius.home.kraxel.org>
Hi,
> So adding support for bigendian formats to the driver shouldn't be
> much of a problem. The vram will continue to run in little endian
> RGB565, the shadow will be big endian RGB565, and the driver must
> byteswap when copying.
For completeness: The other obvious option (for fbcon) would be to
handle the byteswapping in the generic drm fbdev emulation, which
would have the advantage that it would be more generic and would
not depend on the drm driver supporting the bigendian rgb565
formats ...
take care,
Gerd
next prev parent reply other threads:[~2022-07-12 8:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 18:21 [PATCH 0/3] drm: Endianness fixes Geert Uytterhoeven
2022-07-08 18:21 ` Geert Uytterhoeven
2022-07-08 18:21 ` [PATCH 1/3] drm/fourcc: Add missing big-endian XRGB1555 and RGB565 formats Geert Uytterhoeven
2022-07-08 18:21 ` Geert Uytterhoeven
2022-07-11 15:22 ` Michel Dänzer
2022-07-11 15:30 ` Geert Uytterhoeven
2022-07-11 15:30 ` Geert Uytterhoeven
2022-07-11 16:28 ` Michel Dänzer
2022-07-11 16:28 ` Michel Dänzer
2022-07-12 7:47 ` Gerd Hoffmann
2022-07-12 7:47 ` Gerd Hoffmann
2022-07-12 8:01 ` Geert Uytterhoeven
2022-07-12 8:01 ` Geert Uytterhoeven
2022-07-12 8:39 ` Gerd Hoffmann
2022-07-12 8:39 ` Gerd Hoffmann
2022-07-12 8:43 ` Geert Uytterhoeven
2022-07-12 8:43 ` Geert Uytterhoeven
2022-07-12 9:03 ` Gerd Hoffmann
2022-07-12 9:03 ` Gerd Hoffmann
2022-07-12 9:09 ` Michel Dänzer
2022-07-12 9:09 ` Michel Dänzer
2022-07-12 9:10 ` Geert Uytterhoeven
2022-07-12 9:10 ` Geert Uytterhoeven
2022-07-12 8:31 ` Gerd Hoffmann [this message]
2022-07-12 8:31 ` Gerd Hoffmann
2022-07-08 18:21 ` [PATCH 2/3] drm/format-helper: Fix endianness in drm_fb_*_to_*() conversion helpers Geert Uytterhoeven
2022-07-08 18:21 ` Geert Uytterhoeven
2022-07-08 18:21 ` [PATCH 3/3] drm/gud: Fix endianness in gud_xrgb8888_to_color() helper Geert Uytterhoeven
2022-07-08 18:21 ` Geert Uytterhoeven
2022-07-19 14:39 ` Noralf Trønnes
2022-07-19 14:39 ` Noralf Trønnes
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=20220712083157.wtujadjcyboerxcl@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=michel.daenzer@mailbox.org \
--cc=noralf@tronnes.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.