[coreboot] Resend: [PATCH] add h8dmr fam10 target

[ron minnich]

On Tue, Sep 22, 2009 at 6:17 AM, Ward Vandewege <ward at gnu.org> wrote:
> Ping - can I get an ack please? I've got a machine running this port for
> almost 2 months now, so it's at least somewhat useable. The outstanding
> issues below are not related to this port as such.
>
> Thanks,
> Ward.
>
> ---------------------------------
>
> See attached.
>
> There are a number of outstanding issues:
>
> * we don't have the mc_patch_01000086.h CPU ucode file yet which is
> referenced in a comment in src/mainboard/supermicro/h8dmr_fam10/Options.lb.
> AMD has not released it yet. This is not a problem specific to this port.
>
> * I'm seeing toolchain issues. I can't get this tree to compile correctly with
> gcc 4.3 (32 bit) - there is an optimization issue where certain parts of the
> CBFS code execute very slowly. With gcc 3.4 (32 bit) that slowness
> disappears. This is probably not a problem related to this port specifically.

I don't think it's toolchain, with this description. This sounds more
like a cache issue.

>
> * setting CONFIG_DEFAULT_CONSOLE_LOGLEVEL lower than 8 simply hangs the boot
> shortly after the warm reset triggered by the MCP55 code. I think this too
> might be a toolchain problem (but I see it on gcc 3.4 as well as 4.3).

There ought to be a warning in the target .config to this effect, else
others will be confused.

>
> * during startup, the CPU cores talk through each other on serial for a
> while. Again, not an issue specific to this port.

Geez, I thought all the discussion had fixed that :-)

>
> * to avoid very slow LZMA decompression I use this port with LZMA compression
> disabled in CBFS. I'm not sure what's causing this particular slowness.

This and the other problem sure sound like a few weird possibilities.
What do the MTRRs look like once booted? Is there any chance you are
somehow running on a core that is not set up correctly (this used to
really happen sometimes).

I think this description of problems with the port ought to be in the
target file in a README.

ron