From: "Laszlo Ersek" <lersek@redhat.com>
To: jim slaughter <jim.slaughter@sage-micro.com>, devel@edk2.groups.io
Subject: Re: [edk2-devel] Help with Logo Display Problems
Date: Mon, 11 May 2020 23:26:59 +0200 [thread overview]
Message-ID: <bd28d315-ae32-5fe8-2d49-785270a0bcac@redhat.com> (raw)
In-Reply-To: <CAP1zt87BSQ_f3fCjh=kXhW-O4JLHHdNARDWDtp0AvrzZeog9Hg@mail.gmail.com>
On 05/11/20 20:04, jim slaughter wrote:
> Hello,
>
> Yes BootLogoEnableLogo() appears in several files and is not commented out.
>
> Files:
> PlatformBm.c
> BdsPlatform.c
> BootLogoLib.c
> BootLogoLib.h
> PlatformBm.c
That doesn't answer my question.
Does the PlatformBootManagerLib instance that is *specifically* linked
into BdsDxe in *your* firmware platform call BootLogoEnableLogo()?
Build your firmware with "--report-file=report.txt", and look up the
following part:
Module Name: BdsDxe
[...]
Module INF Path: MdeModulePkg/Universal/BdsDxe/BdsDxe.inf
[...]
Library
[...]
<IMPORTANT-LINE-HERE>
{PlatformBootManagerLib: Time = ...ms}
The pathname just before the "PlatformBootManagerLib: Time" line gives
you the INF file path that is relevant. Check the C files listed in that
INF file, for a BootLogoEnableLogo() call. The call should be made in
PlatformBootManagerAfterConsole().
Thanks
Laszlo
>
> Jim Slaughter
> ;
>
> On Mon, May 11, 2020 at 12:12 PM jim slaughter via groups.io <jim.slaughter=
> sage-micro.com@groups.io> wrote:
>
>> Hello,
>>
>> I do not know. Will look into this.
>>
>> Is this call, BootLogoEnableLogo(), normally in the code?
>> I have not added any code in this area.
>>
>> Jim S.
>> ;
>>
>> On Mon, May 11, 2020 at 11:41 AM Laszlo Ersek <lersek@redhat.com> wrote:
>>
>>> On 05/10/20 05:00, jim slaughter wrote:
>>>> Hello,
>>>>
>>>> I have followed previous directions provided and the build works ok. I
>>>> built an IA32 generic binary.
>>>> I cannot tell if the logo code is working since I cannot see the logo
>>> on my
>>>> display.
>>>>
>>>> I do see a file in
>>>> the ~/src/edk2-stable202002/Build/MdeModule/DEBUG_GCC5/IA32/$ directory,
>>>> called LogoDxe.efi and another called LogoDxe. This leads me to
>>>> believe that the Logo entry point is in the image.
>>>>
>>>> After the build I did find an empty map file? How do I get a map of the
>>>> build?
>>>>
>>>> How do I debug this problem? I have no debugger. Can I freely use
>>>> DEBUG((...........)); .
>>>>
>>>> Any help please. I am stuck. Thank you.
>>>>
>>>
>>> Does your PlatformBootManagerLib instance call BootLogoEnableLogo() in
>>> PlatformBootManagerAfterConsole()?
>>>
>>> Thanks,
>>> Laszlo
>>>
>>>
>>
>> --
>> Jim Slaughter
>>
>>
>>
>
next prev parent reply other threads:[~2020-05-11 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 3:00 Help with Logo Display Problems jim slaughter
2020-05-11 16:41 ` [edk2-devel] " Laszlo Ersek
2020-05-11 17:12 ` jim slaughter
[not found] ` <160E089A62B6865C.18245@groups.io>
2020-05-11 18:04 ` jim slaughter
2020-05-11 21:26 ` Laszlo Ersek [this message]
2020-05-11 18:27 ` Andrew Fish
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=bd28d315-ae32-5fe8-2d49-785270a0bcac@redhat.com \
--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