From: Fu Wei <fu.wei@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>,
Roy Franz <roy.franz@linaro.org>,
leif Lindholm <leif.lindholm@linaro.org>
Cc: tim@xen.org, stefano.stabellini@citrix.com, jbeulich@suse.com,
xen-devel@lists.xen.org
Subject: Re: [PATCH V2 for-4.5] EFI: Always use EFI command line
Date: Sat, 25 Oct 2014 17:27:03 +0800 [thread overview]
Message-ID: <544B6CE7.5010905@linaro.org> (raw)
In-Reply-To: <1414227980.3584.15.camel@citrix.com>
On 10/25/2014 05:06 PM, Ian Campbell wrote:
> On Fri, 2014-10-24 at 16:41 -0700, Roy Franz wrote:
>> (I'm not sure how I'm supposed to refer to to docs/misc/efi.markdown in
>> the booting.txt. Should I assume that it will be processed to html
>> and refrence it that way?)
>
> This stuff kinda sucks because it all depends on where you build and
> install to etc. What you've done in naming the file as it appears in the
> source is fine. Other places use a reference to the canonical online
> copy at http://xenbits.xen.org/docs/unstable/ which is fine too I think.
>
>> @@ -104,4 +106,6 @@ and really not meant to be used together with the `-cfg=` command line option.
>> Filenames must be specified relative to the location of the EFI binary.
>>
>> Extra options to be passed to Xen can also be specified on the command line,
>> -following a `--` separator option.
>> +following a `--` separator option.
>
> Will grub automatically insert this "--" marker? Or is there some
> special handling in Xen when none of -cfg/-help/-videothing are present?
> (Doesn't look to be the case)
For now, I didn't make this automatically "--" injection.
Do we need to do this, or just let user do it by themselves?
In my opinion, according to the wiki page, we should make the injection?
http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Multiboot
any thought and suggestion?? :-)
>
> Ian.
>
--
Best regards,
Fu Wei
Software Engineer From Red Hat
LEG Team
Linaro.org | Open source software for ARM SoCs
Ph: +86 186 2020 4684 (mobile)
IRC: fuwei
Skype: tekkamanninja
Room 1512, Regus One Corporate Avenue,Level 15,
One Corporate Avenue,222 Hubin Road,Huangpu District,
Shanghai,China 200021
next prev parent reply other threads:[~2014-10-25 9:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 23:41 [PATCH V2 for-4.5] EFI: Always use EFI command line Roy Franz
2014-10-25 9:06 ` Ian Campbell
2014-10-25 9:27 ` Fu Wei [this message]
2014-10-25 10:22 ` Fu Wei
2014-10-25 19:18 ` Roy Franz
2014-10-27 10:55 ` Jan Beulich
2014-10-27 22:29 ` Roy Franz
2014-10-28 1:15 ` Konrad Rzeszutek Wilk
2014-10-28 7:48 ` Jan Beulich
2014-10-29 3:23 ` Roy Franz
2014-10-29 8:40 ` Jan Beulich
2014-10-29 12:44 ` Daniel Kiper
2014-10-29 15:26 ` Ian Campbell
2014-10-29 16:55 ` Daniel Kiper
2014-10-30 2:21 ` Roy Franz
2014-10-30 9:49 ` Jan Beulich
2014-10-30 10:24 ` Ian Campbell
2014-10-30 17:57 ` Daniel Kiper
2014-10-30 19:29 ` Roy Franz
2014-10-30 22:18 ` Daniel Kiper
2014-10-30 23:54 ` Roy Franz
2014-11-04 21:49 ` Daniel Kiper
2014-11-04 22:48 ` Roy Franz
2014-11-05 14:30 ` Daniel Kiper
2014-11-06 5:35 ` Roy Franz
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=544B6CE7.5010905@linaro.org \
--to=fu.wei@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=jbeulich@suse.com \
--cc=leif.lindholm@linaro.org \
--cc=roy.franz@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).