Re: [Xen-devel] [PATCH 4/8] arm: link a device tree blob into the xen image

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Mon, 2012-02-13 at 13:18 +0000, David Vrabel wrote:
> diff --git a/config/arm.mk b/config/arm.mk
> index f64f0c1..f20fd2d 100644
> --- a/config/arm.mk
> +++ b/config/arm.mk
> @@ -16,3 +16,9 @@ LDFLAGS_DIRECT_Linux = _linux
>  LDFLAGS_DIRECT += -marmelf$(LDFLAGS_DIRECT_$(XEN_OS))_eabi
>  
>  CONFIG_LOAD_ADDRESS ?= 0x80000000
> +
> +# XXX: When running on the model there is no bootloader to provide a
> +# device tree.  It must be linked into Xen.
> +ifndef CONFIG_DTB_FILE
> +$(error CONFIG_DTB_FILE must be set to the absolute filename of a
> DTB)
> +endif 

This turns out to be a little aggressive -- it also triggers when you
are building the tools. Not a big deal, but a bit annoying, is there
some way we can avoid this? Put it in xen/arch/arm/Foo perhaps?

Ian.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel