From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47888) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XhGVp-0004aD-UZ for qemu-devel@nongnu.org; Thu, 23 Oct 2014 07:25:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XhGVk-0006RY-A6 for qemu-devel@nongnu.org; Thu, 23 Oct 2014 07:25:01 -0400 Received: from mail-lb0-f169.google.com ([209.85.217.169]:34993) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XhGVk-0006RI-3w for qemu-devel@nongnu.org; Thu, 23 Oct 2014 07:24:56 -0400 Received: by mail-lb0-f169.google.com with SMTP id 10so639960lbg.14 for ; Thu, 23 Oct 2014 04:24:55 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <5448E515.80300@suse.de> References: <5448D400.6010503@linaro.org> <5448E515.80300@suse.de> From: Peter Maydell Date: Thu, 23 Oct 2014 12:24:34 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] dynamic sysbus instantiation and load_dtb implementation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Eric Auger , Ard Biesheuvel , qemu list , Alex Williamson , Antonios Motakis , Paolo Bonzini , Christoffer Dall On 23 October 2014 12:23, Alexander Graf wrote: > On 23.10.14 12:19, Ard Biesheuvel wrote: >> 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. Any particular reason? Surely it's always the same... -- PMM