From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Xen on ARM DT based boot protocol Date: Thu, 23 May 2013 13:47:04 +0100 Message-ID: <519E0FC8.3050509@eu.citrix.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" 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: 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. > 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"; > }; > > Are we still on time to make this change on 4.3? Is this just an ARM-specific thing, or would it affect x86 as well? The state of the ARM port when we do the release is up to you guys, so I'm fine with whatever. ARM is still tech-preview anyway, right? No promises (yet) that the interface won't change? So whichever interface you chose, if it turns out to be the wrong one, you can change it for 4.4 if necessary. -George