[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] dynamic sysbus instantiation and load_dtb implementatio
|
From: |
Alexander Graf |
|
Subject: |
Re: [Qemu-devel] dynamic sysbus instantiation and load_dtb implementation |
|
Date: |
Thu, 23 Oct 2014 13:23:01 +0200 |
|
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 |
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