sravan/system76-coreboot
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Now that no boards set RAMBASE < 1M, get rid of some dead code. Trivial.

Browse Source 
It's probably time to reconsider moving all fam10 boards to RAMBASE = 1M.

Signed-off-by: Myles Watson <mylesgw@gmail.com>
Acked-by: Myles Watson <mylesgw@gmail.com>


git-svn-id: svn://svn.coreboot.org/coreboot/trunk@5977 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1
This commit is contained in:
Myles Watson
2010-10-20 19:23:22 +00:00
parent bda153be73
commit fa78d998d5
2 changed files with 0 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
src/arch/i386/coreboot_ram.ld
View File

@@ -106,13 +106,6 @@ SECTIONS
}
_eheap = .;
/* Some assertions to print human readable errors for certain linker
* error scenarios.
*/
/* Avoid running into 0xa0000-0xfffff */
_bogus = ASSERT(CONFIG_RAMBASE >= 0x100000 || _eheap < 0xa0000, "Please move RAMBASE to 1MB");
/* The ram segment. This includes all memory used by the memory
* resident copy of coreboot, except the tables that are produced on
* the fly, but including stack and heap.
@@ -125,13 +118,6 @@ SECTIONS
*/
_bogus = ASSERT( ( _eram_seg < (CONFIG_RAMTOP)) , "Please increase CONFIG_RAMTOP");
/* This rule is only good for the few broken targets that still live
* below 1MB per default. Those are the Geode and VIA targets that come
* with their own version of real mode switches that can't live above
* 1MB. Once these are fixed, this rule should go away.
*/
_bogus = ASSERT( !((CONFIG_CONSOLE_VGA || CONFIG_PCI_ROM_RUN || CONFIG_VGA_ROM_RUN || CONFIG_HAVE_SMI_HANDLER) && ((_ram_seg<0xa0000) && (_eram_seg>0xa0000))), "Please increase CONFIG_RAMTOP and if still fail, try to set CONFIG_RAMBASE to 1M");
/* Discard the sections we don't need/want */
/DISCARD/ : {