From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47204) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XhGU2-0002C1-PW for qemu-devel@nongnu.org; Thu, 23 Oct 2014 07:23:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XhGTw-0005j4-OG for qemu-devel@nongnu.org; Thu, 23 Oct 2014 07:23:10 -0400 Received: from cantor2.suse.de ([195.135.220.15]:38335 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XhGTw-0005im-Hb for qemu-devel@nongnu.org; Thu, 23 Oct 2014 07:23:04 -0400 Message-ID: <5448E515.80300@suse.de> Date: Thu, 23 Oct 2014 13:23:01 +0200 From: Alexander Graf MIME-Version: 1.0 References: <5448D400.6010503@linaro.org> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] dynamic sysbus instantiation and load_dtb implementation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ard Biesheuvel , Eric Auger Cc: Peter Maydell , qemu list , Alex Williamson , Paolo Bonzini , Antonios Motakis , Christoffer Dall On 23.10.14 12:19, Ard Biesheuvel wrote: >> Dear all, >> >> The goal of this mail is to summarize how dynamic sysbus device tree >> nodes were created on ARM with "machvirt dynamic sysbus device >> instantiation", >> https://lists.gnu.org/archive/html/qemu-devel/2014-09/msg01626.html >> and request some advises after commit "hw/arm/boot: load DTB as a ROM >> image", which puts into question the current implementation. >> > > The reason for this change was that, before, the DTB would only be > generated once, and after a reset, the machine would go through the > kernel boot protocol as before but the DTB pointer would point to > garbage. Any idea how ppc deals with this? Do they recreate the device > tree after each reset? Yes, we regenerate the device tree on each reset. Alex