ROMSTRAP

[YhLu]

I solved the problem about the ROMSTRAP by romstrap.lds and romstrap.inc.
Also I change 0x10 in id.lds and id.inc to let it don't use 0xffffffe0...

Current I still can not get output from serial port. And I can use postcard
with your chipset.

Regards

YH

-----Original Message-----
From: Tom Warren [mailto:twarren at nvidia.com] 
Sent: Friday, August 20, 2004 9:42 AM
To: YhLu; ebiederman at lnxi.com
Cc: linuxbios at clustermatic.org
Subject: RE: ROMSTRAP

YH,

If you have specific Nvidia chipset questions, you can ask me directly,
or I can point you to our developer liaison.

All of our chipsets use SIP tables to allow autoprogramming of (AMD) CPU
link defaults, MAC addresses, etc. The pointers to these 2 tables (safe
and user) are at 0xFFFFFFE0 and 0xFFFFFFE4 (dwords). Some of the table
format might be proprietary, depending on the chipset.

What was Eric's original question? I didn't see it come across the
reflector.

- Tom Warren
NVIDIA

-----Original Message-----
From: linuxbios-admin at clustermatic.org
[mailto:linuxbios-admin at clustermatic.org] On Behalf Of YhLu
Sent: Thursday, August 19, 2004 5:07 PM
To: ebiederman at lnxi.com
Cc: linuxbios at clustermatic.org
Subject: ROMSTRAP


Eric,

I'm debug the one Opteron MB with NV CK 804.

That chipset (SB) can use ROM Strap to set some register before control
is handed to CPU.

But the space it need about 0xffffffe00 to 0xfffffef. 

I guess that add romstarp.lds and romstrap.inc could solve the problem.
And it is only needed by fallback.

Please advise.

Regards

YH

_______________________________________________
Linuxbios mailing list
Linuxbios at clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios