qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Anthony Liguori" <aliguori@us.ibm.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Patch Tracking" <patches@linaro.org>,
	"Will Deacon" <will.deacon@arm.com>,
	qemu-devel@nongnu.org, "Joss Reeves" <joseph.reeves@gmail.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH for-1.5 0/3] hw/pci-host/versatile: Fix issues with newer kernels
Date: Thu, 16 May 2013 18:07:02 +0100	[thread overview]
Message-ID: <CAFEAcA8tvyAr+BJJ8vConSDKOBkgRXUg3erQJM-7hSA=uueyoQ@mail.gmail.com> (raw)
In-Reply-To: <201305161858.57214.arnd@arndb.de>

On 16 May 2013 17:58, Arnd Bergmann <arnd@arndb.de> wrote:
> FWIW, I plan to really get this done in the kernel for 3.11 properly
> and rework the entire versatile and realview code base to work without
> any platform specific code in arch/arm. The plan is to use the new
> infrastructure for PCI and put that code into drivers/pci/host,
> and have it scan the hardware using DT only. We can have a backwards
> compatibility setup for versatile-pb without DT, but in the long
> run, I would prefer to kill off that boot option.

That sounds cool.

> I remember there was a way to autogenerate the dtb blob in qemu at
> some point, based on the devices enabled in the model. Did that ever
> make it in?

Nope, and it never will, except for the extremely limited case
of mach-virt plus some basic stuff like virtio devices. For
ARM you absolutely must pass in the device tree blob that
came with the kernel version you're booting or it's all liable
to crash horribly, fail to find devices or otherwise misbehave,
so the only reliable thing for QEMU to do is make minimal
modifications to the dtb the user gives us.
[Extended version of this rant here:
https://lists.gnu.org/archive/html/qemu-devel/2013-05/msg01877.html ]

thanks
-- PMM

  reply	other threads:[~2013-05-16 17:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14 15:33 [Qemu-devel] [PATCH for-1.5 0/3] hw/pci-host/versatile: Fix issues with newer kernels Peter Maydell
2013-05-14 15:33 ` [Qemu-devel] [PATCH for-1.5 1/3] Revert "versatile_pci: Put the host bridge PCI device at slot 29" Peter Maydell
2013-05-14 15:33 ` [Qemu-devel] [PATCH for-1.5 2/3] hw/pci-host/versatile.c: Update autodetect to detect newer kernels Peter Maydell
2013-05-14 15:33 ` [Qemu-devel] [PATCH for-1.5 3/3] hw/pci-host/versatile.c: Provide property for forcing broken IRQ mapping Peter Maydell
2013-05-15 14:02 ` [Qemu-devel] [PATCH for-1.5 0/3] hw/pci-host/versatile: Fix issues with newer kernels Linus Walleij
2013-05-16 16:58   ` Arnd Bergmann
2013-05-16 17:07     ` Peter Maydell [this message]
2013-05-17 11:50     ` Linus Walleij
2013-05-17 12:10       ` Peter Maydell
2013-05-16 12:50 ` Anthony Liguori

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='CAFEAcA8tvyAr+BJJ8vConSDKOBkgRXUg3erQJM-7hSA=uueyoQ@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=arnd@arndb.de \
    --cc=aurelien@aurel32.net \
    --cc=joseph.reeves@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=mst@redhat.com \
    --cc=patches@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=will.deacon@arm.com \
    /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).