On 19.06.2012, at 22:51, Peter Maydell wrote:
> On 19 June 2012 20:15, Alexander Graf wrote:
>> Now that we are dynamically creating the dtb, it's really useful to
>> be able to dump the created blob for debugging.
>
>> @@ -300,6 +302,22 @@ static int mpc8544_load_device_tree(CPUPPCState *env,
On 19 June 2012 20:15, Alexander Graf wrote:
> Now that we are dynamically creating the dtb, it's really useful to
> be able to dump the created blob for debugging.
> @@ -300,6 +302,22 @@ static int mpc8544_load_device_tree(CPUPPCState *env,
> qemu_devtree_setprop_cell(fdt, pci, "#address-cel
Now that we are dynamically creating the dtb, it's really useful to
be able to dump the created blob for debugging.
This patch implements a -machine dumpdtb= option for e500 that
dumps the dtb exactly in the form the guest would get it to disk. It
can then be analyzed by dtc to get information abo
Now that we are dynamically creating the dtb, it's really useful to
be able to dump the created blob for debugging.
This patch implements a -machine dumpdtb= option for e500 that
dumps the dtb exactly in the form the guest would get it to disk. It
can then be analyzed by dtc to get information abo
