On 02/08/2017 07:59 PM, Tim Lewis wrote: > 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
Thanks all, I do have some experience with using DEBUG() so I will take that approach (and as Andrew said, that way the DEBUG() output can be conditionally filtered based on priority so once I verify through that and shell commands I can turn them off easily). David > > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of > Rebecca Cran > Sent: Wednesday, February 08, 2017 6:56 PM > To: Andrew Fish <af...@apple.com> > Cc: edk2-de...@ml01.01.org; David A. Van Arnem <dvanar...@cmlab.biz> > Subject: Re: [edk2] Print from DXE_DRIVER > > >> On Feb 8, 2017, at 5:43 PM, Andrew Fish <af...@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). > -- Regards, David Van Arnem Development Engineer IV Computer Measurement Laboratory, LLC _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
