On 4 October 2014 19:00, Michael Gloff mgl...@emacinc.com wrote:
I've run into a slight issue that when I enable RFKILL in busybox config, my
config gets overwritten by busybox.inc. I do not have wifi in
DISTRO_FEATURES. I believe that
busybox_cfg(bb.utils.contains('DISTRO_FEATURES', 'wifi', True, False, d),
'CONFIG_RFKILL', cnf, rem)
is not performing as intended and am unsure how to fix. I've tried a couple
of variations, but wound up just commenting it out for my local builds.
Basically, rfkill does not get configured in unless you have wifi
DISRO_FEATURES.
That logic is behaving exactly as intended: if the DISTRO_FEATURES
contains wifi then enable CONFIG_RFKILL, otherwise disable it.
I presume you're planning on using rfkill with bluetooth radios? That
test needs to be extended to check for either wifi or bluetooth.
Patches welcome! (change contains() to contains_any(), and pass wifi
bluetooth).
Ross
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
