All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: Julius Werner <jwerner@google.com>
Cc: coreboot@coreboot.org, seabios@seabios.org, grub-devel@gnu.org
Subject: Re: [coreboot] RFC: Changing CBMEM console to run as a persistent ring-buffer
Date: Sat, 22 Apr 2017 09:22:53 +0200	[thread overview]
Message-ID: <1492845773.2760.209.camel@users.sourceforge.net> (raw)
In-Reply-To: <CAODwPW_V+y_JmDx66g738vT=7uJwch=NXXVVHJ1y1K-urO=rDA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]

[For the GRUB folks, this is about coreboot commit d67c6876 (Turn CBMEM
console into a ring buffer that can persist across reboots) [1].
Julius’ message can be find in the coreboot list archive [2].]


Dear Julius,


Am Montag, den 10.04.2017, 15:50 -0700 schrieb Julius Werner:

[…]

> The change may also cause some hiccups if you're using a newer version of
> coreboot with an older version of cbmem (or SeaBIOS or whatever else reads
> the console): it will not crash and it will still print the whole log, but
> if the log has rolled over (into "ring buffer mode") it will print lines
> out of order. This is unfortunately the best I can do with the way current
> readers are implemented. I'm of course also updating the code for cbmem so
> as soon as you deploy the new version it will be able to display buffers
> from both old and new coreboot versions correctly. (I'll send patches to
> align SeaBIOS and the Linux memconsole driver in the same manner as soon as
> the coreboot patch is approved.)

Could you please also check, if GRUB’s CBMEM console driver, and the
the command cbmemc to display it need any updates?


Thanks,

Paul


PS: Where can I get your S/MIME certificate, used to sign your email?


[1] https://review.coreboot.org/18301
[2] https://mail.coreboot.org/pipermail/coreboot/2017-April/083950.html

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

       reply	other threads:[~2017-04-22  7:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAODwPW_V+y_JmDx66g738vT=7uJwch=NXXVVHJ1y1K-urO=rDA@mail.gmail.com>
2017-04-22  7:22 ` Paul Menzel [this message]
2017-04-24 23:51   ` [coreboot] RFC: Changing CBMEM console to run as a persistent ring-buffer Julius Werner
2017-04-25  5:26 Vladimir 'phcoder' Serbinenko
2017-04-25 18:15 ` Julius Werner
2017-04-25 18:25   ` Vladimir 'phcoder' Serbinenko
2017-04-25 18:48     ` Julius Werner
2017-04-25 20:16       ` Julius Werner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1492845773.2760.209.camel@users.sourceforge.net \
    --to=paulepanter@users.sourceforge.net \
    --cc=coreboot@coreboot.org \
    --cc=grub-devel@gnu.org \
    --cc=jwerner@google.com \
    --cc=seabios@seabios.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.