From: Johan Rydberg <jrydberg@night.trouble.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: multiboot2: variable data size
Date: Wed, 29 Nov 2006 01:22:49 +0100 [thread overview]
Message-ID: <87bqmrgkyu.fsf@night.trouble.net> (raw)
In-Reply-To: <456C2F8C.1040709@intel.com> (mao bibo's message of "Tue, 28 Nov 2006 20:46:04 +0800")
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
"bibo,mao" <bibo.mao@intel.com> writes:
> If kernel image is bzImage, x64 efi bootloader need switch to 32 bit
> protect mode(or real mode) from 64 bit long mode, and if kernel
> image is gzipped/plain format, efi bootloader can directly jump to
> 64-bit kernel entry address without mode switch.
My opinion is that bzImages should be avoided on EFI platforms, or the
decompress-code in Linux has to be rewritten.
It took me a good couple of hours of debugging to find out that Linux
simply ignores the memory layout and assumes that low memory is free
to use as it likes.
~j
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2006-11-29 0:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <iss.8f960c3c.4ebf.45648480.44026.78@relay0i.sun.com>
2006-11-22 20:55 ` Grub-devel Digest, Vol 33, Issue 19 Joe Bonasera
2006-11-25 2:09 ` multiboot2: variable data size Hollis Blanchard
2006-11-25 3:10 ` Yoshinori K. Okuji
2006-11-25 3:33 ` Hollis Blanchard
2006-11-25 3:46 ` Yoshinori K. Okuji
2006-11-25 4:08 ` Hollis Blanchard
2006-11-25 4:36 ` Yoshinori K. Okuji
2006-11-25 5:01 ` Hollis Blanchard
2006-11-28 9:29 ` Johan Rydberg
2006-11-28 11:35 ` Yoshinori K. Okuji
2006-11-28 12:46 ` bibo,mao
2006-11-28 23:29 ` Yoshinori K. Okuji
2006-11-29 1:55 ` bibo,mao
2006-11-29 2:37 ` Andrei E. Warkentin
2006-11-29 0:22 ` Johan Rydberg [this message]
2006-11-29 2:13 ` bibo,mao
2006-11-28 12:50 ` tgingold
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=87bqmrgkyu.fsf@night.trouble.net \
--to=jrydberg@night.trouble.net \
--cc=grub-devel@gnu.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.