On Fr, 2015-10-02 at 09:40 -0400, Kevin O'Connor wrote:
> On Fri, Oct 02, 2015 at 10:09:17AM +0200, Gerd Hoffmann wrote:
> > > - read four bytes from under the fw_cfg selector QEMU_CFG_KERNEL_SIZE
> > > (0x0008),
> > > - if it is zero,return -1 --> no kernel boot requested,
> > > - if it is
On Fr, 2015-10-02 at 09:38 -0400, Kevin O'Connor wrote:
> On Fri, Oct 02, 2015 at 10:16:26AM +0200, Gerd Hoffmann wrote:
> > Hi,
> >
> > > That's fine with me. Marc - I think qemu_vmlinux_setup() in SeaBIOS
> > > with the following would work:
> > >
> > > void qemu_vmlinux_setup(void)
> > > {
On Fri, Oct 02, 2015 at 10:16:26AM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > That's fine with me. Marc - I think qemu_vmlinux_setup() in SeaBIOS
> > with the following would work:
> >
> > void qemu_vmlinux_setup(void)
> > {
> > u32 kernel_size;
> > qemu_cfg_read_entry(_size,
On 10/02/15 15:25, Laszlo Ersek wrote:
> In Dec 2014 - Jan 2015, Matt, Paolo, Jordan & myself had a long
> discussion about the different ways to boot an EFI kernel (subject "the
> different ways to boot an EFI kernel"). Ultimately Matt wrote an article:
>
>
Hi,
> > Any -kernel boot on x86 will use either linuxboot.bin or multiboot.bin.
>
> (Except when your firmware is OVMF -- OVMF has its own LoadLinuxLib. So,
> if you decide to extend linuxboot.bin / multiboot.bin with the DMA
> capability, that can't regress OVMF by definition, and you
On 10/02/15 14:07, Gerd Hoffmann wrote:
> Hi,
>
>>> Any -kernel boot on x86 will use either linuxboot.bin or multiboot.bin.
>>
>> (Except when your firmware is OVMF -- OVMF has its own LoadLinuxLib. So,
>> if you decide to extend linuxboot.bin / multiboot.bin with the DMA
>> capability, that
On Fri, Oct 02, 2015 at 10:09:17AM +0200, Gerd Hoffmann wrote:
> > - read four bytes from under the fw_cfg selector QEMU_CFG_KERNEL_SIZE
> > (0x0008),
> > - if it is zero,return -1 --> no kernel boot requested,
> > - if it is nonzero, return 0 --> which means "top priority".
> >
> > In
On 10/02/15 11:01, Gerd Hoffmann wrote:
> Hi,
>
>> A solution that I can see is adding DMA boot capabilities to the
>> linuxboot.S optionrom. I was trying to avoid this, but it looks like
>> not doing so creates lots of problems. It may be better than adding a
>> "nice" shortcut somewhere in
> - read four bytes from under the fw_cfg selector QEMU_CFG_KERNEL_SIZE
> (0x0008),
> - if it is zero,return -1 --> no kernel boot requested,
> - if it is nonzero, return 0 --> which means "top priority".
>
> In other words, I agree with:
>
> > -option_rom[nb_option_roms].bootindex =
Hi,
> That's fine with me. Marc - I think qemu_vmlinux_setup() in SeaBIOS
> with the following would work:
>
> void qemu_vmlinux_setup(void)
> {
> u32 kernel_size;
> qemu_cfg_read_entry(_size, QEMU_CFG_KERNEL_SIZE,
> sizeof(kernel_size));
> if (kernel_size)
>
Hi,
> A solution that I can see is adding DMA boot capabilities to the
> linuxboot.S optionrom. I was trying to avoid this, but it looks like
> not doing so creates lots of problems. It may be better than adding a
> "nice" shortcut somewhere in QEMU or SeaBIOS.
>
> Who uses this optionrom (and
On Fri, 02 Oct 2015 10:16:26 +0200
Gerd Hoffmann wrote:
> Hi,
>
> > That's fine with me. Marc - I think qemu_vmlinux_setup() in SeaBIOS
> > with the following would work:
> >
> > void qemu_vmlinux_setup(void)
> > {
> > u32 kernel_size;
> >
On 10/02/15 15:40, Kevin O'Connor wrote:
> On Fri, Oct 02, 2015 at 10:09:17AM +0200, Gerd Hoffmann wrote:
>>> - read four bytes from under the fw_cfg selector QEMU_CFG_KERNEL_SIZE
>>> (0x0008),
>>> - if it is zero,return -1 --> no kernel boot requested,
>>> - if it is nonzero, return 0 -->
On Fri, Oct 02, 2015 at 09:40:41AM -0400, Kevin O'Connor wrote:
> On Fri, Oct 02, 2015 at 10:09:17AM +0200, Gerd Hoffmann wrote:
> > > - read four bytes from under the fw_cfg selector QEMU_CFG_KERNEL_SIZE
> > > (0x0008),
> > > - if it is zero,return -1 --> no kernel boot requested,
> > > -
On 2015-10-02 06:25:50, Laszlo Ersek wrote:
> On 10/02/15 14:07, Gerd Hoffmann wrote:
> > Hi,
> >
> >>> Any -kernel boot on x86 will use either linuxboot.bin or multiboot.bin.
> >>
> >> (Except when your firmware is OVMF -- OVMF has its own LoadLinuxLib. So,
> >> if you decide to extend
Add an entry to the bootorder file with name "vmlinux".
Give this entry more priority than the romfile.
Signed-off-by: Marc Marí
---
hw/i386/pc.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/hw/i386/pc.c b/hw/i386/pc.c
index 81d93b4..c4c51f7 100644
On 10/01/15 14:16, Marc Marí wrote:
> Add an entry to the bootorder file with name "vmlinux".
> Give this entry more priority than the romfile.
>
> Signed-off-by: Marc Marí
> ---
> hw/i386/pc.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git
On Thu, Oct 01, 2015 at 05:25:11PM +0200, Laszlo Ersek wrote:
> On 10/01/15 14:16, Marc Marí wrote:
> > Add an entry to the bootorder file with name "vmlinux".
> > Give this entry more priority than the romfile.
> >
> > Signed-off-by: Marc Marí
> > ---
> > hw/i386/pc.c | 4
On 10/01/15 18:02, Kevin O'Connor wrote:
> On Thu, Oct 01, 2015 at 05:25:11PM +0200, Laszlo Ersek wrote:
>> On 10/01/15 14:16, Marc Marí wrote:
>>> Add an entry to the bootorder file with name "vmlinux".
>>> Give this entry more priority than the romfile.
>>>
>>> Signed-off-by: Marc Marí
On Thu, 1 Oct 2015 12:02:42 -0400
"Kevin O'Connor" wrote:
> On Thu, Oct 01, 2015 at 05:25:11PM +0200, Laszlo Ersek wrote:
> > On 10/01/15 14:16, Marc Marí wrote:
> > > Add an entry to the bootorder file with name "vmlinux".
> > > Give this entry more priority than the
20 matches
Mail list logo