RE: Re: [Edk2 Dev] EDK2 w/ (EDK)BiosVideo Driver

Subject: RE: Re: [Edk2 Dev] EDK2 w/ (EDK)BiosVideo Driver

From: Lu ken <ken.lu@intel.com>

To: dev@edk2.tianocore.org

Date: 2009-01-19 10:08:14

Hi, Michael:
=09I think ModeNumber =3D 0 mean text mode.
=09Thanks.

-----Original Message-----
From: Joe Doe [mailto:nospam@t-media-welt.de]=20
Sent: Saturday, January 17, 2009 2:32 AM
To: dev@edk2.tianocore.org
Subject: RE: Re: [Edk2 Dev] EDK2 w/ (EDK)BiosVideo Driver

Hey Andrew!

Thank you for your response.

I checked it twice by logging EDK-Duet and EDK2-Duet w/ same BiosVideo.efi =
and LegacyBiosThunk.

For EDK2-Duet it is impossible to get any VBE/VESA to work:

Using new VGA...

PCI-Device VendorID=3D10DE, DeviceID=3D606

Called BiosVideoChildHandleInstall...

PCI_DEVICE_ENABLED=3D3

PCI CLASS_CODE[0]=3D0

PCI CLASS_CODE[1]=3D0

PCI CLASS_CODE[2]=3D3

Using new VGA...

PCI-Device VendorID=3D10DE, DeviceID=3D606

VESA-Signature:41534556

VESA version =3D768...

Processing Mode Number 57F0

Continue 1 VESA-Call

Processing Mode Number 65E0

Continue 1 VESA-Call

Processing Mode Number 858D

Continue 1 VESA-Call

Processing Mode Number E1E8

Continue 1 VESA-Call

Processing Mode Number EFC7

Continue 1 VESA-Call

Processing Mode Number F3F0

Continue 1 VESA-Call

Error on Mode number =3D0...

Error on check for VBE...

Allocating VGA frame buffer

HorizontalResolution=3D280

VerticalResolution=3D1E0

PixelFormat=3D3

PixelBitMask=3DAFAFAFAF

PixelsPerScanLine=3D280

ModeNumber=3D0

----------------------------

The same build in EDK works. So i think it has to do with the CSM (real-mod=
e) stuff in EDK2?

------------------------------------------------------
https://edk2.tianocore.org/ds/viewMessage.do?dsForumId=3D135&dsMessageId=3D=
34376

To unsubscribe from this discussion, please e-mail [unsubscribeURL]

------------------------------------------------------
https://edk2.tianocore.org/ds/viewMessage.do?dsForumId=3D135&dsMessageId=3D=
34404

To unsubscribe from this discussion, please e-mail [unsubscribeURL]