From: Gerd Hoffmann <kraxel@redhat.com>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: Ilia Mirkin <imirkin@alum.mit.edu>,
amd-gfx@lists.freedesktop.org,
open list <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality.
Date: Tue, 18 Apr 2017 12:14:00 +0200 [thread overview]
Message-ID: <1492510440.27392.27.camel@redhat.com> (raw)
In-Reply-To: <fe944ecc-3ca4-26d8-77bc-873a53dcbb3f@daenzer.net>
Hi,
> > Quite true that this proves nothing. However one should note that
> > fbcon -> fbdev works,
>
> BTW, this supports Gerd's patch, since the KMS fbdev emulation code uses
> e.g. DRM_FORMAT_XRGB8888 for depth/bpp 24/32, and the fbdev API uses
> native endian packed colour values.
Same is true for DRM_IOCTL_MODE_ADDFB, with depth/bpp 24/32 you'll get
DRM_FORMAT_XRGB8888 (only DRM_IOCTL_MODE_ADDFB2 allows userspace specify
fourcc formats directly).
cheers,
Gerd
WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>
Cc: Daniel Vetter
<daniel.vetter-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>,
open list <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality.
Date: Tue, 18 Apr 2017 12:14:00 +0200 [thread overview]
Message-ID: <1492510440.27392.27.camel@redhat.com> (raw)
In-Reply-To: <fe944ecc-3ca4-26d8-77bc-873a53dcbb3f-otUistvHUpPR7s880joybQ@public.gmane.org>
Hi,
> > Quite true that this proves nothing. However one should note that
> > fbcon -> fbdev works,
>
> BTW, this supports Gerd's patch, since the KMS fbdev emulation code uses
> e.g. DRM_FORMAT_XRGB8888 for depth/bpp 24/32, and the fbdev API uses
> native endian packed colour values.
Same is true for DRM_IOCTL_MODE_ADDFB, with depth/bpp 24/32 you'll get
DRM_FORMAT_XRGB8888 (only DRM_IOCTL_MODE_ADDFB2 allows userspace specify
fourcc formats directly).
cheers,
Gerd
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2017-04-18 10:14 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 10:12 [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality Gerd Hoffmann
2017-04-10 10:12 ` Gerd Hoffmann
2017-04-10 12:02 ` Daniel Vetter
2017-04-10 12:02 ` Daniel Vetter
2017-04-10 16:28 ` Alex Deucher
2017-04-10 16:28 ` Alex Deucher
2017-04-10 13:12 ` Pekka Paalanen
2017-04-10 13:12 ` Pekka Paalanen
2017-04-10 14:17 ` Gerd Hoffmann
2017-04-10 14:17 ` Gerd Hoffmann
2017-04-10 14:45 ` Ilia Mirkin
2017-04-10 14:45 ` Ilia Mirkin
2017-04-10 16:26 ` Alex Deucher
2017-04-10 16:26 ` Alex Deucher
2017-04-10 15:09 ` Pekka Paalanen
2017-04-10 15:09 ` Pekka Paalanen
2017-04-10 16:10 ` Ilia Mirkin
2017-04-10 16:10 ` Ilia Mirkin
2017-04-11 7:31 ` Pekka Paalanen
2017-04-11 7:31 ` Pekka Paalanen
2017-04-11 11:23 ` Gerd Hoffmann
2017-04-11 11:23 ` Gerd Hoffmann
2017-04-13 7:44 ` Pekka Paalanen
2017-04-13 7:44 ` Pekka Paalanen
2017-04-11 14:18 ` Ilia Mirkin
2017-04-11 14:18 ` Ilia Mirkin
2017-04-17 6:43 ` Ilia Mirkin
2017-04-18 2:53 ` Michel Dänzer
2017-04-18 2:53 ` Michel Dänzer
2017-04-18 5:04 ` Ilia Mirkin
2017-04-18 5:04 ` Ilia Mirkin
2017-04-18 5:58 ` Michel Dänzer
2017-04-18 5:58 ` Michel Dänzer
2017-04-18 10:14 ` Gerd Hoffmann [this message]
2017-04-18 10:14 ` Gerd Hoffmann
2017-04-19 1:01 ` Michel Dänzer
2017-04-19 1:01 ` Michel Dänzer
2017-04-19 3:19 ` Ilia Mirkin
2017-04-19 3:19 ` Ilia Mirkin
2017-04-19 3:28 ` Ilia Mirkin
2017-04-19 3:28 ` Ilia Mirkin
2017-04-19 7:09 ` Pekka Paalanen
2017-04-19 7:09 ` Pekka Paalanen
2017-04-19 12:34 ` Gerd Hoffmann
2017-04-19 12:34 ` Gerd Hoffmann
2017-04-18 10:00 ` Gerd Hoffmann
2017-04-18 10:00 ` Gerd Hoffmann
2017-04-18 11:18 ` Pekka Paalanen
2017-04-18 11:18 ` Pekka Paalanen
2017-04-18 13:39 ` Gerd Hoffmann
2017-04-18 13:39 ` Gerd Hoffmann
2017-04-18 14:01 ` Pekka Paalanen
2017-04-18 14:01 ` Pekka Paalanen
2017-04-18 20:50 ` Gerd Hoffmann
2017-04-18 20:50 ` Gerd Hoffmann
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=1492510440.27392.27.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imirkin@alum.mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
/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.