Re: [Xen-devel] [PATCHv4 00/04] arm: pass a device tree to dom0

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Mon, 2012-04-02 at 11:50 +0100, David Vrabel wrote:
> We don't yet make use of the device tree to map MMIO regions or setup
> interrupts for the guest and we still include the UART used for Xen's
> console.
> 
> Note the kernel must support device tree (ATAGS are no longer provided
> by Xen).
> 
> It is also possible to provide the Xen and dom0 command line via the
> device tree.  This isn't as useful as it seems as Xen still needs to
> be rebuilt to included the updated device tree.

Applied, thanks.

BTW, I dropped the dump of the DT tree, it's ok for debugging DT
specifically but a bit much for normal use.

> The instructions on the wiki[1] have been updated to reflect these
> changes.

There's a reference to "make dtbs" in there, should that be changed to
reflect the need to use a DTB from your device-tree.git (which has a
differently named target)?

Ian.

> 
> Changes since v3:
>   - dropped already applied patches
>   - tweaked set_memory_reg() to be a bit more readable.
> 
> Changes since v2:
>   - dropped already applied patches
>   - fix crash on boot if bootargs is missing
>   - allow space in dom0's dtb for the mem reserve entry
>   - bail if dom0's dtb couldn't be created
>   - new patch to print warning if a node is nested too deep
> 
> Changes since v1:
>   - coding style
>   - move libfdt headers
>   - added myself as device tree maintainer
>   - fix potential infinite loop when assigning mem
>   - check dtb destination more carefully
>   - minor updates for clarity
> 
> David
> 
> [1] http://wiki.xen.org/wiki/Xen_ARMv7_with_Virtualization_Extensions



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel