From: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
Cc: Matt Fleming
<matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
"H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
linux-efi <linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] Fix efifb initialisation when the only GOP device implements ConOut.
Date: Mon, 07 Jan 2013 18:36:35 +0000 [thread overview]
Message-ID: <1357583795.2844.18.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20130107175846.GA385-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
On Mon, 2013-01-07 at 17:58 +0000, Matthew Garrett wrote:
> Ignore this case? You can't run 32-bit kernels on 64-bit EFI, or
> vice-versa. You'll die on the first call to UEFI services.
The kernel has code to avoid calling UEFI services in that case. Even if
we don't want to support that (any more?), we should at least fail
gracefully rather than just jumping to the wrong entry point and having
RandomShit™ happening.
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6171 bytes --]
next prev parent reply other threads:[~2013-01-07 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1357431222.9270.73.camel@shinybook.infradead.org>
[not found] ` <1357431222.9270.73.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org>
2013-01-07 17:08 ` [PATCH] Fix efifb initialisation when the only GOP device implements ConOut Matt Fleming
[not found] ` <1357524250.9270.86.camel@shinybook.infradead.org>
[not found] ` <1357524250.9270.86.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org>
2013-01-07 17:15 ` Matt Fleming
[not found] ` <1357578923.8203.72.camel-ZqTwcBeJ+wsBof6jY8KHXm7IUlhRatedral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-01-07 17:51 ` David Woodhouse
[not found] ` <1357581080.2844.17.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org>
2013-01-07 17:58 ` Matthew Garrett
[not found] ` <20130107175846.GA385-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-01-07 18:36 ` David Woodhouse [this message]
[not found] ` <1357583795.2844.18.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org>
2013-01-07 18:43 ` Matthew Garrett
[not found] ` <20130107184320.GA1400-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-01-07 19:12 ` David Woodhouse
[not found] ` <1357585971.2844.22.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org>
2013-01-07 19:16 ` Matthew Garrett
[not found] ` <20130107191648.GA2229-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-01-07 19:45 ` David Woodhouse
[not found] ` <1357524456.9270.90.camel@shinybook.infradead.org>
[not found] ` <1357524456.9270.90.camel-Fexsq3y4057IgHVZqg5X0TlWvGAXklZc@public.gmane.org>
2013-01-07 18:58 ` [PATCH] Specify ELF ABI for EFI handover protocol Matt Fleming
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=1357583795.2844.18.camel@shinybook.infradead.org \
--to=dwmw2-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org \
--cc=x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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