Another way is to get it from the ConOut device path. There's a UEFI
variable called "ConOut" (refer to UEFI spec) that holds a device path.
Doing a LocateDevicePath() with gEfiGraphicsOutputProtocolGuid and this
device path gives you the handle to GOP that ConOut is using. Just
OpenProtocol() with this handle to get the GOP instance.
On Wed, Oct 8, 2014 at 11:17 AM, Rafael Machado <
rafaelrodrigues.mach...@gmail.com> wrote:
> Hi J. E.
>
> Just one question.
> Are you sure that this GOP you are using is handled by the current active
> graphic device ?
>
> I'm asking this because some time ago I had one problem like this, and the
> situation was that my system had two gop handles, but the first one that
> was detected was not related to the active device.
>
> To check this I used the Edid protocol.
>
> Thanks and Regards
> Rafael R. Machado
>
>
> 2014-10-03 3:15 GMT-03:00 J. E. <nszero...@hotmail.com>:
>
>> BltLibVideoToBltBuffer seems to be unreliable on some PC's. Most work
>> fine, but a select few return black pixels, no errors. EFI_STATUS =
>> EFI_SUCCESS.
>>
>> If BltLibVideoToBltBuffer returns black pixels does that mean the
>> hardware/firmware doesn't support screen-to-buffer functionality?
>> I assume this is because someone didnt test the function or feel the need
>> to implement the function in the BIOS code or GOP driver, rather than a GOP
>> handle issue.
>>
>>
>> ------------------------------------------------------------------------------
>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>>
>>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
