From: Etienne Lorrain <etienne_lorrain@yahoo.fr>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, ebiederm@xmission.com
Subject: RE : Re: [PATCH 5/5] x86_64 EFI support -v3: EFI document
Date: Thu, 9 Aug 2007 13:23:56 +0200 (CEST) [thread overview]
Message-ID: <741983.8529.qm@web26910.mail.ukl.yahoo.com> (raw)
In-Reply-To: <200708091251.21726.ak@suse.de>
--- Andi Kleen <ak@suse.de> wrote:
> > Note that Gujin has a simple problem by using that 32 bits entry point:
>
> There is really no 32bit entry point today usable for external users.
That is why I added the 16 bits entry point support (selected by default),
my target with Gujin was not only to load Linux but also another simpler
format - gzip'ed ELF 32/64 files with real-mode embedded at address 0 .
I also had to show that it was possible to write the Linux-real-mode
code in C with GCC so that someone else would do it and maintain it.
I may (in few version) remove Gujin code which fills Linux zero-page
structure if the 16 bit entry point works in all cases (mostly in DOS
which help me to create a DBG debug file to sort out Gujin/BIOS problems
remotely).
I may maintain another patch to produce this gzip'ed ELF32/64 for Linux
as an example of how to use that Gujin interface, but that is not really
related. That patch is in Gujin Sourceforge download.
Note that I call (instead of jump to) the 16 bits entry point so that
this "function" can return to the bootloader if it detects a problem.
Etienne.
_____________________________________________________________________________
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail
next prev parent reply other threads:[~2007-08-09 11:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 9:47 [PATCH 5/5] x86_64 EFI support -v3: EFI document Etienne Lorrain
2007-08-09 10:51 ` Andi Kleen
2007-08-09 11:23 ` Etienne Lorrain [this message]
2007-08-09 14:09 ` huang ying
2007-08-09 16:29 ` H. Peter Anvin
2007-08-09 17:01 ` Andi Kleen
2007-08-09 17:25 ` H. Peter Anvin
2007-08-10 13:03 ` Huang, Ying
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=741983.8529.qm@web26910.mail.ukl.yahoo.com \
--to=etienne_lorrain@yahoo.fr \
--cc=ak@suse.de \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox