From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: Xen on ARM DT based boot protocol Date: Thu, 23 May 2013 15:07:00 +0100 Message-ID: <519E2284.9050604@citrix.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini Cc: george.dunlap@eu.citrix.com, xen-devel@lists.xensource.com, andre.przywara@calxeda.com, Ian Campbell List-Id: xen-devel@lists.xenproject.org On 23/05/13 13:39, Stefano Stabellini wrote: > Hi Ian, > Andre was pointing out to me today that the current boot protocol has a > problem: > > > chosen { > bootargs = "dom0_mem=128M console=com1,vga"; > xen,dom0-bootargs = "earlyprintk=xenboot console=ttyAMA1 root=/dev/mmcblk0 debug rw init=/bin/bash"; > }; > > > because we are using bootargs for Xen arguments, the bootloader cannot > just pass the same two lines to Xen on ARM and to Linux on ARM. I think it is unlikely the command line arguments for Linux are the same for bare metal and dom0. Even in this example here you have a Xen-specific option (earlyprintk=xenboot). > It would make their life easier if we had instead: > > > chosen { > xen,xen-bootarg = "dom0_mem=128M console=com1,vga"; > bootargs = "earlyprintk=xenboot console=ttyAMA1 root=/dev/mmcblk0 debug rw init=/bin/bash"; > }; David