From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] busybox: Add check for wifi/bluetooth to enable rfkill
Date: Tue, 12 Jun 2012 16:35:44 +0100 [thread overview]
Message-ID: <1339515344.8065.14.camel@ted> (raw)
In-Reply-To: <1339514126-23855-1-git-send-email-sgw@linux.intel.com>
On Tue, 2012-06-12 at 08:15 -0700, Saul Wold wrote:
> rfkill is a usefull tool when you have a device with bluetooth and wifi enabled
>
> [YOCTO #2494]
>
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
> meta/recipes-core/busybox/busybox.inc | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-core/busybox/busybox.inc b/meta/recipes-core/busybox/busybox.inc
> index 5b83d32..83b25b4 100644
> --- a/meta/recipes-core/busybox/busybox.inc
> +++ b/meta/recipes-core/busybox/busybox.inc
> @@ -57,6 +57,11 @@ def features_to_busybox_settings(d):
> busybox_cfg('nls', distro_features, 'CONFIG_LOCALE_SUPPORT', cnf, rem)
> busybox_cfg('ipv4', distro_features, 'CONFIG_FEATURE_IFUPDOWN_IPV4', cnf, rem)
> busybox_cfg('ipv6', distro_features, 'CONFIG_FEATURE_IFUPDOWN_IPV6', cnf, rem)
> + busybox_cfg('wifi', distro_features, 'CONFIG_RFKILL', cnf, rem)
> + busybox_cfg('bluetooth', distro_features, 'CONFIG_RFKILL', cnf, rem)
> + machine_features = d.getVar('MACHINE_FEATURES', True).split()
> + busybox_cfg('wifi', machine_features, 'CONFIG_RFKILL', cnf, rem)
> + busybox_cfg('bluetooth', machine_features, 'CONFIG_RFKILL', cnf, rem)
> return "\n".join(cnf), "\n".join(rem)
>
> # X, Y = ${@features_to_uclibc_settings(d)}
This makes the busybox package machine specific? Is that intentional?
Cheers,
Richard
prev parent reply other threads:[~2012-06-12 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 15:15 [PATCH 1/1] busybox: Add check for wifi/bluetooth to enable rfkill Saul Wold
2012-06-12 15:29 ` Khem Raj
2012-06-12 15:35 ` Richard Purdie [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=1339515344.8065.14.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox