public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "David A. Van Arnem" <dvanarnem@cmlab.biz>
To: "edk2-devel@ml01.01.org" <edk2-devel@ml01.01.org>
Subject: Print from DXE_DRIVER
Date: Wed, 8 Feb 2017 15:10:43 -0700	[thread overview]
Message-ID: <4a3de604-5e60-7ed2-e520-29ab6b551c33@cmlab.biz> (raw)

Hello,

I am working on a DXE_DRIVER for a custom device.  I like to use Print()
statements to trace code execution during development.  Thus I have put
a print statement in each of my Supported(), Start(), and Stop()
functions for the driver binding protocol.  Currently I am building the
driver as part of the UefiCpuPkg, with no changes to the current
UefiCpuPkg.dsc except for adding my driver under [Components].  I have
also added the PrintLib and UefiLib to the [LibraryClasses] section in
my driver's INF file, and included the necessary headers.

When I load the driver from the shell (load <drivername>.efi), I get a
message indicating it loaded successfully, but no output from the
Print() messages.  The documentation for the shell says load should test
both the Supported() and Start() functions, so I would expect to see the
output, but I am not sure I am using the correct library instances to
accomplish this.  Is it possible to use Print() from a DXE_DRIVER, and
which library instance should I use in the UefiCpuPkg.dsc file?  If not,
would changing it to a UEFI_DRIVER help?  Any other recommendations?

If there is an example in edk2 that does this that you could point me
to, that would be sufficient as well.  Thanks!

-- 
Regards,
David Van Arnem
Development Engineer IV
Computer Measurement Laboratory, LLC



             reply	other threads:[~2017-02-08 22:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 22:10 David A. Van Arnem [this message]
2017-02-09  0:15 ` Print from DXE_DRIVER 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
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=4a3de604-5e60-7ed2-e520-29ab6b551c33@cmlab.biz \
    --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