From: Anthony Liguori <anthony@codemonkey.ws>
To: Jordan Justen <jljusten@gmail.com>
Cc: Gleb Natapov <gleb@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel <qemu-devel@nongnu.org>,
Michal Suchanek <hramrach@centrum.cz>,
Kevin O'Connor <kevin@koconnor.net>, Avi Kivity <avi@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [Qemu-devel] Re: RFC: emulation of system flash
Date: Thu, 10 Mar 2011 13:23:36 -0600 [thread overview]
Message-ID: <4D792538.4030407@codemonkey.ws> (raw)
In-Reply-To: <AANLkTinoxO_juZe=but=C692r+5ZWQ_6CUz37dfzTgr6@mail.gmail.com>
On 03/10/2011 01:03 PM, Jordan Justen wrote:
> On Thu, Mar 10, 2011 at 03:46, Jan Kiszka<jan.kiszka@siemens.com> wrote:
>> On 2011-03-10 12:27, Jan Kiszka wrote:
>>> On 2011-03-10 10:47, Gleb Natapov wrote:
>>>> My suggestion is to extend
>>>> -bios option like this:
>>>>
>>>> -bios bios.bin,flash=flash.bin,flash_base=addr
>>>>
>>>> flash.bin will be mapped at address flash_base, or, if flash_base is not
>>>> present, just below bios.bin.
>>> ...or define -flash in a way that allows mapping the bios image as an
>>> overlay to the otherwise guest-managed flash image.
>> Better define flash chips as qdev devices and make the attributes qdev
>> properties:
>>
>> -device flash,image=...,base=...,overlay=...,overlay_start=...
> I was hoping it would not necessarily require a script to run OVMF. :)
>
> The original proposal would have allowed for:
>
> qemu -L . -flash ovmf.fd
If you implement a CSM for Tiano Core, then you won't need to use any
special parameters because we can just use OVMF by default ;-)
Regards,
Anthony Liguori
> -Jordan
>
next prev parent reply other threads:[~2011-03-10 19:23 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 4:51 [Qemu-devel] RFC: emulation of system flash Jordan Justen
2011-03-10 9:10 ` [Qemu-devel] " Avi Kivity
2011-03-10 18:43 ` Jordan Justen
2011-03-10 21:52 ` Carl-Daniel Hailfinger
2011-03-10 22:14 ` Jordan Justen
2011-03-10 22:31 ` Carl-Daniel Hailfinger
2011-03-10 22:58 ` Jordan Justen
2011-03-10 23:41 ` Carl-Daniel Hailfinger
2011-03-11 2:12 ` Jordan Justen
2011-03-10 9:47 ` Gleb Natapov
2011-03-10 11:27 ` Jan Kiszka
2011-03-10 11:46 ` Jan Kiszka
2011-03-10 11:53 ` Paolo Bonzini
2011-03-10 12:07 ` Jan Kiszka
2011-03-10 19:03 ` Jordan Justen
2011-03-10 19:23 ` Anthony Liguori [this message]
2011-03-10 20:05 ` Jordan Justen
2011-03-10 11:48 ` Gleb Natapov
2011-03-10 12:06 ` Jan Kiszka
2011-03-10 12:17 ` Gleb Natapov
2011-03-10 12:27 ` Jan Kiszka
2011-03-10 19:08 ` Jordan Justen
2011-03-10 19:13 ` Gleb Natapov
2011-03-10 21:46 ` Carl-Daniel Hailfinger
2011-03-10 22:11 ` Scott Wood
2011-03-10 21:41 ` Carl-Daniel Hailfinger
2011-03-10 22:05 ` Jordan Justen
2011-03-10 18:59 ` Jordan Justen
2011-03-10 19:12 ` Gleb Natapov
2011-03-10 19:50 ` Jordan Justen
2011-03-10 20:08 ` Антон Кочков
2011-03-10 20:21 ` Gleb Natapov
2011-03-11 21:41 ` Jordan Justen
2011-03-14 14:29 ` Gleb Natapov
2011-03-10 21:37 ` [Qemu-devel] " Carl-Daniel Hailfinger
2011-03-10 21:55 ` Jordan Justen
2011-03-10 22:10 ` Carl-Daniel Hailfinger
2011-03-10 22:29 ` Jordan Justen
2011-03-10 23:53 ` Carl-Daniel Hailfinger
2011-03-11 0:19 ` [Qemu-devel] " Jan Kiszka
2011-03-11 0:27 ` Carl-Daniel Hailfinger
2011-03-11 19:09 ` Jordan Justen
2011-03-11 23:10 ` Michal Suchanek
2011-03-12 9:24 ` Jan Kiszka
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=4D792538.4030407@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=hramrach@centrum.cz \
--cc=jan.kiszka@siemens.com \
--cc=jljusten@gmail.com \
--cc=kevin@koconnor.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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).