On Mar 6, 2014, at 11:55 PM, Onipchuk Vladimir <v-onipc...@yandex.ru> wrote:
>
>
> My DEBUG prints uses <Library/DebugLib.h>.
In the edk2 there is not a 1 to 1 mapping between a Library Class and a Library
Instance.
The driver includes a generic include, <Library/DebugLib.h>, that is the public
interface of the library class. Then the INF file list the library class name,
DebugLib.
The goal is to make the driver not need to worry about how the library is
implement. The DSC file picks the library instance.
So for example a platform could chose a DebugLib instance that is a no-op, or
send it to EFI StdErr, EFI STdOut, ReportStatusCode, or some proprietary
scheme.
In the EDK the library include files sometimes had implementation detail of the
library exposed, and there was a 1 to 1 mapping.
> Even if all DEBUG prints turned off, "dh" command (UEFI shell) must print all
> device handles with registered protocols.
> But even driver binding and component name protocols (installed in entrypoint
> of my driver) not displayed.
> After "loadpcirom" this protocols displayed in "dh" output.
Yea that would only be possible if your entry point hit an error and did not
return EFI_SUCCES.
Thanks,
Andrew Fish
>
> Thanks,
> Vladimir.
>
> 06.03.2014, 18:04, "Andrew Fish" <af...@apple.com>:
>> On Mar 6, 2014, at 5:57 AM, Onipchuk Vladimir <v-onipc...@yandex.ru> wrote:
>>
>>> My DEBUG print samples:
>>>
>>> DEBUG ((EFI_D_INFO, "SUPPORTED!\n"));
>>
>> EFI_D_INFO could be turned off on this platform.
>>
>>> or
>>>
>>> if (EFI_ERROR (Status)) {
>>> DEBUG((EFI_D_ERROR,"Install BLOCK_IO protocol error - %x\n",Status));
>>> goto ON_ERROR;
>>> }
>>
>> Where is your driver sending DEBUG() prints?
>>
>> You can add this to the edk2 build command --report-file=build.og
>>
>> The build.log will tell you what library instances are getting used by your
>> driver.
>>
>> Thanks,
>>
>> Andrew Fish
>>
>>> Using Print() function in driver causes boot process freezing.
>>>
>>> 06.03.2014, 17:38, "Andrew Fish" <af...@apple.com>:
>>>
>>>> On Mar 6, 2014, at 3:27 AM, Onipchuk Vladimir <v-onipc...@yandex.ru>
>>>> wrote:
>>>>> Neeraj,
>>>>>
>>>>> oh no, I mean checking on the non-problematic platform (DG41TX in my
>>>>> case).
>>>>> On the problematic platform, I can't even print debug message at the
>>>>> start of my code. So I think, my driver not executing at the platform
>>>>> initialization stage.
>>>> How are you routing your DEBUG prints, or are you using Print()?
>>>>
>>>> If you are using DEBUG() you need to look out for how you implement it.
>>>>
>>>> These require the console to be connected, which can happen after your
>>>> driver is loaded, or maybe StdErr is not set.
>>>>
>>>> https://svn.code.sf.net/p/edk2/code/trunk/edk2/MdePkg/Library/UefiDebugLibConOut/
>>>>
>>>> https://svn.code.sf.net/p/edk2/code/trunk/edk2/MdePkg/Library/UefiDebugLibStdErr/
>>>>
>>>> This is not UEFI spec, or even PI spec it is the old Intel Framework, so
>>>> it might not exist everywhere.
>>>>
>>>> https://svn.code.sf.net/p/edk2/code/trunk/edk2/IntelFrameworkModulePkg/Library/PeiDxeDebugLibReportStatusCode/
>>>>
>>>> Thanks,
>>>>
>>>> Andrew Fish
>>>
>>> ------------------------------------------------------------------------------
>>> Subversion Kills Productivity. Get off Subversion & Make the Move to
>>> Perforce.
>>> With Perforce, you get hassle-free workflows. Merge that actually works.
>>> Faster operations. Version large binaries. Built-in WAN optimization and
>>> the
>>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> edk2-devel mailing list
>>> edk2-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>>
>> ,
>> ------------------------------------------------------------------------------
>> Subversion Kills Productivity. Get off Subversion & Make the Move to
>> Perforce.
>> With Perforce, you get hassle-free workflows. Merge that actually works.
>> Faster operations. Version large binaries. Built-in WAN optimization and the
>> freedom to use Git, Perforce or both. Make the move to Perforce.
>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>> ,
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries. Built-in WAN optimization and the
> freedom to use Git, Perforce or both. Make the move to Perforce.
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
