Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] configs/imx6-sabresd_qt5: Move mdev from eudev
Date: Wed,  9 Oct 2019 13:55:58 -0300	[thread overview]
Message-ID: <20191009165601.3424-1-festevam@gmail.com> (raw)

Since commit cf66a67112cd706d2e7 ("package/glmark2: drm support needs udev")
udev is needed when the drm flavor is used.

Move mdev from eudev in order to fix the following glmark2
build failure:

Unknown flavor: . Supported flavors are dispmanx-glesv2, drm-gl,
drm-glesv2, mir-gl, mir-glesv2, wayland-gl, wayland-glesv2, win32-gl,
win32-glesv2, x11-gl, x11-glesv2

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

diff --git a/configs/imx6-sabresd_qt5_defconfig b/configs/imx6-sabresd_qt5_defconfig
index 4616f57eae..a2925bd056 100644
--- a/configs/imx6-sabresd_qt5_defconfig
+++ b/configs/imx6-sabresd_qt5_defconfig
@@ -95,4 +95,4 @@ BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_VIDEOPARSERS=y
 BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_KMS=y
 
 # For automatic kernel module loading
-BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV=y
+BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=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 Fabio Estevam [this message]
2019-10-09 16:55 ` [Buildroot] [PATCH 2/4] configs/imx6-sabresd_qt5: Select the KMSRO gallium driver Fabio Estevam
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-1-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