mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt Fleming <matt.fleming@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Henrik Rydberg <rydberg@euromail.se>,
	Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org,
	Jordan Justen <jordan.l.justen@intel.com>,
	Matthew Garrett <mjg@redhat.com>
Subject: Re: [GIT PULL] x86/efi changes for v3.5
Date: Sun, 03 Jun 2012 21:40:27 +0100	[thread overview]
Message-ID: <1338756027.4584.3.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <4FCAD63D.7070604@zytor.com>

On Sat, 2012-06-02 at 20:13 -0700, H. Peter Anvin wrote:
> On 06/02/2012 11:38 AM, Henrik Rydberg wrote:
> > Hi Ingo, Hans Peter, Matt, Jordan,
> > 
> >> This patchset makes changes to the bzImage EFI header, so that 
> >> it can be signed with a secure boot signature tool. It should 
> >> not affect anyone who is not using the EFI self-boot feature in 
> >> any way.
> > 
> > Commit 2e064b1 (Fix issue of overlapping .reloc section for EFI_STUB)
> > breaks EFI boot on my MacBookAir3,1. The efi firmware no longer
> > recognizes the bzImage and falls back to BIOS emulation boot.
> > 
> > Reverting 2e064b1 works for me, but I am happy to test other options
> > as well.
> > 
> 
> Matt, Jordan,
> 
> Could you look into this please?

Yeah, there's a bug report for this here,

	https://bugzilla.kernel.org/show_bug.cgi?id=43309

I suspect that older firmware doesn't handle a zero .reloc section
properly. So, unfortunately we will have to leave the .reloc section
with a dummy reloc, rather than having one with no entries.

I'll put a patch together.


      reply	other threads:[~2012-06-03 20:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23  7:54 Ingo Molnar
2012-06-02 18:38 ` Henrik Rydberg
2012-06-03  3:13   ` H. Peter Anvin
2012-06-03 20:40     ` Matt Fleming [this message]

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=1338756027.4584.3.camel@mfleming-mobl1.ger.corp.intel.com \
    --to=matt.fleming@intel.com \
    --cc=hpa@zytor.com \
    --cc=jordan.l.justen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mjg@redhat.com \
    --cc=rydberg@euromail.se \
    /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

all inboxes | Powered by JetHome®