Personal oppinions

Microcode

The issue about the CPU microcodes is that they are non-free, and under a license that is incompatible with coreboot's license.

Practically speaking, I guess that if the microcode is in the cbfs(coreboot filesystem) instead of beeing integrated directly in coreboot, that would count as agrgate work and should be safe, but I'm not a lawyer(so ask a good one instead).
The solution would then be to remove the microcodes from the coreboot repositories.

(I guess that it would then end up in the blob repository instead which is a separate repository, and would then be included in the coreboot filesytem).

Some people say that the microcode is the equivalent of having a more recent CPU, as a justification for using it.
Though since Intel microcodes are encrypted and signed, its meaning is not public, therefore we can't really know what's inside, so people usually trust what the CPU vendor say about it, such as that it fixes some bugs(erratas for such bugs are published).

My goal is to have a 100% free computer, and also to spread that code, so that other people can have a 100% free computer too.
According to the FSF, and the FSF criterias for differenciating software from hardware, that microcode is software.
So since they consider it as non-free, a coreboot image containing that microcode would not be considered free by the FSF.

On my Lenovo x60, the microcode was easy to remove, and it worked fine, beside printing a scary kernel message pointing to an Intel errata.
Practically speaking, after resuming(so after suspend to ram), the temperatures reading will not be updated, and the temperature overheat will not be reported. The hardware issues you may encounter will depend on your specific CPU, not the model, but instead the date at which it was manufactured.

The result of it is that the FSF certified the gluglug's lenovo x60: gluglug removed the last microcodes(that were not used by the x60), sent that source code to the FSF, which certified it.
So instead of debating trough huge flames aobut the fact that we should use, or not use the microcode, it was more effective to remove it.
The benefit is the publicity arround that laptop that can be made 100% free software, which makes users aware of it and willing to switch to it.

For coreboot developers

This section is mainly usefull for finding informations for:

Asking me to test some code (that's why I listed all my hardware).

Find my work in progress code.

Find legacy code.

Find what I'm interested in working on:

If you want to work on the same thing than me, you could contact me if you want so:

I could help if I have time.

I could test if I have time.

I may have some pointers.

HOWTO that documents how to do a native VGA init for the Lenovo x60:

It probably applies to the Lenovo t60 that have an Intel GPU, with no or very minor modifications.

Hardware

Mainboard/Devices running coreboot

Device/Mainboard

Serial/output

flash recovery mecanism

My work / area of interest

M4A785T-M

Serial

External programmer

Swapping the flash chip

I've been the main porter.

Lenovo X60

Serial on the dock

USB debug

spkmodem

External programmer with pomona clip

Native GPU init

Various other improvements.

Lenovo T60

USB debug

spkmodem(untried but should work)

External programmer with pomona clip(untried but should work)

Various improvements.

Alix 1.C

Serial

Hot swap with the LPC dongle

Various improvements.

E350M1

Serial

Some other outputs may work but I didn't test them.

External programmer

Swapping the flash chip

None(I just use it).

Mainboard/Devices not running coreboot (yet?)

HP nc6320

Asus N71JQ

Note that they will probably never run coreboot, as I don't think they're worth the time.