From: Alexander Graf <agraf@suse.de>
To: Adam Lackorzynski <adam@os.inf.tu-dresden.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] multiboot: Fix module loading and setting of mmap
Date: Wed, 18 Nov 2009 16:12:27 +0100 [thread overview]
Message-ID: <4B040EDB.9040503@suse.de> (raw)
In-Reply-To: <20091118145332.GE31670@os.inf.tu-dresden.de>
Adam Lackorzynski wrote:
> On Wed Nov 18, 2009 at 15:33:10 +0100, Alexander Graf wrote:
>
>> Adam Lackorzynski wrote:
>>
>>> I need to following to fix multiboot booting for me.
>>>
>>> Should linuxboot.bin and multiboot.bin end up in pc-bios instead of
>>> pc-bios/optionrom?
>>>
>>> load_image(initrd_filename,
>>> mb_kernel_data + mb_mod_start - mh_load_addr);
>>>
>>> @@ -720,7 +720,7 @@ static int load_multiboot(void *fw_cfg,
>>> fw_cfg_add_bytes(fw_cfg, FW_CFG_INITRD_DATA, mb_bootinfo_data,
>>> sizeof(bootinfo));
>>>
>>> - option_rom[nb_option_roms] = "multiboot.bin";
>>> + option_rom[nb_option_roms] = "optionrom/multiboot.bin";
>>>
>>>
>> This is wrong. The .bin file should be in pc-bios. It just doesn't get
>> copied over as part of the build process, but instead relies on the
>> committer to make sure the binary is updated on every source change.
>>
>
> Ok, didn't know. Thank you both for clarifying! New patch attached.
>
>
> Signed-off-by: Adam Lackorzynski <adam@os.inf.tu-dresden.de>
>
Acked-by: Alexander Graf <agraf@suse.de>
Alex
next prev parent reply other threads:[~2009-11-18 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 14:02 [Qemu-devel] [PATCH] multiboot: Fix module loading and setting of mmap Adam Lackorzynski
2009-11-18 14:33 ` Alexander Graf
2009-11-18 14:53 ` Adam Lackorzynski
2009-11-18 15:12 ` Alexander Graf [this message]
2009-11-18 14:35 ` Anthony Liguori
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=4B040EDB.9040503@suse.de \
--to=agraf@suse.de \
--cc=adam@os.inf.tu-dresden.de \
--cc=aliguori@us.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.