ADLO committed (NO FUNCTION TABLES!)

Eric W. Biederman ebiederman at lnxi.com
Mon Nov 25 17:03:00 CET 2002


"Ronald G. Minnich" <rminnich at lanl.gov> writes:

> One thing we should keep in mind for the shadow ram thing: 
> Just about every chipset I have seen has shadow ram registers that can 
> correctly be set with the following info:
> 
> VendorID, DeviceID, Function, register, AndMask, OrMask.
> 
> This rapidly leads to a simple table something like this:
> 
> struct shadowram{ 
> 	int physaddress;
> 	u16 VendorID, DeviceID, Function;
> 	u8 register;
> 	u8 AndMask, OrMask}; 
> 
> struct shadowram s[] = {
> 	{0xf0000, 0xabcd, 0x1234, 0x15, 0x40, 0xf8, 0x1},
> 	{ etc.}
> 	{0,}
> };
> 
> I haven't stumbled across a chipset yet for which this would not work.

Except for the Athlons?  Which control this in the CPU?

But that is the basic idea.
For the most part we should just enable these area in LinuxBIOS.  If the BIOS
doesn't need to disable writes to this area of RAM, absolutely nothing needs
to happen.

Eric




More information about the coreboot mailing list