[coreboot] Removing microcode updates from blobs

Gabe Black gabeblack at google.com
Sat Dec 14 06:24:02 CET 2013

If you don't want to hear it, ignore it. We shouldn't break things just so
people with mistaken opinions are happy, nor how long it took to rearrange
things into a broken state.


On Fri, Dec 13, 2013 at 9:14 PM, mrnuke <mr.nuke.me at gmail.com> wrote:

> On 12/13/2013 09:44 PM, ron minnich wrote:
> > I guess I don't understand why people feel better being able to build
> > a firmware image which will boot the CPU in a broken mode.
> >
> I have no idea either. However, what I do have is chronic fatigue from
> hearing clueless people complain and moan about having microcode in
> their coreboot.
> I want my time with the coreboot community to be fun. I like talking
> about silly mistakes that cost me hours or days. I like being made fun
> of when that happens. I like doing fun stuff. I like playing with
> hardware. I do NOT like litter from useless philosophical discussions
> about which blob is more acceptable than the other.
> I spend a few weeks now completing the change, and in exchange, I get a
> lifetime of peace on the matter. We all do. It's a win-win. The change
> will be mostly transparent to the average coreboot user.
> What's there not to like?
> Alex
> --
> coreboot mailing list: coreboot at coreboot.org
> http://www.coreboot.org/mailman/listinfo/coreboot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20131213/ca7586f4/attachment-0001.html>

More information about the coreboot mailing list