From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:52682) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ud1eK-0002wA-5z for qemu-devel@nongnu.org; Thu, 16 May 2013 13:07:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ud1eG-0003Ub-D3 for qemu-devel@nongnu.org; Thu, 16 May 2013 13:07:28 -0400 Received: from mail-la0-x231.google.com ([2a00:1450:4010:c03::231]:55380) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ud1eG-0003UO-6o for qemu-devel@nongnu.org; Thu, 16 May 2013 13:07:24 -0400 Received: by mail-la0-f49.google.com with SMTP id fp13so2654632lab.36 for ; Thu, 16 May 2013 10:07:22 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <201305161858.57214.arnd@arndb.de> References: <1368545616-22344-1-git-send-email-peter.maydell@linaro.org> <201305161858.57214.arnd@arndb.de> From: Peter Maydell Date: Thu, 16 May 2013 18:07:02 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH for-1.5 0/3] hw/pci-host/versatile: Fix issues with newer kernels List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Arnd Bergmann Cc: Anthony Liguori , "Michael S. Tsirkin" , Linus Walleij , Patch Tracking , Will Deacon , qemu-devel@nongnu.org, Joss Reeves , =?UTF-8?Q?Andreas_F=C3=A4rber?= , Aurelien Jarno On 16 May 2013 17:58, Arnd Bergmann 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