> >> I think we should generally #define RAMBASE for x86 architectures to > >> (above) 1MB and remove it from Kconfig. > >> > >> It will allow us to simplify CAR and make the different CPUs' CAR code > >> look more alike > > > > I think that's a great idea. Extra complexity has never helped us. > > > > For RAMTOP would we have to play some tricks to figure out how big > > coreboot_ram was if RAMTOP isn't a config variable? The fam10 boards > use a > > lot of RAM right now. > > Excellent idea! > > Myles, is there ever a case where RAMTOP would be so low that the > fam10 boards would run out of RAM? What is the need for RAMTOP? For suspend/resume I think we like to keep RAMTOP-RAMBASE = 1M. Last time I checked, some of the fam10 boards are using RAMBASE=2M and RAMTOP=16M.
Once you start allowing 48 cores and you want page tables on all of their stacks, it gets big quickly. Thanks, Myles -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
