[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAErSpo7c5Ph+GufivPt2XFoTbRnAoLnNdZwcc69QMCFdavNJjA@mail.gmail.com>
Date: Wed, 5 Dec 2012 15:21:35 -0700
From: Bjorn Helgaas <bhelgaas@...gle.com>
To: Matthew Garrett <mjg59@...f.ucam.org>
Cc: linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
linux-efi@...r.kernel.org, dwmw2@...radead.org,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Seth Forshee <seth.forshee@...onical.com>
Subject: Re: Use PCI ROMs from EFI boot services
On Wed, Dec 5, 2012 at 1:22 PM, Matthew Garrett <mjg59@...f.ucam.org> wrote:
> On Wed, Dec 05, 2012 at 01:09:25PM -0700, Bjorn Helgaas wrote:
>
>> That's right; nobody stepped up to fix the section mismatch. I'm
>> happy to fold in your fix, especially if Matthew acks it.
>
> Yes, sorry, I've been way behind on pretty much everything for the past
> few months. Please do add my Ack.
>
>> David, Eric, what about the kexec question? It looks to me like this
>> wouldn't make things worse than they are today. If I understand
>> correctly, today we don't use ROM data from EFI on either an initial
>> boot or a kexec. After this patch, we could use EFI ROM data on the
>> initial boot, but not after a kexec. So it's worse in the sense that
>> the kexec case doesn't match the initial boot, but at least it's not
>> something that used to work and is now broken.
>
> I think I'd agree here - it's not ideal, but it's no more broken than
> the current situation.
OK, I applied Seth's fix, added his Tested-by, and put this series in
my -next branch. I plan to merge it during the v3.8 merge window next
week.
Thanks!
Bjorn
--
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