** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1512134
Title:
Multiboot v1 memory map offset wrong
Status in QEMU:
Invalid
Bug description:
I'
Tested today with GRUB 2.0. Indeed, mmap_entry points to the start of
the structure, without a fancy offset. I guess we can close this ticket
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1512134
Tit
Hi,
Have you tested your code with GRUB (Legacy) itself? Looking at code
from one of my own hobby kernels, and from a hobby kernel that has
largely not been written by me, both are interpreting the fields as qemu
is (i.e. mmap_addr points to a multiboot_mmap_entry, and not to
multiboot_mmap_entry
I forgot to tell how i detected the issue:
I print all the fields, and in "type", i had the size of the next entry (and
in size, i have always zero, which corresponds to the high part of addr)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed
