From: Peter Maydell <peter.maydell@linaro.org>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
qemu-ppc <qemu-ppc@nongnu.org>, Greg Kurz <groug@kaod.org>,
Guenter Roeck <linux@roeck-us.net>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] hw: ppc: sam460ex: Disable Ethernet devicetree nodes
Date: Tue, 17 Aug 2021 10:42:32 +0100 [thread overview]
Message-ID: <CAFEAcA8x5Ne2=WF2NXDsO-6GO=Lbw+8qXx3KR7BhebVPkpiHXQ@mail.gmail.com> (raw)
In-Reply-To: <28b9ae3d-80b8-f48b-dfe6-9b895d5c5db3@eik.bme.hu>
On Tue, 17 Aug 2021 at 10:25, BALATON Zoltan <balaton@eik.bme.hu> wrote:
> We could also modify the pc-bios/canyonlands.dts to comment out the
> ethernet ports from it or add the disabled properties there, maybe also
> adding a comment that explains these are not emulated in QEMU but to me
> keeping the dts unmodified, matching real hardware and let the board code
> patch it according to what's emulated looks more obvious to clearly show
> what changes we have from the originial hardware which would be less clear
> if we loaded a modified dtb. Modifying the dtb simplifies the board code
> but hides the differences from real hardware. So since we already have to
> modify the loaded dtb anyway I'm OK with changing it at the same place as
> this patch proposes.
If this was preventing Linux from booting then I'd be a bit more
inclined to it. But it doesn't sound like it's actually doing that?
AIUI you just get a couple of non-functional ethernet interfaces
that can be ignored, and "some devices don't actually work" is
pretty much par-for-the-course for most QEMU models...
-- PMM
next prev parent reply other threads:[~2021-08-17 9:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 2:59 [PATCH] hw: ppc: sam460ex: Disable Ethernet devicetree nodes Guenter Roeck
2021-08-16 5:41 ` David Gibson
2021-08-16 10:11 ` Philippe Mathieu-Daudé
2021-08-16 15:13 ` Guenter Roeck
2021-08-16 10:21 ` BALATON Zoltan
2021-08-17 3:06 ` David Gibson
2021-08-17 9:24 ` BALATON Zoltan
2021-08-17 9:42 ` Peter Maydell [this message]
2021-08-16 10:26 ` Peter Maydell
2021-08-16 10:58 ` Philippe Mathieu-Daudé
2021-08-16 11:58 ` BALATON Zoltan
2021-08-17 3:09 ` David Gibson
2021-08-16 13:59 ` Guenter Roeck
2021-08-16 14:03 ` Peter Maydell
2021-08-16 14:11 ` Guenter Roeck
2021-08-16 14:19 ` Peter Maydell
2021-08-16 14:57 ` Guenter Roeck
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='CAFEAcA8x5Ne2=WF2NXDsO-6GO=Lbw+8qXx3KR7BhebVPkpiHXQ@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=linux@roeck-us.net \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).