From: Shea Levy <shea@shealevy.com>
To: Matt Fleming <matt.fleming@intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: EFI Boot Stub Early Console
Date: Sun, 18 Mar 2012 08:10:03 -0400 [thread overview]
Message-ID: <4F65D09B.4050807@shealevy.com> (raw)
In-Reply-To: <1332069701.4041.42.camel@mfleming-mobl1.ger.corp.intel.com>
Hi Matt,
On 3/18/12 7:21 AM, Matt Fleming wrote:
> I don't think you'll need to use the graphics protocols, you should
> just be able to put something together using the 'output_string'
> function from the EFI simple text output protocol, e.g. something like
> this, https://lkml.org/lkml/2012/3/16/193
From the UEFI 2.3.1 spec:
> Prior to a call to ExitBootServices(), all of the fields of the EFI
> System Table are valid. After an operating system has taken control of
> the platform with a call to ExitBootServices(), only the Hdr,
> FirmwareVendor, FirmwareRevision, RuntimeServices,
> NumberOfTableEntries, and ConfigurationTable fields are valid.
Doesn't this mean that ConOut can't be used for the earlyprintk, since
any bootloader (including the bootstub) will call ExitBootServices()
before any printk'ing actually happens?? Or am I misunderstanding the
spec somehow? I suppose I could just try it and see what happens...
Cheers,
Shea
next prev parent reply other threads:[~2012-03-18 12:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 18:56 EFI Boot Stub Early Console Shea Levy
2012-03-12 19:00 ` Shea Levy
2012-03-12 22:11 ` H. Peter Anvin
2012-03-12 22:18 ` Shea Levy
2012-03-12 22:23 ` H. Peter Anvin
2012-03-12 22:28 ` Shea Levy
2012-03-17 13:12 ` Shea Levy
2012-03-18 11:21 ` Matt Fleming
2012-03-18 12:10 ` Shea Levy [this message]
2012-03-19 8:47 ` Matt Fleming
2012-03-19 15:56 ` Alan Cox
2012-03-19 16:02 ` Shea Levy
2012-03-19 16:03 ` Matt Fleming
2012-03-20 15:45 ` Maarten Lankhorst
2012-03-20 16:43 ` H. Peter Anvin
[not found] ` <CAOhV88Om7hKHeaGNp-PtFkn=y0T9EBQCbPSBE58vOYQ2+Genew@mail.gmail.com>
2012-03-18 4:29 ` Shea Levy
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=4F65D09B.4050807@shealevy.com \
--to=shea@shealevy.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
/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