From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Rob Landley <rob@landley.net>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: Thorsten Glaser <tg@debian.org>, Michael Tokarev <mjt@tls.msk.ru>,
security@debian.org,
Debian QEMU Team <pkg-qemu-devel@lists.alioth.debian.org>,
debian-ports@lists.debian.org
Subject: Re: qemu-system-sh4eb build has something hinky in the ethernet
Date: Mon, 24 Nov 2025 08:18:58 +0100 [thread overview]
Message-ID: <351ebd4d-8ec6-43fe-b308-a0e54801a33b@linaro.org> (raw)
In-Reply-To: <CAMuHMdXZNroJF=s8gXj_vguGPGjUvgLu7w2PZxQg9tcHtSkNyg@mail.gmail.com>
On 1/9/25 09:47, Geert Uytterhoeven wrote:
> On Sun, 24 Aug 2025 at 20:40, Rob Landley <rob@landley.net> wrote:
>> Anyway, this works fine on little endian, but the qemu-system-sh4eb
>> build has something hinky in the ethernet, I haven't tackled it myself
>> because I don't know whether the device emulation or the driver is
>> what's missing an endian swap. (I don't want to fix it the "wrong way",
>
> That is using sh_eth, right?
>
> Last time I tried booting a big-endian ARM kernel on R-Car M2-W,
> the Linux kernel booted fine, except for Ethernet. So sh_eth is definitely
> not big-endian clean.
qemu-system-sh4{eb} only emulates the R2D+ board, which AFAIK
provides ethernet via a RTL8139 over PCI. While old, RTL8139
is very tested and expected to have endianness well handled.
>
> [*] I didn't have a big-endian userspace.
>
> Gr{oetje,eeting}s,
>
> Geert
>
next parent reply other threads:[~2025-11-24 7:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aKi6IWVX2uIlGKnw@seger.debian.org>
[not found] ` <Pine.BSM.4.64L.2508230023030.21591@herc.mirbsd.org>
[not found] ` <6abe2750-5e2c-43a1-be57-1dc2ccabdd91@tls.msk.ru>
[not found] ` <119d5858-52f4-ce1b-9ee7-9615ce2054b9@debian.org>
[not found] ` <79f14fef-123f-4938-b069-10f07e7d0405@landley.net>
[not found] ` <CAMuHMdXZNroJF=s8gXj_vguGPGjUvgLu7w2PZxQg9tcHtSkNyg@mail.gmail.com>
2025-11-24 7:18 ` Philippe Mathieu-Daudé [this message]
2025-11-24 7:31 ` 64mb limitation of qemu-system-sh4 board Philippe Mathieu-Daudé
2025-11-24 7:33 ` John Paul Adrian Glaubitz
2025-11-24 8:48 ` Philippe Mathieu-Daudé
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=351ebd4d-8ec6-43fe-b308-a0e54801a33b@linaro.org \
--to=philmd@linaro.org \
--cc=debian-ports@lists.debian.org \
--cc=geert@linux-m68k.org \
--cc=mjt@tls.msk.ru \
--cc=pkg-qemu-devel@lists.alioth.debian.org \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
--cc=security@debian.org \
--cc=tg@debian.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).