lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 13 Jan 2014 15:07:35 +0000
From:	Matt Fleming <matt@...sole-pimps.org>
To:	Roy Franz <roy.franz@...aro.org>
Cc:	linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, matt.fleming@...el.com,
	linux@....linux.org.uk, leif.lindholm@...aro.org,
	grant.likely@...aro.org, dave.martin@....com, msalter@...hat.com,
	patches@...aro.org
Subject: Re: [PATCH V6 0/8] Add ARM EFI stub

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