From: Pekka Paalanen <ppaalanen@gmail.com>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
open list <linux-kernel@vger.kernel.org>,
amd-gfx@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, 11 Apr 2017 10:31:01 +0300 [thread overview]
Message-ID: <20170411103101.0497fe08@eldfell> (raw)
In-Reply-To: <CAKb7UvhbgSGwx-2EsrQrHmghzYqO9AhRQ10bDWKfdcXHc3fJeQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
On Mon, 10 Apr 2017 12:10:14 -0400
Ilia Mirkin <imirkin@alum.mit.edu> wrote:
> On Mon, Apr 10, 2017 at 11:09 AM, Pekka Paalanen <ppaalanen@gmail.com> wrote:
> > I also wonder if a real BE machine could have different results than
> > the virtual machine.
>
> I have a PPC G5 with an AGP GeForce FX 5200 that I can test things on,
> if necessary. (I got it specifically for this purpose, as the people
> who use this type of hw daily tend to perform updates rarely... in no
> small part due to the fact that updates tend to break the HW.)
>
> Just let know what you need tested, I should be able to turn it around
> within a couple of days.
That's part of my problem. I don't really know what should be tested.
What do people do with their BE machines that we should avoid breaking?
I suppose correlating with what Gerd was testing would be nice, i.e.
does X.org with modesetting look right with and without GLAMOR? Maybe
you also want to throw in xf86-video-nouveau for comparison.
As to what apps to test those with... Gerd? I presume anything that does
*not* use OpenGL, since we have doubts of Mesa's correctness on BE,
right? So maybe some of the traditional ancient X11 apps? xterm with
colours?
However, I totally agree with Alex that someone with a BE machine
should review the whole stack before we could be confident with anything.
Thanks,
pq
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-04-11 7:31 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
2017-04-10 12:02 ` Daniel Vetter
2017-04-10 16:28 ` Alex Deucher
2017-04-10 13:12 ` Pekka Paalanen
2017-04-10 14:17 ` Gerd Hoffmann
2017-04-10 14:45 ` Ilia Mirkin
2017-04-10 16:26 ` Alex Deucher
2017-04-10 15:09 ` Pekka Paalanen
2017-04-10 16:10 ` Ilia Mirkin
2017-04-11 7:31 ` Pekka Paalanen [this message]
2017-04-11 11:23 ` Gerd Hoffmann
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
2017-04-18 10:14 ` Gerd Hoffmann
2017-04-19 1:01 ` Michel Dänzer
2017-04-19 3:19 ` Ilia Mirkin
2017-04-19 3:28 ` Ilia Mirkin
2017-04-19 7:09 ` Pekka Paalanen
2017-04-19 12:34 ` Gerd Hoffmann
2017-04-18 10:00 ` Gerd Hoffmann
2017-04-18 11:18 ` Pekka Paalanen
2017-04-18 13:39 ` Gerd Hoffmann
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=20170411103101.0497fe08@eldfell \
--to=ppaalanen@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imirkin@alum.mit.edu \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.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