All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: Alper Nebi Yasak <alpernebiyasak@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jack Rosenthal <jrosenth@chromium.org>,
	Douglas Anderson <dianders@chromium.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	coreboot@coreboot.org, Guenter Roeck <groeck@chromium.org>,
	Stephen Boyd <swboyd@chromium.org>,
	Wei-Ning Huang <wnhuang@chromium.org>,
	Julius Werner <jwerner@chromium.org>,
	Samuel Holland <samuel@sholland.org>
Subject: Re: [PATCH] firmware: coreboot: framebuffer: Allow building with simpledrm
Date: Tue, 25 Jul 2023 11:02:21 -0700	[thread overview]
Message-ID: <ZMAOLQWrRttRgpoP@google.com> (raw)
In-Reply-To: <20230725174334.887485-1-alpernebiyasak@gmail.com>

(administrative note: I doubt coreboot@coreboot.org is interested in
receiving linux kernel driver patches)

On Tue, Jul 25, 2023 at 08:43:33PM +0300, Alper Nebi Yasak wrote:
> The coreboot framebuffer driver registers a "simple-framebuffer" device
> based on the information from the firmware, after checking that it's
> compatible with the formats listed in simplefb.h. It was added before
> simpledrm, and its Kconfig marked as dependent on the simplefb driver.
> 
> The simpledrm driver can also handle "simple-framebuffer" devices and
> the coreboot framebuffer works fine with it on a 'Lick' Chromebook.
> Allow building the coreboot framebuffer driver with simpledrm as well.
> 
> Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>

Reviewed-by: Brian Norris <briannorris@chromium.org>

      reply	other threads:[~2023-07-25 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 17:43 [PATCH] firmware: coreboot: framebuffer: Allow building with simpledrm Alper Nebi Yasak
2023-07-25 18:02 ` Brian Norris [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=ZMAOLQWrRttRgpoP@google.com \
    --to=briannorris@chromium.org \
    --cc=alpernebiyasak@gmail.com \
    --cc=coreboot@coreboot.org \
    --cc=dianders@chromium.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=groeck@chromium.org \
    --cc=jrosenth@chromium.org \
    --cc=jwerner@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samuel@sholland.org \
    --cc=swboyd@chromium.org \
    --cc=wnhuang@chromium.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.