From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Alper Nebi Yasak <alpernebiyasak@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
chrome-platform@lists.linux.dev,
Patrick Georgi <pgeorgi@chromium.org>,
Julius Werner <jwerner@chromium.org>,
Samuel Holland <samuel@sholland.org>,
coreboot@coreboot.org, Brian Norris <briannorris@chromium.org>
Subject: Re: [PATCH] firmware: coreboot: framebuffer: Avoid invalid zero physical address
Date: Thu, 28 Dec 2023 11:17:14 +0800 [thread overview]
Message-ID: <ZYzourLcnrxRubaG@google.com> (raw)
In-Reply-To: <20231108182625.46563-1-alpernebiyasak@gmail.com>
On Wed, Nov 08, 2023 at 09:25:13PM +0300, Alper Nebi Yasak wrote:
> On ARM64 systems coreboot defers framebuffer allocation to its payload,
> to be done by a libpayload function call. In this case, coreboot tables
> still include a framebuffer entry with display format details, but the
> physical address field is set to zero (as in [1], for example).
>
> Unfortunately, this field is not automatically updated when the
> framebuffer is initialized through libpayload, citing that doing so
> would invalidate checksums over the entire coreboot table [2].
>
> [...]
Applied, thanks!
[1/1] firmware: coreboot: framebuffer: Avoid invalid zero physical address
commit: ecea08916418a94f99f89c543303877cb6e08a11
Just realized the bot didn't send the mail for the patch.
prev parent reply other threads:[~2023-12-28 3:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 18:25 [PATCH] firmware: coreboot: framebuffer: Avoid invalid zero physical address Alper Nebi Yasak
2023-11-08 23:53 ` Julius Werner
2023-12-28 3:17 ` Tzung-Bi Shih [this message]
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=ZYzourLcnrxRubaG@google.com \
--to=tzungbi@kernel.org \
--cc=alpernebiyasak@gmail.com \
--cc=briannorris@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=coreboot@coreboot.org \
--cc=gregkh@linuxfoundation.org \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgeorgi@chromium.org \
--cc=samuel@sholland.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).