From: Charles Manning <cdhmanning@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wf111: Add mdev dependency
Date: Tue, 11 Aug 2015 19:17:02 +1200 [thread overview]
Message-ID: <1439277422-26111-1-git-send-email-cdhmanning@gmail.com> (raw)
wf111 really needs mdev
Signed-off-by: Charles Manning <cdhmanning@gmail.com>
---
package/wf111/Config.in | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/package/wf111/Config.in b/package/wf111/Config.in
index d2ba440..c8a7537 100644
--- a/package/wf111/Config.in
+++ b/package/wf111/Config.in
@@ -2,6 +2,7 @@ config BR2_PACKAGE_WF111
bool "wf111"
depends on BR2_LINUX_KERNEL
depends on BR2_ARM_CPU_ARMV5 || BR2_ARM_CPU_ARMV7A || BR2_i386
+ depends on BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV
# Binary tools are distributed alongside the driver, and are
# dynamically linked against the glibc.
depends on BR2_TOOLCHAIN_USES_GLIBC
@@ -30,7 +31,7 @@ config BR2_PACKAGE_WF111_TARBALL_PATH
endif
-comment "wf111 needs an (e)glibc toolchain"
+comment "wf111 needs an (e)glibc toolchain and mdev"
depends on BR2_LINUX_KERNEL
depends on BR2_ARM_CPU_ARMV5 || BR2_ARM_CPU_ARMV7A || BR2_i386
- depends on !BR2_TOOLCHAIN_USES_GLIBC
+ depends on !BR2_TOOLCHAIN_USES_GLIBC || !BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV
--
1.9.1
next reply other threads:[~2015-08-11 7:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 7:17 Charles Manning [this message]
2015-08-11 11:40 ` [Buildroot] [PATCH] wf111: Add mdev dependency Baruch Siach
2015-08-11 20:11 ` Charles Manning
2015-08-12 4:38 ` Baruch Siach
2015-08-12 5:16 ` Charles Manning
2015-08-12 5:38 ` Baruch Siach
2015-08-12 5:56 ` Charles Manning
2015-08-12 22:54 ` Floris Bos
2015-08-12 10:29 ` Floris Bos
2015-08-12 20:49 ` Charles Manning
2015-08-12 21:47 ` Floris Bos
2015-08-18 20:28 ` 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=1439277422-26111-1-git-send-email-cdhmanning@gmail.com \
--to=cdhmanning@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