From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] RFC: BIOS filename option
Date: Thu, 04 Oct 2007 05:11:55 +0200 [thread overview]
Message-ID: <1191467515.31950.41.camel@rapid> (raw)
Hi,
This is a proposal to allow the user to select a BIOS file name on the
command line. The goal is mainly to ease debug, for example when I want
to try to run a firmware comming from a real machine instead of the
default one.
The only change is to add a -bios <filename> option, use the given file
if any or use the default if none were given.
Maybe the options would be better named as -biosfile.... Or it maybe a
good idea to give a full path, not to concatenate the given name with
the bios_dir prefix...
Some may find this option is not so useful, as one can specify a
directory to find the target BIOS. But I feel more confortable keeping
all BIOS images together at the same place.
Please comment.
--
J. Mayer <l_indien@magic.fr>
Never organized
next reply other threads:[~2007-10-04 3:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 3:11 J. Mayer [this message]
2007-10-04 11:38 ` [Qemu-devel] RFC: BIOS filename option Thiemo Seufer
2007-10-05 12:36 ` J. Mayer
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=1191467515.31950.41.camel@rapid \
--to=l_indien@magic.fr \
--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).