You need to compile with debug symbols if you want to break using line numbers
of a file. Else you have to set breakpoints on address
sin9yt
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org
Hi everybody,
Firstly, I want to introduce myself. I'm Jan Dabros and I'm working for
Semihalf - embedded system company based in Poland. I am a big fan of
coreboot and the idea of open firmware in general, that's why would really
like to contribute to this project. Let's see how it goes :)
My
Hi Michal,
On 27.03.20 15:49, Michal Zygowski wrote:
> Another question about libgfxinit.
>
> Up till Skylake the libgfxinit worked great for me, however after
> enabling it on a Kaby Lake platform I noticed the colors are flipped.
> I.e. when using VGA ROM the bootsplash image is correctly
Another question about libgfxinit.
Up till Skylake the libgfxinit worked great for me, however after
enabling it on a Kaby Lake platform I noticed the colors are flipped.
I.e. when using VGA ROM the bootsplash image is correctly displayed in
RGB, but when using libgfxinit and hires FB the colors
I did a compare of the UFEIPAYLOAD.fd with the one extracted. There are some
header starting with .ELF in the extracted one. It's possibly the reason why
the extracted one works. The header is possibly added by cbfstool when it build
the image.
Mar 25, 2020, 00:17 by
Hello Everybody,
I am new to coreboot build environment and need your help in using gdb with
coreboot.
I want to use gdb to take a closer look at the stages in coreboot and the order
they are executed in. I also want to single step through the code to see what
functions are being called in
6 matches
Mail list logo
