Hello, I am currently having an issue with a vga bios. I am trying to find the source of the issue using YABEL's awsome full debug feature (0x31ff). The problem is I think YABEL may be broken. I can't seem to get past copying the rom. Can someone please test YABEL in full debug(0x31ff), so we can figure out if indeed YABEL is broken or if it is just me?
Note: this same vga bios works fine with Real_Mode.
Starting Graphics Initialization Check CBFS header at fffeffe0 magic is 4f524243 Found CBFS header at fffeffe0 Check fallback/coreboot_ram CBFS: follow chain: fff80000 + 38 + c80e + align -> fff8c880 Check pci8086,3577.rom In cbfs, rom address for PCI: 00:02.0 = fff8c8b8 PCI Expansion ROM, signature 0xaa55, INIT size 0x10000, data ptr 0x0040 PCI ROM Image, Vendor 8086, Device 3577, PCI ROM Image, Class Code 030000, Code Type 00 copying VGA ROM Image from fff8c8b8 to 0xc0000, 0x10000 bytes <------Locks up here----------->
Hello, I am currently having an issue with a vga bios. I am trying to find the source of the issue using YABEL's awsome full debug feature (0x31ff). The problem is I think YABEL may be broken. I can't seem to get past copying the rom. Can someone please test YABEL in full debug(0x31ff), so we can figure out if indeed YABEL is broken or if it is just me?
PCI Expansion ROM, signature 0xaa55, INIT size 0x10000, data ptr 0x0040 PCI ROM Image, Vendor 8086, Device 3577, PCI ROM Image, Class Code 030000, Code Type 00 copying VGA ROM Image from fff8c8b8 to 0xc0000, 0x10000 bytes <------Locks up here----------->
I used qemu, and YABEL initializes the VGA correctly, but there is no debug output with the flags set to 0x31ff.
It's not the greatest test, since the ROM doesn't need to be copied for qemu, so I never see that line.
Thanks, Myles
On 2/19/10 4:42 PM, Joseph Smith wrote:
Hello, I am currently having an issue with a vga bios. I am trying to find the source of the issue using YABEL's awsome full debug feature (0x31ff). The problem is I think YABEL may be broken. I can't seem to get past copying the rom. Can someone please test YABEL in full debug(0x31ff), so we can figure out if indeed YABEL is broken or if it is just me?
Note: this same vga bios works fine with Real_Mode.
Starting Graphics Initialization Check CBFS header at fffeffe0 magic is 4f524243 Found CBFS header at fffeffe0 Check fallback/coreboot_ram CBFS: follow chain: fff80000 + 38 + c80e + align -> fff8c880 Check pci8086,3577.rom In cbfs, rom address for PCI: 00:02.0 = fff8c8b8 PCI Expansion ROM, signature 0xaa55, INIT size 0x10000, data ptr 0x0040 PCI ROM Image, Vendor 8086, Device 3577, PCI ROM Image, Class Code 030000, Code Type 00 copying VGA ROM Image from fff8c8b8 to 0xc0000, 0x10000 bytes <------Locks up here----------->
You did also enable "CONFIG_DEBUG", did you?
On 2/19/10 4:42 PM, Joseph Smith wrote:
Hello, I am currently having an issue with a vga bios. I am trying to find the source of the issue using YABEL's awsome full debug feature (0x31ff).
You did also enable "CONFIG_DEBUG", did you?
I didn't realize it was necessary. I didn't expect to have to edit src/Kconfig to be able to use an option in the menu.
Thanks, Myles
On Fri, Feb 19, 2010 at 10:36 AM, Myles Watson mylesgw@gmail.com wrote:
On 2/19/10 4:42 PM, Joseph Smith wrote:
Hello, I am currently having an issue with a vga bios. I am trying to find the source of the issue using YABEL's awsome full debug feature (0x31ff).
You did also enable "CONFIG_DEBUG", did you?
I didn't realize it was necessary. I didn't expect to have to edit src/Kconfig to be able to use an option in the menu.
Now I get plenty of output. I tried it with SimNOW, so I get the "copying..." line and it works fine.
Maybe we should change CONFIG_DEBUG in yabel code to be CONFIG_YABEL_DEBUG and add some code like this:
#if defined(CONFIG_YABEL_DEBUG_FLAGS) && CONFIG_YABEL_DEBUG_FLAGS != 0 #define CONFIG_YABEL_DEBUG 1 #else #define CONFIG_YABEL_DEBUG 0 #endif
I think this meaning of CONFIG_DEBUG should be separate from the other instances in the tree.
Thanks, Myles
On Fri, 19 Feb 2010 11:05:39 -0700, Myles Watson mylesgw@gmail.com wrote:
On Fri, Feb 19, 2010 at 10:36 AM, Myles Watson mylesgw@gmail.com wrote:
On 2/19/10 4:42 PM, Joseph Smith wrote:
Hello, I am currently having an issue with a vga bios. I am trying to find
the
source of the issue using YABEL's awsome full debug feature
(0x31ff).
You did also enable "CONFIG_DEBUG", did you?
I didn't realize it was necessary. I didn't expect to have to edit src/Kconfig to be able to use an option in the menu.
Now I get plenty of output. I tried it with SimNOW, so I get the "copying..." line and it works fine.
Maybe we should change CONFIG_DEBUG in yabel code to be
CONFIG_YABEL_DEBUG
and add some code like this:
#if defined(CONFIG_YABEL_DEBUG_FLAGS) && CONFIG_YABEL_DEBUG_FLAGS != 0 #define CONFIG_YABEL_DEBUG 1 #else #define CONFIG_YABEL_DEBUG 0 #endif
Yes, I like that :-)
On 2/19/10 7:05 PM, Myles Watson wrote:
I think this meaning of CONFIG_DEBUG should be separate from the other instances in the tree.
There are only two, and I think we could / should drop them anyways. But renaming the YABEL ones is good.
I have another patch in the queue that drops the non-yabel biosemu ....
Maybe we should rename yabel back to bios emulator? or generally something more meaningful? yet another makes little sense if it's the only one ;-)
Also CONFIG_DEBUG would applies to the x86emu portion of the code, too. Not sure if it makes sense to have CONFIG_X86EMU_DEBUG _and_ CONFIG_YABEL_DEBUG and they're in the very same field of what things can go wrong.
On Fri, 19 Feb 2010 20:30:48 +0100, Stefan Reinauer stepan@coresystems.de wrote:
Maybe we should rename yabel back to bios emulator? or generally something more meaningful? yet another makes little sense if it's the only one ;-)
I think the polite thing to do would be to ask Pattrick Hüper first, if it is ok to rename it because he wrote it :-) But I am all for renaming it.
Hi,
On Fri, Feb 19, 2010 at 10:45 PM, Joseph Smith joe@settoplinux.org wrote:
On Fri, 19 Feb 2010 20:30:48 +0100, Stefan Reinauer stepan@coresystems.de wrote:
Maybe we should rename yabel back to bios emulator? or generally something more meaningful? yet another makes little sense if it's the only one ;-)
I think the polite thing to do would be to ask Pattrick Hüper first, if it is ok to rename it because he wrote it :-) But I am all for renaming it.
i am fine with renaming it... i couldn't think of a better name when i originally posted it for coreboot... and "biosemu" was already taken and quite different... thus the "yet another...". I'll just have to adapt my mailfilter so i still catch all yabel/biosemu/whatever related mails :-)
Cheers, Pattrick
-- Thanks, Joseph Smith Set-Top-Linux www.settoplinux.org
On Fri, 19 Feb 2010 10:36:25 -0700, "Myles Watson" mylesgw@gmail.com wrote:
On 2/19/10 4:42 PM, Joseph Smith wrote:
Hello, I am currently having an issue with a vga bios. I am trying to find
the
source of the issue using YABEL's awsome full debug feature (0x31ff).
You did also enable "CONFIG_DEBUG", did you?
I didn't realize it was necessary. I didn't expect to have to edit src/Kconfig to be able to use an option in the menu.
Thanks, Myles
Yes.... I think we need to add this to /util/x86emu/yabel/debug.h:
#if MAXIMUM_CONSOLE_LOGLEVEL_8 #if DEFAULT_CONSOLE_LOGLEVEL_8
#define CONFIG_DEBUG
#endif #endif
On Fri, 19 Feb 2010 18:16:33 +0100, Stefan Reinauer stepan@coresystems.de wrote:
On 2/19/10 4:42 PM, Joseph Smith wrote:
Hello, I am currently having an issue with a vga bios. I am trying to find the source of the issue using YABEL's awsome full debug feature (0x31ff).
The
problem is I think YABEL may be broken. I can't seem to get past copying the rom. Can someone please test YABEL in full debug(0x31ff), so we can figure out if indeed YABEL is broken or if it is just me?
Note: this same vga bios works fine with Real_Mode.
Starting Graphics Initialization Check CBFS header at fffeffe0 magic is 4f524243 Found CBFS header at fffeffe0 Check fallback/coreboot_ram CBFS: follow chain: fff80000 + 38 + c80e + align -> fff8c880 Check pci8086,3577.rom In cbfs, rom address for PCI: 00:02.0 = fff8c8b8 PCI Expansion ROM, signature 0xaa55, INIT size 0x10000, data ptr 0x0040 PCI ROM Image, Vendor 8086, Device 3577, PCI ROM Image, Class Code 030000, Code Type 00 copying VGA ROM Image from fff8c8b8 to 0xc0000, 0x10000 bytes <------Locks up here----------->
You did also enable "CONFIG_DEBUG", did you?
Hmm, I will have to check that. Is that in Kconfig yet? Or do I have to go and manually enable it?
-
Joseph Smith -
Myles Watson -
Pattrick Hueper -
Stefan Reinauer