[coreboot] bug report on dbm690t

[Rudolf Marek]

> Is this problem new? And did it happen with your ExtINT bugfix applied?
>   

I think the ExtInt fix, is not fix of problem. I think it just disabled 
some "stuck" interrupt.

Rudolf

>
>   
>> Check fallback/payload
>> CBFS: follow chain: fff272c0 + 38 + 15a88 + align -> fff3cd80
>> Check fallback/coreboot_ram
>> CBFS: follow chain: fff3cd80 + 38 + 1178f + align -> fff4e580
>> Check pci1002,791f.rom
>> In cbfs, rom address for PCI: 01:05.0 = fff4e5b8
>> PCI Expansion ROM, signature 0xaa55, INIT size 0xda00, data ptr 0x01b0
>> PCI ROM Image, Vendor 1002, Device 791f,
>> PCI ROM Image,  Class Code 030000, Code Type 00
>> copying VGA ROM Image from fff4e5b8 to 0xc0000, 0xda00 bytes
>> Executing Initialization Vector...
>> int15 (AX=4e08) vector at ff859
>> Unknown INT15 function 4e08!
>> int15 (AX=4e08) vector at ff859
>> Unknown INT15 function 4e08!
>> int15 (AX=4e08) vector at ff859
>> Unknown INT15 function 4e08!
>> Unexpected Exception: 13 @ 10:0001ff2f - Halting
>> Code: 0 eflags: 00010002
>> eax: 00000040 ebx: ffff42a4 ecx: 000ca0d9 edx: 02062020
>> edi: 0000001f esi: 000397f0 ebp: 0000c000 esp: 0003bae4
>>   
>>     
>
> On my Asus M2A-VM (which is very similar to the AMD DBM690T, but it has
> RS690 instead of RS690M) the ROM execution works in r4681 (didn't test
> anything newer yet).
>
> Regards,
> Carl-Daniel
>
>