On Mon, Jan 26, 2015 at 02:07:41PM -0600, Timothy Pearson wrote:
On 01/26/2015 01:51 PM, Kevin O'Connor wrote:
It will likely be hard to figure out why your
vendor vgabios is
hanging. It's possible something in seabios is causing it to get
confused, but it's also possible something during the coreboot
initialization is confusing it.
I suggest increasing the SeaBIOS debugging level to 8 and see if it
reveals any further information.
Debug level 8:
SeaBIOS (version rel-1.7.5-150-g301dd09-20150126_140432-apollo)
Scan for VGA option rom
Attempting to init PCI bdf 01:04.0 (vd 18ca:0020)
Copying data 32768@0xfff36278 to 32768@0x000c0000
Checking rom 0x000c0000 (sig aa55 size 64)
Running option rom at c000:0003
So, no additional information. You could try increasing the debug
level to 99 just to see if irqs are still on (and if so, to see where
the pc is when irqs are hitting). However, unless you have access to
the vendor vgabios code it's very difficult to guess what's confusing
BTW, did you make sure all of the following are disabled in coreboot:
CONFIG_VGA_ROM_RUN, CONFIG_PCI_ROM_RUN, CONFIG_ON_DEVICE_ROM_RUN
If coreboot supports native vga init for your board, you could try
using seavgabios and skip the vendor vgabios.
Another approach would be to see if you can get get the vga bios to
run in some emulator (such as xorg's x86emu, coreboot's emulator,
qemu, etc) and then try to figure out what's different.
Please keep the mailing list on the CC.