How Chrome OS works upstream

I'm responsible for a couple of such (embedded) beasts. And oh what a nice place it is to be there! *Everything* is upstreamed (which was a handful of drivers plus a new subsystem actually, so it certainly wasn't a trivial process). And there is no longer any dependency on some long string of patches from the SoC vendor since they have done their part.

Which means that bisecting problems is actually possible and simple, something which I found very difficult before the SoC was sufficiently supported upstream.

It is highly recommended to seek this position!

That said, we pick a kernel from the stable tree (i.e. it has backports) when we do update, so it's not actually a SHA1 from Linus' tree. But close enough, and we could do that if we wanted to...