From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCH 4/8] arm: link a device tree blob into the xen image Date: Fri, 10 Feb 2012 13:40:53 +0000 Message-ID: <4F351E65.6020604@citrix.com> References: <1328879024-5621-1-git-send-email-david.vrabel@citrix.com> <1328879024-5621-5-git-send-email-david.vrabel@citrix.com> <1328880943.6133.264.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1328880943.6133.264.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 10/02/12 13:35, Ian Campbell wrote: > On Fri, 2012-02-10 at 13:03 +0000, David Vrabel wrote: >> From: David Vrabel >> >> Link a device tree blob (DTB) into the xen image. This is loaded >> immediately after Xen and xen_start() is called with the correct >> address in atag_paddr. > > Is platform.dtb supposed to be included in this patch/series or is it > intended that I should supply it from somewhere? (in which case, how and > where etc). I make a symlink to vexpress-v2p-aem-v7a.dtb built in my Linux tree. Would it be better build the DTB from source included in Xen? Or specify the DTB in some other way (makefile variables?)? David