Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] configs/imx6-sabresd_qt5: Select the KMSRO gallium driver
Date: Wed,  9 Oct 2019 13:55:59 -0300	[thread overview]
Message-ID: <20191009165601.3424-2-festevam@gmail.com> (raw)
In-Reply-To: <20191009165601.3424-1-festevam@gmail.com>

After migrating to Mesa 19.2 the imx-drm_dri.so is no longer installed
unless the kmsro gallium driver is selected, so explicitly select
BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_KMSRO to fix the problem.

Suggested-by: Peter Seiderer <ps.report@gmx.net>
Signed-off-by: Fabio Estevam <festevam@gmail.com>
---
 configs/imx6-sabresd_qt5_defconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/configs/imx6-sabresd_qt5_defconfig b/configs/imx6-sabresd_qt5_defconfig
index a2925bd056..887e53dc21 100644
--- a/configs/imx6-sabresd_qt5_defconfig
+++ b/configs/imx6-sabresd_qt5_defconfig
@@ -48,6 +48,7 @@ BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
 # GL driver
 BR2_PACKAGE_MESA3D=y
 BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_ETNAVIV=y
+BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_KMSRO=y
 BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_SWRAST=y
 BR2_PACKAGE_MESA3D_OPENGL_ES=y
 
-- 
2.17.1

  reply	other threads:[~2019-10-09 16:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09 16:55 [Buildroot] [PATCH 1/4] configs/imx6-sabresd_qt5: Move mdev from eudev Fabio Estevam
2019-10-09 16:55 ` Fabio Estevam [this message]
2019-10-09 16:56 ` [Buildroot] [PATCH 3/4] imx6-sabresd/readme.txt: Improve Qt5 Cinematic Demo instructions Fabio Estevam
2019-10-09 16:56 ` [Buildroot] [PATCH 4/4] configs/imx6-sabresd: Bump U-Boot and kernel versions Fabio Estevam
2019-10-09 19:14 ` [Buildroot] [PATCH 1/4] configs/imx6-sabresd_qt5: Move mdev from 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=20191009165601.3424-2-festevam@gmail.com \
    --to=festevam@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox