Hi
On Tue, Apr 21, 2015 at 7:48 AM, Aaron Durbin adurbin@chromium.org wrote:
On Tue, Apr 21, 2015 at 12:35 AM, Anatol Pomozov anatol.pomozov@gmail.com wrote:
Hi
I am playing with coreboot and try to build it with seabios payload for my Zako device. Here is .config I use to compile coreboot at current HEAD (4038a7f631dc) https://gist.github.com/a950a69e737ac06a24f3 I use board "Panther" that I believe is the same as one in my Zako.
I use google's servo to deploy FW to the board and I see a weird debug log in my console. The log from coreboot looks like newline is inserted, but return caret is not. SeaBIOS debug looks normal. Here and the log example https://gist.github.com/anatol/8e30c8d5045ddf7e6b03
The host is Linux Arch. I tried several different console apps (cu, com) but result is the same.
Dear community, do you have ideas what can make the coreboot log unreadable?
Feel free to cherry pick this: http://review.coreboot.org/9932
Thanks Aaron, it fixed the issue for me.
Also, I've been working on optimizing SeaBIOS/coreboot for all the Haswell ChromeBoxes for the past year, and noticed that your config isn't ideal. Feel free to check out my config, build scripts, etc at https://github.com/MattDevo/coreboot and lmk if you have any questions (or feedback/improvements etc)
Thanks Matt. Checking your configs and patches is on my TODO list.