On Tue, Sep 21, 2021 at 03:07:25PM -0700, Julius Werner wrote:
> > Since it doesn't seem possible to have each boot component using the same
> > log
> > format, we added a log_format and log_phys_addr fields to give flexibility
> > in
> > how logs are stored. An example of a different log format
On Tue, Sep 21, 2021 at 03:40:20PM +, Peter Stuge wrote:
> Alec Brown wrote:
> > Below is how the layout of these logs would store their data.
> >
> > bf_log_header:
> >+---+
> > u32| version |
> > u32| size |
> >
On Sun, Sep 19, 2021 at 12:53:35AM +0200, Heinrich Schuchardt wrote:
>
>
> Am 18. September 2021 18:04:13 MESZ schrieb Alec Brown
> :
> >Hi everyone,
> >
> >I've been working on improving the specification for the firmware and
> >bootloader
> >log that Daniel Kiper has proposed and take into a
> Since it doesn't seem possible to have each boot component using the same log
> format, we added a log_format and log_phys_addr fields to give flexibility in
> how logs are stored. An example of a different log format that can be used is
> the cbmem_console log format used by coreboot:
I am not
Alec Brown wrote:
> Below is how the layout of these logs would store their data.
>
> bf_log_header:
>+---+
> u32| version |
> u32| size |
> u8[64] | producer |
> u8[64] | log_format|
>
Am 18. September 2021 18:04:13 MESZ schrieb Alec Brown
:
>Hi everyone,
>
>I've been working on improving the specification for the firmware and
>bootloader
>log that Daniel Kiper has proposed and take into account most of the
>suggestions
>that were made in these threads [1], [2].
>
>The goal
