From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Noralf Trønnes" <noralf@tronnes.org>,
"Gerd Hoffmann" <kraxel@redhat.com>
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH 0/3] drm: Endianness fixes
Date: Fri, 8 Jul 2022 20:21:06 +0200 [thread overview]
Message-ID: <cover.1657300532.git.geert@linux-m68k.org> (raw)
Hi all,
This patch series contains several endianness fixes for the DRM
subsystem.
This has been tested on ARAnyM using a work-in-progress Atari DRM
driver, which supports (a.o.) big-endian RGB565 (more info and related
patches can be found in [1]).
Thanks for your comments!
[1] "[PATCH v3 00/10] drm: Add support for low-color frame buffer formats"
https://lore.kernel.org/r/cover.1657294931.git.geert@linux-m68k.org
Geert Uytterhoeven (3):
drm/fourcc: Add missing big-endian XRGB1555 and RGB565 formats
drm/format-helper: Fix endianness in drm_fb_*_to_*() conversion
helpers
drm/gud: Fix endianness in gud_xrgb8888_to_color() helper
drivers/gpu/drm/drm_format_helper.c | 80 +++++++++++++++++------------
drivers/gpu/drm/drm_fourcc.c | 4 ++
drivers/gpu/drm/gud/gud_pipe.c | 14 ++---
3 files changed, 58 insertions(+), 40 deletions(-)
--
2.25.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Noralf Trønnes" <noralf@tronnes.org>,
"Gerd Hoffmann" <kraxel@redhat.com>
Cc: linux-fbdev@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] drm: Endianness fixes
Date: Fri, 8 Jul 2022 20:21:06 +0200 [thread overview]
Message-ID: <cover.1657300532.git.geert@linux-m68k.org> (raw)
Hi all,
This patch series contains several endianness fixes for the DRM
subsystem.
This has been tested on ARAnyM using a work-in-progress Atari DRM
driver, which supports (a.o.) big-endian RGB565 (more info and related
patches can be found in [1]).
Thanks for your comments!
[1] "[PATCH v3 00/10] drm: Add support for low-color frame buffer formats"
https://lore.kernel.org/r/cover.1657294931.git.geert@linux-m68k.org
Geert Uytterhoeven (3):
drm/fourcc: Add missing big-endian XRGB1555 and RGB565 formats
drm/format-helper: Fix endianness in drm_fb_*_to_*() conversion
helpers
drm/gud: Fix endianness in gud_xrgb8888_to_color() helper
drivers/gpu/drm/drm_format_helper.c | 80 +++++++++++++++++------------
drivers/gpu/drm/drm_fourcc.c | 4 ++
drivers/gpu/drm/gud/gud_pipe.c | 14 ++---
3 files changed, 58 insertions(+), 40 deletions(-)
--
2.25.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2022-07-08 18:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 18:21 Geert Uytterhoeven [this message]
2022-07-08 18:21 ` [PATCH 0/3] drm: Endianness fixes 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
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=cover.1657300532.git.geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.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.