qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [RESEND][PATCH v2 1/2] Rework -boot option
Date: Mon, 29 Jun 2009 08:50:18 +0200	[thread overview]
Message-ID: <4A48642A.1090500@web.de> (raw)
In-Reply-To: <A9DBB5A444BD4F09A2CE0F5733ED76DB@FSCPC>

[-- Attachment #1: Type: text/plain, Size: 850 bytes --]

Sebastian Herbszt wrote:
> Jan Kiszka wrote:
>> This patch changes the boot command line option to the canonical format
>>
>>  -boot [order=]drives[,interactive=on|off]
>>
>> where 'drives' is using the same format as the old -boot. The format
>> switch allows to add the 'interactive' option and use the existing
>> infrastructure to parse it. However, the old format is still understood
>> and will be processed at least for a transition time.
>>
>> The state of 'interactive' is transfered to the firmware via the new
>> configuration value FW_CFG_BOOT_INTERACTIVE.
> 
> What about using "[boot]menu" instead of "interactive"?
> The Phoenix BIOS i got here allows me to enable/disable the boot menu,
> so this seems common.

Yes, short is beautiful. Will sent out a new series, addressing all
suggestions made so far.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

      reply	other threads:[~2009-06-29  6:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-27  8:11 [Qemu-devel] [RESEND][PATCH v2 1/2] Rework -boot option Jan Kiszka
2009-06-28 16:54 ` Avi Kivity
2009-06-28 18:15   ` [Qemu-devel] " Jan Kiszka
2009-06-28 19:40 ` Sebastian Herbszt
2009-06-29  6:50   ` Jan Kiszka [this message]

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=4A48642A.1090500@web.de \
    --to=jan.kiszka@web.de \
    --cc=aliguori@us.ibm.com \
    --cc=herbszt@gmx.de \
    --cc=qemu-devel@nongnu.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).