From: Gerd Hoffmann <kraxel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Pekka Paalanen <ppaalanen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Daniel Vetter
<daniel.vetter-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
open list <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality.
Date: Mon, 10 Apr 2017 16:17:27 +0200 [thread overview]
Message-ID: <1491833847.30990.77.camel@redhat.com> (raw)
In-Reply-To: <20170410161214.305f5daf@eldfell>
Hi,
> which software have you used as representative of "reality"?
ppc64 (big endian) virtual machine, running with qemu stdvga & bochs-drm
driver. Xorg with modesetting driver uses DRM_FORMAT_XRGB8888 (one and
only format supported by bochs-drm), and we have to interpret that in
bigendian byte order on the host side to get a correct display.
Didn't try wayland. Can do, but will take a while. Don't have a
wayland-capable guest install at hand, and installing one takes a while
because I don't have a physical pseries and emulation is slooooww.
> To solve that problem, we would like to know if anything existing would
> break for each possible solution, but no developers using BE have really
> turned up.
That is part of the problem.
And even ppc is moving to little endian these days ...
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-10 14:17 UTC|newest]
Thread overview: 28+ 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
[not found] ` <20170410101202.19229-1-kraxel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-04-10 12:02 ` Daniel Vetter
[not found] ` <20170410120212.3igweieunldjcjuy-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2017-04-10 16:28 ` Alex Deucher
2017-04-10 13:12 ` Pekka Paalanen
2017-04-10 14:17 ` Gerd Hoffmann [this message]
[not found] ` <1491833847.30990.77.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-04-10 14:45 ` Ilia Mirkin
[not found] ` <CAKb7Uvgidg9_RkU0NJY7qwhcf0_Hyc0EGzWmvk0qqaf_YDW97g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-10 16:26 ` Alex Deucher
2017-04-10 15:09 ` Pekka Paalanen
2017-04-10 16:10 ` Ilia Mirkin
[not found] ` <CAKb7UvhbgSGwx-2EsrQrHmghzYqO9AhRQ10bDWKfdcXHc3fJeQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-11 7:31 ` Pekka Paalanen
2017-04-11 11:23 ` Gerd Hoffmann
[not found] ` <1491909833.30990.93.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-04-13 7:44 ` Pekka Paalanen
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 5:04 ` Ilia Mirkin
2017-04-18 5:58 ` Michel Dänzer
[not found] ` <fe944ecc-3ca4-26d8-77bc-873a53dcbb3f-otUistvHUpPR7s880joybQ@public.gmane.org>
2017-04-18 10:14 ` Gerd Hoffmann
[not found] ` <1492510440.27392.27.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-04-19 1:01 ` Michel Dänzer
2017-04-19 3:19 ` Ilia Mirkin
2017-04-19 3:28 ` Ilia Mirkin
[not found] ` <4230c093-6a8a-76d6-dce8-f9b2300fa70f-otUistvHUpPR7s880joybQ@public.gmane.org>
2017-04-19 7:09 ` Pekka Paalanen
2017-04-19 12:34 ` Gerd Hoffmann
2017-04-18 10:00 ` Gerd Hoffmann
[not found] ` <1492509617.27392.19.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-04-18 11:18 ` Pekka Paalanen
2017-04-18 13:39 ` Gerd Hoffmann
[not found] ` <1492522793.27392.55.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-04-18 14:01 ` Pekka Paalanen
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=1491833847.30990.77.camel@redhat.com \
--to=kraxel-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=daniel.vetter-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ppaalanen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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