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: [PATCH V6 0/8] Add ARM EFI stub
Date: Mon, 13 Jan 2014 15:07:35 +0000	[thread overview]
Message-ID: <20140113150735.GF3256@console-pimps.org> (raw)
In-Reply-To: <1389371417-379-1-git-send-email-roy.franz@linaro.org>

On Fri, 10 Jan, at 08:30:09AM, Roy Franz wrote:
> This patch series adds EFI stub support for the ARM architecture.  The 
> stub for ARM is implemented in a similar manner to x86 in that it is a 
> shim layer between EFI and the normal zImage/bzImage boot process, and 
> that an image with the stub configured is bootable as both a zImage and 
> EFI application.  This patchset adds common code that is shared with
> the ARM64 EFI stub.
> 
> This patch depends on Leif Lindholm's ARM v7 runtime services patchset, which 
> in turn depends on Mark Salter's early_io_remap() patchset.  This EFI stub 
> patchset can be tested without those by simply modifying the Kconfig for 
> EFI_STUB to not depend on EFI.  The kernel will boot using the stub, 
> however no EFI support will be available in the kernel.
> 
> I have addressed all the feedback I have recieved to date, and I am hoping 
> that this patchset is acceptable for merging into 3.14.  It has been 
> functionally stable for some time, and provides useful functionality.  
> Further consolidation of the ARM/ARM64 stubs planned as part of the 
> ongoing development of the stubs and supporting tools for both 
> architectures (getting the FDT from a UEFI configuration table, using UEFI 
> memory map instead of FDT for memory description.) 

Is this going to Linus via one of the ARM maintainer trees?

-- 
Matt Fleming, Intel Open Source Technology Center

  parent reply	other threads:[~2014-01-13 15:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 16:30 [PATCH V6 0/8] Add ARM EFI stub Roy Franz
2014-01-10 16:30 ` [PATCH V6 1/8] efi-stub.txt updates for ARM Roy Franz
2014-01-10 16:30 ` [PATCH V6 2/8] Add shared printk wrapper for consistent prefixing Roy Franz
2014-01-10 16:30 ` [PATCH V6 3/8] Add helper function to get and convert EFI command line Roy Franz
2014-01-13 15:04   ` Matt Fleming
2014-01-14 19:41     ` Roy Franz
2014-01-10 16:30 ` [PATCH V6 4/8] Add shared FDT related functions for ARM/ARM64 Roy Franz
2014-01-10 16:30 ` [PATCH V6 5/8] Add strstr to compressed string.c for ARM Roy Franz
2014-01-10 16:30 ` [PATCH V6 6/8] Add EFI stub " Roy Franz
2014-01-14  9:05   ` Ard Biesheuvel
2014-01-15  1:47     ` Roy Franz
2014-01-15  2:16       ` Roy Franz
2014-01-15  9:46         ` Ard Biesheuvel
2014-01-15 11:47         ` Leif Lindholm
2014-01-14 19:29   ` Rob Herring
2014-01-14 19:35     ` Roy Franz
2014-01-10 16:30 ` [PATCH V6 7/8] Disable stack protection for decompressor/stub Roy Franz
2014-01-10 16:30 ` [PATCH V6 8/8] Add config EFI_STUB for ARM to Kconfig Roy Franz
2014-01-13 15:07 ` Matt Fleming [this message]
2014-01-14 19:39   ` [PATCH V6 0/8] Add ARM EFI stub Roy Franz

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=20140113150735.GF3256@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).