All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/4] configs/imx6-sabresd_qt5: Select the KMSRO gallium driver
Date: Fri, 11 Oct 2019 15:20:18 +0200	[thread overview]
Message-ID: <20191011152018.46a51ec2@windsurf> (raw)
In-Reply-To: <CAK4VdL34zHGntieYHunSrOwMCcH05R_YwhGJd9jd8t_tpPYUvg@mail.gmail.com>

On Fri, 11 Oct 2019 15:15:16 +0200
Erico Nunes <nunes.erico@gmail.com> wrote:

> I think it is a valid choice to not have it. For example, you might be
> interested in only having the GPU for offscreen rendering. So if you
> do want the drm driver to bridge to the display, I think you should
> just enable kmsro.

Ah, OK, indeed that makes sense. I'll revive Fabio's patch then.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-10-11 13:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09 17:00 [Buildroot] [PATCH v2 1/4] configs/imx6-sabresd_qt5: Move from mdev to eudev Fabio Estevam
2019-10-09 17:00 ` [Buildroot] [PATCH v2 2/4] configs/imx6-sabresd_qt5: Select the KMSRO gallium driver Fabio Estevam
2019-10-10 20:38   ` Thomas Petazzoni
2019-10-11  2:37     ` Fabio Estevam
2019-10-11 13:15       ` Erico Nunes
2019-10-11 13:20         ` Thomas Petazzoni [this message]
2019-10-16 20:50           ` Fabio Estevam
2019-10-09 17:00 ` [Buildroot] [PATCH v2 3/4] imx6-sabresd/readme.txt: Improve Qt5 Cinematic Demo instructions Fabio Estevam
2019-10-10 20:38   ` Thomas Petazzoni
2019-10-09 17:00 ` [Buildroot] [PATCH v2 4/4] configs/imx6-sabresd: Bump U-Boot and kernel versions Fabio Estevam
2019-10-10 20:39   ` Thomas Petazzoni
2019-10-10 20:38 ` [Buildroot] [PATCH v2 1/4] configs/imx6-sabresd_qt5: Move from mdev to eudev Thomas Petazzoni

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=20191011152018.46a51ec2@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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.