Re: [coreboot] [PATCH] First support for HP DL145 G3

[samuel]

Acked-by: Samuel Verstraete <samuel.verstraete at gmail.com>

2009/3/31 Mondrian Nuessle :
> Hi everybody,
>
> I prepared an initial set of patches to support the HP DL145 G3 server, which is a Broadcom HT-1000/HT-2100 based Socket
> F machine.
>
> The current status of the port is:
> we have serial output (using the serverengines pilot chip on the board, see attached pilot_superio.patch)
> CPU and memory gets initialized
> on-board eth0 is working
> SATA is working
> the on-board graphic was not tested (not important for
>
> a server and the graphics sucks anyway...)
> USB and PS2 work
> no ACPI
> I remember that I could also use a PCIe card, see attached bcm21000.patch
> HTX card does work.
> Earlier problems we had in respect to timer interrupt are not there anymore.
> the hp_dl145_g3.patch includes the mainboard and the target dirs
>
> BUT:
> if I coldboot, the CPUs are only running at 1 GHz and not with 2.6 GHz as they should...
> if we boot the factory BIOS and then perform a warm-reset into Coreboot, the CPUs run with 2.6 GHz.
>
> I hope someone on the list can help.
> There are also some more problems with the HT-1000 (aka bcm5785) southbridge:
>
> - if I activate IDE in bcm5785_early_setup.c, the machine will freeze shortly after being completely booted
>  - if I activate the second IOAPIC (line 179 in bcm5785_early_setup.c), my linux boot hangs when starting udevd...
>  - with both features disabled (see attached bcm5785_noide.patch), the machine boots and does not crash, of course
>    PATA drives are not available.
>
> To boot the machine, I tested FILO. The on-board SATA adapter uses a class id of 0x104 in sata mode
> (which we use). FILO does not accept this class ID; I prepared a patch that adds this class ID to
> the respective if statement in driver/ide.c. FILO does then boot from SATA without any problems (see attached
> filo_dl145_sata.patch).
>
> I hope this gets you started Samuel, and I hope the list can provide some insight regarding the CPU
> frequency problem.
>
> Regards,
> Mondrian