LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas Meyer <thomas@m3y3r.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Latest kernel doesn't boot
Date: Wed, 06 Feb 2008 22:27:16 +0100	[thread overview]
Message-ID: <47AA2634.7020907@m3y3r.de> (raw)
In-Reply-To: <47AA2082.4000402@zytor.com>

H. Peter Anvin schrieb:
> Thomas Meyer wrote:
>>
>> I can not revert the commit e429795c68d3001ecae74f6465420c9f043b0ece. 
>> it gave me errors.
>> but i'm also not sure what could be wrong with this commit!
>>
>> my first idea was that the commit 
>> "[2215e69d2cf5024647f9a034807990590d25dd4e] x86 boot: use E820 memory 
>> map on EFI 32 platform" is the offender, because the macbook pro 
>> doesn't provide a e820 memory map at all. but bisect showed that i'm 
>> wrong here?!
>>
>
> ELILO is expected to convert the memory map from EFI to e820 format.
I'm using elilo-3.6-ia32.efi provided at the elilo homepage.  i wasn't 
able to create a working efi toolchain :-(
Does elilo-3.6 already do the converting of the memory map, or not?
> EFI32 is likely to be poorly supported, since Apple is likely to be 
> the only platform to *ever* ship EFI32 in mass production, and it has 
> a BIOS emulation layer available.
What do you want so say? Does linux support EFI or not?
>
>     -hpa
>

mfg
thomas

  reply	other threads:[~2008-02-06 21:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 22:15 thomas
2008-02-05 22:33 ` H. Peter Anvin
2008-02-05 23:57   ` thomas
2008-02-06 20:18   ` Thomas Meyer
2008-02-06 21:02     ` H. Peter Anvin
2008-02-06 21:27       ` Thomas Meyer [this message]
2008-02-06 21:45         ` H. Peter Anvin
2008-02-09 18:39           ` Thomas Meyer
2008-02-11 17:42             ` Jason Fleischli
2008-02-13  2:01             ` 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=47AA2634.7020907@m3y3r.de \
    --to=thomas@m3y3r.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Latest kernel doesn'\''t boot' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).