[coreboot] YABEL debug broken again

Joseph Smith joe at settoplinux.org
Tue Mar 2 23:54:37 CET 2010




On Tue, 02 Mar 2010 17:23:00 -0500, Joseph Smith <joe at settoplinux.org>
wrote:
> Well it looks like YABEL debug is broken again.....
> 
> util/x86emu/yabel/vbe.c:600: error: 'vbe_mode_info_t' has no member
> named 'attributes'
> util/x86emu/yabel/vbe.c:604: error: 'vbe_mode_info_t' has no member
> named 'attributes'
> util/x86emu/yabel/vbe.c:607: error: 'vbe_mode_info_t' has no member
> named 'attributes'
> util/x86emu/yabel/vbe.c:607: error: 'vbe_mode_info_t' has no member
> named 'attributes'
> util/x86emu/yabel/vbe.c:612: error: 'vbe_mode_info_t' has no member
> named 'attributes'
> util/x86emu/yabel/vbe.c:615: error: 'vbe_mode_info_t' has no member
> named 'attributes'
> util/x86emu/yabel/vbe.c:618: error: 'vbe_mode_info_t' has no member
> named 'attributes'
> util/x86emu/yabel/vbe.c:621: error: 'vbe_mode_info_t' has no member
> named 'x_resolution'
> util/x86emu/yabel/vbe.c:621: error: 'vbe_mode_info_t' has no member
> named 'y_resolution'
> util/x86emu/yabel/vbe.c:624: error: 'vbe_mode_info_t' has no member
> named 'x_charsize'
> util/x86emu/yabel/vbe.c:624: error: 'vbe_mode_info_t' has no member
> named 'y_charsize'
> util/x86emu/yabel/vbe.c:626: error: 'vbe_mode_info_t' has no member
> named 'bits_per_pixel'
> util/x86emu/yabel/vbe.c:628: error: 'vbe_mode_info_t' has no member
> named 'memory_model'
> util/x86emu/yabel/vbe.c:630: error: 'vbe_mode_info_t' has no member
> named 'framebuffer_address'
> util/x86emu/yabel/vbe.c:647: error: 'vbe_mode_info_t' has no member
> named 'x_resolution'
> util/x86emu/yabel/vbe.c:647: error: 'vbe_mode_info_t' has no member
> named 'y_resolution'
> util/x86emu/yabel/vbe.c:647: error: 'vbe_mode_info_t' has no member
> named 'bits_per_pixel'
> util/x86emu/yabel/vbe.c:647: error: 'vbe_mode_info_t' has no member
> named 'framebuffer_address'
> make: *** [util/x86emu/yabel/vbe.o] Error 1
> 
> 
Appears to be something wrong with the union in structure vbe_mode_info_t
in vbe.c. It points to another structure vesa_mode_info_t, but I am not
sure why it is not working?????


-- 
Thanks,
Joseph Smith
Set-Top-Linux
www.settoplinux.org





More information about the coreboot mailing list