Re: [coreboot] memset called to somewhere high on the stack (uncached)

[Myles Watson]

On Tue, Apr 6, 2010 at 4:21 PM, Myles Watson  wrote:
> I'm seeing code reads to memset() in coreboot_ram interleaved with byte
> writes to somewhere high on the stack (_estack -0x1fC).  This is a k8.

It turns out init_processor_name() was being called with the cache
disabled.  It doesn't look like it needs to be.  Boot tested on my box.
This makes it more similar to model_10.

Signed-off-by: Myles Watson

Thanks,
Myles