From: Tim Lewis <tim.lewis@insyde.com>
To: Rebecca Cran <rebecca@bluestop.org>, Andrew Fish <afish@apple.com>
Cc: "edk2-devel@ml01.01.org" <edk2-devel@ml01.01.org>,
"David A. Van Arnem" <dvanarnem@cmlab.biz>
Subject: Re: Print from DXE_DRIVER
Date: Thu, 9 Feb 2017 02:59:05 +0000 [thread overview]
Message-ID: <7236196A5DF6C040855A6D96F556A53F42D2BE@msmail.insydesw.com.tw> (raw)
In-Reply-To: <4066A9E2-CBB9-49B0-BEDC-4455A6CD57A8@bluestop.org>
Also, on many systems, the output will be invisible, since boot screen output is a platform policy. In general, using DEBUG() is better, since it can either be redirected to StdErr() or through the serial port.
Tim
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Rebecca Cran
Sent: Wednesday, February 08, 2017 6:56 PM
To: Andrew Fish <afish@apple.com>
Cc: edk2-devel@ml01.01.org; David A. Van Arnem <dvanarnem@cmlab.biz>
Subject: Re: [edk2] Print from DXE_DRIVER
> On Feb 8, 2017, at 5:43 PM, Andrew Fish <afish@apple.com> wrote:
>
> If you want to write directly to the UEFI Console you can try this. Place it in the entry point of your driver in case you have some bug that is preventing your from registering the Driver Binding Protocol.
>
> gST->ConOut->OutputString (gST->ConOut, L"Hello World\n\r");
Note that on some systems, at some times gST->ConOut may be NULL, so it might be worth checking before calling it (unless you know otherwise on your dev system).
--
Rebecca
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-02-09 2:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 22:10 Print from DXE_DRIVER David A. Van Arnem
2017-02-09 0:15 ` Laszlo Ersek
2017-02-09 0:41 ` David A. Van Arnem
2017-02-09 0:49 ` Andrew Fish
2017-02-09 0:43 ` Andrew Fish
2017-02-09 0:49 ` David A. Van Arnem
2017-02-09 1:04 ` Andrew Fish
2017-02-09 2:16 ` Gao, Liming
2017-02-09 2:55 ` Rebecca Cran
2017-02-09 2:59 ` Tim Lewis [this message]
2017-02-09 20:38 ` David A. Van Arnem
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-list 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=7236196A5DF6C040855A6D96F556A53F42D2BE@msmail.insydesw.com.tw \
--to=devel@edk2.groups.io \
/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