On Mon, Dec 15, 2008 at 10:19 PM, Bao, Zheng Zheng.Bao@amd.com wrote:
Hi, Carl, Base on your lspci, the device id of the 690G internal Graphics is 0x791E, while code in src/southbridge/amd/rs690/rs690_gfx.c has the id 0x791F for 690T. I changed my code to 791E and it hangs exactly where your board does. We need to figure out a way to tell which chipset we used.
Zheng
You can just add another driver to the file with the same ops, like:
static struct pci_driver pcie_driver __pci_driver = { .ops = &pcie_ops, .vendor = PCI_VENDOR_ID_ATI, .device = PCI_DEVICE_ID_ATI_RS690MT_INT_GFX, };
static struct pci_driver pcie_driver __pci_driver = { .ops = &pcie_ops, .vendor = PCI_VENDOR_ID_ATI, .device = PCI_DEVICE_ID_ATI_RS690_INT_GFX, };
Would that fix the problem?
-Corey
-----Original Message----- From: Carl-Daniel Hailfinger [mailto:c-d.hailfinger.devel.2006@gmx.net] Sent: Monday, December 15, 2008 10:17 AM To: Coreboot Cc: Bao, Zheng Subject: Re: [coreboot] DBM690T boot log needed
Hi Zheng,
could you please try to get such a DBM690T log? Thanks!
If I can compare that log with my log, I might be able to find the bug on my 690G board.
Regards, Carl-Daniel
On 11.12.2008 17:12, Carl-Daniel Hailfinger wrote:
Hi,
a boot log for the DBM690T with CONSOLE_LOGLEVEL=9 would be really great. Can anyone please mail such a log to the list?
Thanks!
Regards, Carl-Daniel
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot