qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] x86: Manage BIOS boot menu via command line
Date: Thu, 18 Dec 2008 10:27:24 -0600	[thread overview]
Message-ID: <494A79EC.8000600@codemonkey.ws> (raw)
In-Reply-To: <494A4A55.2090700@siemens.com>


> diff --git a/pc-bios/bios-pq/0006_optional-boot-menu.patch b/pc-bios/bios-pq/0006_optional-boot-menu.patch
> new file mode 100644
> index 0000000..bbe5753
> --- /dev/null
> +++ b/pc-bios/bios-pq/0006_optional-boot-menu.patch
> @@ -0,0 +1,19 @@
> +Make interactive boot menu optional.
> +
> +Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> +
> +diff --git a/bios/rombios.c b/bios/rombios.c
> +index 123672f..7ce5b6c 100644
> +--- a/bios/rombios.c
> ++++ b/bios/rombios.c
> +@@ -2026,6 +2026,10 @@ interactive_bootkey()
> +   Bit16u ss = get_SS();
> +   Bit16u valid_choice = 0;
> + 
> ++  /* QEMU sets CMOS byte 0x60 to non-zero if the boot menu should be skipped */
> ++  if (inb_cmos(0x60))
> ++    return;
> ++
>   

Should we be using firmware config for this?

I think I'd still like to see BIOS patches submitted as separate 
patches.  We'll take care of updating the series file and sticking them 
into the right place.  Diffs of diffs are pretty hard for me to read :-)

Regards,

Anthony Liguori

      parent reply	other threads:[~2008-12-18 16:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18 13:04 [Qemu-devel] [PATCH] x86: Manage BIOS boot menu via command line Jan Kiszka
2008-12-18 13:30 ` Gleb Natapov
2008-12-18 16:06   ` [Qemu-devel] " Jan Kiszka
2008-12-18 16:20 ` [Qemu-devel] " Paul Brook
2008-12-18 16:28   ` Anthony Liguori
2008-12-18 16:57     ` Jan Kiszka
2008-12-18 17:23       ` Anthony Liguori
2008-12-18 17:41         ` Gleb Natapov
2008-12-18 18:43           ` Laurent Vivier
2008-12-18 21:28             ` [Qemu-devel] " Jan Kiszka
2008-12-18 16:27 ` Anthony Liguori [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=494A79EC.8000600@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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).