On Wed, Jul 16, 2025 at 11:54:28AM +0200, Luc Michel wrote:
> Add a note in the DTB section explaining how to dump the generated DTB
> using the dumpdtb machine option.
>
> Signed-off-by: Luc Michel <luc.michel@amd.com>
Reviewed-by: Francisco Iglesias <francisco.iglesias@amd.com>
> ---
> docs/system/arm/xlnx-versal-virt.rst | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/docs/system/arm/xlnx-versal-virt.rst b/docs/system/arm/xlnx-versal-virt.rst
> index 94c8bacf61a..5d7fa18592b 100644
> --- a/docs/system/arm/xlnx-versal-virt.rst
> +++ b/docs/system/arm/xlnx-versal-virt.rst
> @@ -63,11 +63,17 @@ Users can load firmware or boot-loaders with the ``-device loader`` options.
>
> When loading an OS, QEMU generates a DTB and selects an appropriate address
> where it gets loaded. This DTB will be passed to the kernel in register x0.
>
> If there's no ``-kernel`` option, we generate a DTB and place it at 0x1000
> -for boot-loaders or firmware to pick it up.
> +for boot-loaders or firmware to pick it up. To dump and observe the generated
> +DTB, one can use the ``dumpdtb`` machine option:
> +
> +.. code-block:: bash
> +
> + $ qemu-system-aarch64 -M amd-versal-virt,dumpdtb=example.dtb -m 2G
> +
>
> If users want to provide their own DTB, they can use the ``-dtb`` option.
> These DTBs will have their memory nodes modified to match QEMU's
> selected ram_size option before they get passed to the kernel or FW.
>
> --
> 2.50.0
>