All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Pekka Paalanen <ppaalanen@gmail.com>
Cc: Finn Thain <fthain@linux-m68k.org>,
	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>,
	Javier Martinez Canillas <javierm@redhat.com>,
	Sam Ravnborg <sam@ravnborg.org>, Helge Deller <deller@gmx.de>,
	Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
	"Linux/m68k" <linux-m68k@vger.kernel.org>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 05/10] drm/fourcc: Add DRM_FORMAT_C[124]
Date: Tue, 15 Mar 2022 08:52:21 +0100	[thread overview]
Message-ID: <CAMuHMdUOwVLBLmxaVUO4yADVCf1k7CyhBZiesHx2Fr4LW3QWMQ@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdVU=JKwEn-=Wf3CYObtaLt2T7NmWrXUwdPHdvNsbgge=g@mail.gmail.com>

On Tue, Mar 15, 2022 at 8:51 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > Also, when drm_fourcc.h is describing pixel formats, it needs to
> > consider only how a little-endian CPU accesses them. That's how pixel
> > data in memory is described. Display hardware plays no part in that.
> > It is the driver's job to expose the pixel formats that match display
> > hardware behaviour.
>
> But if the "CPU format" does not match the "display support",

s/support/format/

> all pixel data must be converted?

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: Pekka Paalanen <ppaalanen@gmail.com>
Cc: Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
	Finn Thain <fthain@linux-m68k.org>,
	David Airlie <airlied@linux.ie>, Helge Deller <deller@gmx.de>,
	Javier Martinez Canillas <javierm@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH v2 05/10] drm/fourcc: Add DRM_FORMAT_C[124]
Date: Tue, 15 Mar 2022 08:52:21 +0100	[thread overview]
Message-ID: <CAMuHMdUOwVLBLmxaVUO4yADVCf1k7CyhBZiesHx2Fr4LW3QWMQ@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdVU=JKwEn-=Wf3CYObtaLt2T7NmWrXUwdPHdvNsbgge=g@mail.gmail.com>

On Tue, Mar 15, 2022 at 8:51 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > Also, when drm_fourcc.h is describing pixel formats, it needs to
> > consider only how a little-endian CPU accesses them. That's how pixel
> > data in memory is described. Display hardware plays no part in that.
> > It is the driver's job to expose the pixel formats that match display
> > hardware behaviour.
>
> But if the "CPU format" does not match the "display support",

s/support/format/

