I was reading around and two of the things I came by, the OSCON 2013 slides ( https://docs.google.com/presentation/d/1eGPMu03vCxIO0a3oNX8Hmij_Qwwz6R6ViFC_1HlHOYQ/ ) and a post on SeaBIOS's mailing list ( http://www.seabios.org/pipermail/seabios/2013-April/006136.html ) mentioned pulling from the ChromiumOS's repos due to patches yet to be submitted to the upstream one. I'll still give the upstream repos a try, but does anyone know whether the upstream stuff are Link compatible?

Liwei

On 8 September 2013 02:51, John Lewis <jlewis@johnlewis.ie> wrote:

Well, you can try using the upstream coreboot git repo for a start - I haven't had much success using ChromiumOS's version. Largely due to the binaries they're using, I think.

John.

Liwei <xieliwei@gmail.com> wrote:

Hello list,
I've been tinkering around with the Pixel for a while and today decided to compile a copy of Coreboot on my own. As predicted for a first timer, I made a brick.

I can pretty much recover from that by reflashing with a bus pirate-like device, but I'm wondering what did I do wrong?

The device wakes up when I open the lid or press the power button (keyboard light goes on) but that's it. It still turns off if I hold on to the power button for a while.

Attached are my flash layout ( http://paste.ubuntu.com/6075724/ ) and coreboot config ( http://paste.ubuntu.com/6075719/ ).

Source is chromeos-2013.04 branch from https://chromium.googlesource.com/chromiumos/third_party/coreboot . The last commit is 747c728538785498b6d1aa7029a7673c91068ece.

SeaBIOS, which is my payload, is firmware-link-2695.B branch from https://chromium.googlesource.com/chromiumos/third_party/seabios . The last commit is 93d1fc99763baa363cbe1855b4533dfd4a1a0308.

I'd appreciate it very much if someone can give me some pointers on what I must do to get a working image. Thanks!

Liwei