On Oct 8, 2014, at 3:43 PM, J. E. <nszero...@hotmail.com> wrote:
> I always use the last handle in the handle list, it works on 100% of the PC's
> Ive tested. Some PC's have 3 or 4 handles.
> However I'd prefer to do it the correct way so I will query the protocol as
> suggested.
>
I’ve put one bullet in the revolver and spun the chamber. So far on a 100% of
the revolvers I’ve tried the gun has never fired. I assume this means a gun
with only a single bullet is 100% safe if I spin the chamber first….
You should look for the GOP on the gST->ConsoleOutHandle. On system that
support the ConSpliter this will be the virtual console device that follows the
platform policy, on a system without the ConSpliter it will the active device.
You can also use the ConOut variable to get a list of the active console
devices.
> I currently use:
>
> nGOPHandleIndex = handleCount - 1;
> Status = gBS->HandleProtocol(
> handleBuffer[nGOPHandleIndex],
> &gEfiGraphicsOutputProtocolGuid,
> (VOID **)&(GraphicsOutput));
>
This depends on an implementation artifact that could change at any time. The
1st one is the ConSpliter, and the 2nd - Nth are going to be the real GOP based
on the ConOut variables. If you were in a multi headed system where a connect
all was done, like booting the shell, the last one may not be the active
console.
Thanks,
Andrew Fish
> The PC that returns black pixels has 2 total handles.
> If I choose the 1st handle, there is no graphics output at all. It stays on
> the console text screen.
> If I choose the 2nd handle, there is graphics output, but
> BltLibVideoToBltBuffer returns black pixels.
>
> So I am definitely using the correct handle for GOP graphics.
>
> I was thinking maybe the BlitLib was using the 1st handle instead of the 2nd
> handle, but I couldn't find a way to set the handle index in BlitLib. Even if
> it was using the 1st handle, wouldn't I see bits of ASCII characters in the
> returned blit from the console? I see no text, just black.
> BltLibVideoToBltBuffer also has no option to set the handle.
>
> So it seems the BIOS in question simply hasn't implemented proper
> Screen-to-Blit functionality.
> I suppose it's not a feature many people would use so it would be easy for
> some BIOS developers to forget to test/implement this function.
>
> Thanks.
>
> Date: Wed, 8 Oct 2014 12:27:18 -0500
> From: tcrog...@gmail.com
> To: edk2-devel@lists.sourceforge.net
> Subject: Re: [edk2] BltLibVideoToBltBuffer returns black pixels
>
> 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
> Analyzerhttp://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________ edk2-devel mailing list
> edk2-devel@lists.sourceforge.nethttps://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
