From: Avi Kivity <avi@redhat.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH master, stable-0.12] Don't load options roms intended to be loaded by the bios in qemu
Date: Tue, 22 Dec 2009 11:40:18 +0200 [thread overview]
Message-ID: <4B309402.3010207@redhat.com> (raw)
In-Reply-To: <20091222093554.GC31094@hall.aurel32.net>
On 12/22/2009 11:35 AM, Aurelien Jarno wrote:
> On Tue, Dec 22, 2009 at 11:25:13AM +0200, Avi Kivity wrote:
>
>> The first such option rom will load at address 0, which isn't very nice,
>> and the second will report a conflict and abort, which is horrible.
>>
>> Signed-off-by: Avi Kivity<avi@redhat.com>
>> ---
>> hw/loader.c | 3 +++
>> 1 files changed, 3 insertions(+), 0 deletions(-)
>>
>> diff --git a/hw/loader.c b/hw/loader.c
>> index 2ceb8eb..c6bf0f1 100644
>> --- a/hw/loader.c
>> +++ b/hw/loader.c
>> @@ -654,6 +654,9 @@ int rom_load_all(void)
>> Rom *rom;
>>
>> QTAILQ_FOREACH(rom,&roms, next) {
>> + if (!rom->addr) {
>> + continue;
>> + }
>>
> Some roms needs to be loaded at address 0, it's the case for example of
> the arm versatile bootloader. Adding this code will break the board
> emulation.
>
The idea of keying bios-loading or host-loading on address is broken
(another instance of mixing control and data). We need a separate
control for this. I'll leave this to the authors of the code as I can't
make heads or tails of it.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-12-22 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 9:25 [Qemu-devel] [PATCH master, stable-0.12] Don't load options roms intended to be loaded by the bios in qemu Avi Kivity
2009-12-22 9:35 ` Aurelien Jarno
2009-12-22 9:40 ` Avi Kivity [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=4B309402.3010207@redhat.com \
--to=avi@redhat.com \
--cc=aurelien@aurel32.net \
--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).