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
Public bug reported:
I'm developping a multiboot kernel for multiboot v1
My multiboot header contains the V1 magic (0x1BADB002) and the flags 0x00010243
(with enabled memory detection, and boot loader name)
When booted in multiboot,
Qemu gives me two pointers:
unsigned long mmap_length;
unsign
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
