device/oprom/yabel: Fix vbe-buffer index in vbe.c
There's a issue about {VbeSignature to "VBE2" to indicate VBE 2.0+ request}, these indexes are counted wrong. Change-Id: I8ec85df60076162518aa55a94fa7b66c0c2391ab Signed-off-by: Hal Tsai <hal_tsai@compal.corp-partner.google.com> Reviewed-on: https://review.coreboot.org/25736 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Nico Huber <nico.h@gmx.de>
This commit is contained in:
parent
39c4bb0211
commit
551e1fe06f
|
@ -75,9 +75,9 @@ vbe_prepare(void)
|
||||||
memset(vbe_info_buffer, 0, 512);
|
memset(vbe_info_buffer, 0, 512);
|
||||||
//set VbeSignature to "VBE2" to indicate VBE 2.0+ request
|
//set VbeSignature to "VBE2" to indicate VBE 2.0+ request
|
||||||
vbe_info_buffer[0] = 'V';
|
vbe_info_buffer[0] = 'V';
|
||||||
vbe_info_buffer[0] = 'B';
|
vbe_info_buffer[1] = 'B';
|
||||||
vbe_info_buffer[0] = 'E';
|
vbe_info_buffer[2] = 'E';
|
||||||
vbe_info_buffer[0] = '2';
|
vbe_info_buffer[3] = '2';
|
||||||
// ES:DI store pointer to buffer in virtual mem see vbe_info_buffer above...
|
// ES:DI store pointer to buffer in virtual mem see vbe_info_buffer above...
|
||||||
M.x86.R_EDI = 0x0;
|
M.x86.R_EDI = 0x0;
|
||||||
M.x86.R_ES = VBE_SEGMENT;
|
M.x86.R_ES = VBE_SEGMENT;
|
||||||
|
|
Loading…
Reference in New Issue