[coreboot] [patch] RE: Fam10 breakage

Bao, Zheng Zheng.Bao at amd.com
Mon Mar 1 06:35:26 CET 2010


I have tried. But it makes no difference.
00000030 A CONFIG_MAX_CPUS
...............
00008000 A CONFIG_STACK_SIZE
...............
00228500 A _ebss
00228500 A _end
00230000 A _stack
00238000 A _estack
00238000 A _heap
002f8000 A _eheap
002f8000 A _eram_seg

Zheng


________________________________________
From: coreboot-bounces at coreboot.org [mailto:coreboot-bounces at coreboot.org] On Behalf Of Stefan Reinauer
Sent: Sunday, February 28, 2010 5:27 PM
To: Zheng Bao
Cc: coreboot at coreboot.org; <mylesgw at gmail.com>
Subject: Re: [coreboot] [patch] RE: Fam10 breakage

Have you tried compiling with the reference cross compiler from util/crossgcc? 

Stefan

On 28.02.2010, at 04:52, Zheng Bao <fishbaoz at hotmail.com> wrote:
Unfortunately, it doesn't fix my problem here. It is the coreboot_ram.map
of serengeti_cheetah_fam10 built on my machine. The _estack is not
what we expect. Myles, what is the result at you machine?
 
00000030 A CONFIG_MAX_CPUS
...............
00002000 A CONFIG_STACK_SIZE
...............
00228550 A _ebss
00228550 A _end
0022a000 A _stack
0022c000 A _estack
0022c000 A _heap
002ec000 A _eheap
002ec000 A _eram_seg
01000000 A CONFIG_RAMTOP
04000000 A CONFIG_AGP_APERTURE_SIZE
fff80000 A CONFIG_XIP_ROM_BASE
ffff0000 A CONFIG_ROMBASE

 
Zheng
 
________________________________________
Date: Fri, 26 Feb 2010 13:32:49 -0700
From: mylesgw at gmail.com
To: patrick at georgi-clan.de
CC: coreboot at coreboot.org
Subject: Re: [coreboot] [patch] RE: Fam10 breakage


On Fri, Feb 26, 2010 at 1:24 PM, Patrick Georgi <patrick at georgi-clan.de> wrote:
Am 26.02.2010 16:35, schrieb Myles Watson:
> For me, the only change that needs to be made is:
>
> -           . = ((CONFIG_CONSOLE_VGA ||
> CONFIG_PCI_ROM_RUN)&&(CONFIG_RAMBASE<0x100000)&&(CONFIG_RAMTOP>0x100000)
> ) ? CONFIG_STACK_SIZE : (CONFIG_MAX_CPUS*CONFIG_STACK_SIZE);
>
> +           . += ((CONFIG_CONSOLE_VGA ||
> CONFIG_PCI_ROM_RUN)&&(CONFIG_RAMBASE<0x100000)&&(CONFIG_RAMTOP>0x100000)
> ) ? CONFIG_STACK_SIZE : (CONFIG_MAX_CPUS*CONFIG_STACK_SIZE);
>
> Removing the .stack construct makes no difference.
>
> I like the idea of minimizing the change.
Sounds good, and should be stable (unless that's part of the bug Zheng
Bao is experiencing).

I'd say, commit this (as it fixes things for you). If it's not enough,
we can do the full change.
Great.
 
Acked-by: Patrick Georgi <patrick.georgi at coresystems.de>
Rev 5166.

Thanks,
Myles
________________________________________
Hotmail: Trusted email with powerful SPAM protection. Sign up now. 
-- 
coreboot mailing list: coreboot at coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot





More information about the coreboot mailing list