From: Thomas Zimmermann <tzimmermann@suse.de>
To: Arnd Bergmann <arnd@arndb.de>,
Javier Martinez Canillas <javierm@redhat.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Helge Deller <deller@gmx.de>,
maxime@cerno.tech, sam@ravnborg.org,
Michal Suchanek <msuchanek@suse.de>,
Michael Ellerman <mpe@ellerman.id.au>,
benh@kernel.crashing.org, Paul Mackerras <paulus@samba.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
mark.cave-ayland@ilande.co.uk
Cc: linux-fbdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v4 5/5] drm/ofdrm: Support big-endian scanout buffers
Date: Wed, 12 Oct 2022 10:27:38 +0200 [thread overview]
Message-ID: <c80a6e2d-a3b9-8186-cc95-97c4775171ed@suse.de> (raw)
In-Reply-To: <f26ca6a1-feb1-4822-ac96-bc484b22f8a0@app.fastmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1225 bytes --]
Hi
Am 12.10.22 um 09:44 schrieb Arnd Bergmann:
> On Wed, Oct 12, 2022, at 9:40 AM, Thomas Zimmermann wrote:
>> Am 12.10.22 um 09:17 schrieb Arnd Bergmann:
>>> On Wed, Oct 12, 2022, at 8:46 AM, Thomas Zimmermann wrote:
>>
>>> Does qemu mark the device has having a particular endianess then, or
>>> does it switch the layout of the framebuffer to match what the CPU
>>> does?
>>
>> The latter. On neither architecture does qemu expose this flag. The
>> default endianess corresponds to the host.
>
> "host" as in the machine that qemu runs on, or the machine that is
> being emulated? I suppose it would be broken either way, but in the
> latter case, we could get away with detecting that the machine is
> running under qemu.
Sorry, my mistake. I meant "guest": the endianess of the framebuffer
corresponds to the endianess of the emulated machine. Given that many
graphics cards support LE and BE modes, I assume that this behavior
mimics real-hardware systems.
Best regards
Thomas
>
> Arnd
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-10-12 8:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 10:50 [PATCH v4 0/5] drm: Add driver for PowerPC OF displays Thomas Zimmermann
2022-09-28 10:50 ` [PATCH v4 1/5] drm/ofdrm: Add ofdrm for Open Firmware framebuffers Thomas Zimmermann
2022-09-28 10:50 ` [PATCH v4 2/5] drm/ofdrm: Add CRTC state Thomas Zimmermann
2022-09-28 10:50 ` [PATCH v4 3/5] drm/ofdrm: Add per-model device function Thomas Zimmermann
2022-09-28 10:50 ` [PATCH v4 4/5] drm/ofdrm: Support color management Thomas Zimmermann
2022-09-28 10:50 ` [PATCH v4 5/5] drm/ofdrm: Support big-endian scanout buffers Thomas Zimmermann
2022-09-28 11:12 ` Michal Suchánek
2022-09-28 11:30 ` Thomas Zimmermann
2022-10-11 7:46 ` Javier Martinez Canillas
2022-10-11 11:30 ` Thomas Zimmermann
2022-10-11 20:06 ` Arnd Bergmann
2022-10-11 21:38 ` Michal Suchánek
2022-10-12 6:46 ` Thomas Zimmermann
2022-10-12 7:17 ` Arnd Bergmann
2022-10-12 7:40 ` Thomas Zimmermann
2022-10-12 7:44 ` Arnd Bergmann
2022-10-12 8:27 ` Thomas Zimmermann [this message]
2022-10-12 8:38 ` Arnd Bergmann
2022-10-12 12:00 ` Thomas Zimmermann
2022-10-12 13:12 ` Arnd Bergmann
2022-10-12 14:27 ` Michal Suchánek
2022-10-13 7:39 ` Javier Martinez Canillas
2022-10-17 6:44 ` Benjamin Herrenschmidt
2022-10-12 14:31 ` Thomas Zimmermann
2022-10-12 14:59 ` Ville Syrjälä
2022-10-12 16:01 ` Michal Suchánek
2022-10-12 12:07 ` Michal Suchánek
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=c80a6e2d-a3b9-8186-cc95-97c4775171ed@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=maxime@cerno.tech \
--cc=mpe@ellerman.id.au \
--cc=msuchanek@suse.de \
--cc=paulus@samba.org \
--cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).