linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: matt@console-pimps.org (Matt Fleming)
To: linux-arm-kernel@lists.infradead.org
Subject: EFI_STUB fails to boot non-EFI on arm64
Date: Fri, 23 May 2014 14:24:57 +0100	[thread overview]
Message-ID: <20140523132457.GA23963@console-pimps.org> (raw)
In-Reply-To: <20140523131656.GR4179@bivouac.eciton.net>

On Fri, 23 May, at 02:16:56PM, Leif Lindholm wrote:
> On Fri, May 23, 2014 at 10:45:13AM +0100, Catalin Marinas wrote:
> > As the EFI_STUB for arm64 got into tip and soon into -next, I thought
> > about giving it a try (tip/arm64/efi). Using my boot-wrapper (non-EFI)
> > is still supposed to work but I get the trace below. It looks like
> > memmap.map is NULL but the code still assumes the kernel was started as
> > an EFI app.
> > 
> > Have you guys tested these patches properly?
> 
> Apparently not sufficuently...
> Sorry about that.
> 
> Fix appended:

This looks pretty straight forward. I've picked it up and shoved it on
my arm64-efi branch.

-- 
Matt Fleming, Intel Open Source Technology Center

  reply	other threads:[~2014-05-23 13:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23  9:45 EFI_STUB fails to boot non-EFI on arm64 Catalin Marinas
2014-05-23 13:16 ` Leif Lindholm
2014-05-23 13:24   ` Matt Fleming [this message]
2014-05-23 13:47   ` Catalin Marinas
2014-05-23 15:03     ` Leif Lindholm
2014-05-23 15:17       ` Ard Biesheuvel
2014-05-23 15:45         ` Leif Lindholm
2014-05-23 18:03           ` Roy Franz
2014-05-23 19:43           ` Ard Biesheuvel
2014-05-28 15:59       ` Will Deacon
2014-05-28 18:05         ` Leif Lindholm
2014-05-28 18:40           ` Will Deacon
2014-05-28 20:42             ` Leif Lindholm
2014-07-08  9:21       ` Catalin Marinas
2014-07-08 11:09         ` Leif Lindholm

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=20140523132457.GA23963@console-pimps.org \
    --to=matt@console-pimps.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).