All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, andre.przywara@calxeda.com,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: Xen on ARM DT based boot protocol
Date: Thu, 23 May 2013 13:47:04 +0100	[thread overview]
Message-ID: <519E0FC8.3050509@eu.citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1305231335000.4799@kaball.uk.xensource.com>

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

  reply	other threads:[~2013-05-23 12:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 12:39 Xen on ARM DT based boot protocol Stefano Stabellini
2013-05-23 12:47 ` George Dunlap [this message]
2013-05-23 13:22 ` Ian Campbell
2013-05-23 14:07 ` David Vrabel
2013-05-23 21:04   ` Stefano Stabellini
2013-05-23 22:27     ` Andre Przywara
2013-05-24  8:31       ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=519E0FC8.3050509@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=andre.przywara@calxeda.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.