From: Andi Kleen <ak@suse.de>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
akpm@linux-foundation.org, Yinghai Lu <yhlu.kernel@gmail.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
Chandramouli Narayanan <mouli@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] x86_64 EFI support -v3: EFI document
Date: Wed, 8 Aug 2007 12:08:00 +0200 [thread overview]
Message-ID: <200708081208.01080.ak@suse.de> (raw)
In-Reply-To: <1186561082.4430.63.camel@caritas-dev.intel.com>
> The needed code changing is minimal. In fact, I can boot 32bit Linux
> kernel on my x86_64 EFI machine. With setup as follow:
>
> 1. Apply the efi-fb.patch
Just for the frame buffer, right?
> 2. make efi fb driver not depend on EFI
> 3. configure kernel as follow:
> a. CONFIG_EFI is turned off
> b. CONFIG_FB_EFI is turned on
Hmm, how does the 32bit kernel know where the e820 map is passed then?
With CONFIG_EFI turned off it will just ask the real mode BIOS I think
and I doubt elilo simulates that.
Or did you apply more patches?
-Andi
next prev parent reply other threads:[~2007-08-08 10:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 3:13 [PATCH 5/5] x86_64 EFI support -v3: EFI document Huang, Ying
2007-07-31 4:40 ` Eric W. Biederman
2007-07-31 6:58 ` Huang, Ying
2007-08-01 17:16 ` Eric W. Biederman
2007-08-07 9:29 ` Huang, Ying
2007-08-07 9:54 ` Andi Kleen
2007-08-08 8:18 ` Huang, Ying
2007-08-08 10:08 ` Andi Kleen [this message]
2007-08-08 13:46 ` Huang, Ying
2007-08-08 14:09 ` Andi Kleen
2007-08-08 15:11 ` huang ying
2007-08-08 16:23 ` Andi Kleen
2007-08-08 16:10 ` Eric W. Biederman
2007-08-08 16:22 ` Andi Kleen
2007-08-08 17:17 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2007-08-09 9:47 Etienne Lorrain
2007-08-09 10:51 ` Andi Kleen
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=200708081208.01080.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mouli@linux.intel.com \
--cc=randy.dunlap@oracle.com \
--cc=yhlu.kernel@gmail.com \
--cc=ying.huang@intel.com \
/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.