> all pixel data must be converted?

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

  reply	other threads:[~2022-03-15  7:52 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 20:52 [PATCH v2 00/10] drm: Add support for low-color frame buffer formats Geert Uytterhoeven
2022-03-07 20:52 ` Geert Uytterhoeven
2022-03-07 20:52 ` [PATCH v2 01/10] drm/fourcc: Add drm_format_info_bpp() helper Geert Uytterhoeven
2022-03-07 20:52   ` Geert Uytterhoeven
2022-03-09 12:46   ` Javier Martinez Canillas
2022-03-09 12:46     ` Javier Martinez Canillas
2022-03-07 20:52 ` [PATCH v2 02/10] drm/fourcc: Add drm_format_info.is_color_indexed flag Geert Uytterhoeven
2022-03-07 20:52   ` Geert Uytterhoeven
2022-03-09 12:50   ` Javier Martinez Canillas
2022-03-09 12:50     ` Javier Martinez Canillas
2022-03-07 20:52 ` [PATCH v2 03/10] drm/client: Use actual bpp when allocating frame buffers Geert Uytterhoeven
2022-03-07 20:52   ` Geert Uytterhoeven
2022-03-09 12:51   ` Javier Martinez Canillas
2022-03-09 12:51     ` Javier Martinez Canillas
2022-03-07 20:52 ` [PATCH v2 04/10] drm/framebuffer: Use actual bpp for DRM_IOCTL_MODE_GETFB Geert Uytterhoeven
2022-03-07 20:52   ` Geert Uytterhoeven
2022-03-09 12:53   ` Javier Martinez Canillas
2022-03-09 12:53     ` Javier Martinez Canillas
2022-03-07 20:52 ` [PATCH v2 05/10] drm/fourcc: Add DRM_FORMAT_C[124] Geert Uytterhoeven
2022-03-07 20:52   ` Geert Uytterhoeven
2022-03-08  9:04   ` Pekka Paalanen
2022-03-08  9:04     ` Pekka Paalanen
2022-03-09 12:57   ` Javier Martinez Canillas
2022-03-09 12:57     ` Javier Martinez Canillas
2022-03-14 13:30   ` Geert Uytterhoeven
2022-03-14 13:30     ` Geert Uytterhoeven
2022-03-14 15:05     ` Pekka Paalanen
2022-03-14 15:05       ` Pekka Paalanen
2022-03-14 19:01       ` Geert Uytterhoeven
2022-03-14 19:01         ` Geert Uytterhoeven
2022-03-14 22:15         ` Finn Thain
2022-03-14 22:15           ` Finn Thain
2022-03-15  7:32           ` Pekka Paalanen
2022-03-15  7:32             ` Pekka Paalanen
2022-03-15  7:51             ` Geert Uytterhoeven
2022-03-15  7:51               ` Geert Uytterhoeven
2022-03-15  7:52               ` Geert Uytterhoeven [this message]
2022-03-15  7:52                 ` Geert Uytterhoeven
2022-03-15  8:45               ` Pekka Paalanen
2022-03-15  8:45                 ` Pekka Paalanen
2022-03-15  8:57                 ` Geert Uytterhoeven
2022-03-15  8:57                   ` Geert Uytterhoeven
2022-03-15 10:48                   ` Pekka Paalanen
2022-03-15 10:48                     ` Pekka Paalanen
2022-03-07 20:52 ` [PATCH v2 06/10] drm/fb-helper: Add support for DRM_FORMAT_C[124] Geert Uytterhoeven
2022-03-07 20:52   ` Geert Uytterhoeven
2022-03-09 13:10   ` Javier Martinez Canillas
2022-03-09 13:10     ` Javier Martinez Canillas
2022-03-09 13:14     ` Geert Uytterhoeven
2022-03-09 13:14       ` Geert Uytterhoeven
2022-03-07 20:52 ` [PATCH v2 RFC 07/10] drm/gem-fb-helper: Use actual bpp for size calculations Geert Uytterhoeven
2022-03-07 20:52   ` Geert Uytterhoeven
2022-03-09 13:16   ` Javier Martinez Canillas
2022-03-09 13:16     ` Javier Martinez Canillas
2022-03-07 20:52 ` [PATCH v2 RFC 08/10] drm/fourcc: Document that single-channel "red" can be any color Geert Uytterhoeven
2022-03-07 20:52   ` Geert Uytterhoeven
2022-03-08  9:06   ` Pekka Paalanen
2022-03-08  9:06     ` Pekka Paalanen
2022-03-09 13:33   ` Javier Martinez Canillas
2022-03-09 13:33     ` Javier Martinez Canillas
2022-03-07 20:52 ` [PATCH v2 RFC 09/10] drm/fourcc: Add DRM_FORMAT_R[124] Geert Uytterhoeven
2022-03-07 20:52   ` Geert Uytterhoeven
2022-03-09 13:39   ` Javier Martinez Canillas
2022-03-09 13:39     ` Javier Martinez Canillas
2022-03-07 20:52 ` [PATCH v2 RFC 10/10] drm/fourcc: Add DRM_FORMAT_D[1248] Geert Uytterhoeven
2022-03-07 20:52   ` Geert Uytterhoeven
2022-03-09 13:41   ` Javier Martinez Canillas
2022-03-09 13:41     ` Javier Martinez Canillas

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=CAMuHMdUOwVLBLmxaVUO4yADVCf1k7CyhBZiesHx2Fr4LW3QWMQ@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fthain@linux-m68k.org \
    --cc=javierm@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=ppaalanen@gmail.com \
    --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 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.