Patchwork [2/2,v2] meta-skeleton: Add busybox config fragment example

login
register
mail settings
Submitter Saul Wold
Date Aug. 13, 2013, 5:11 p.m.
Message ID <1376413879-9809-1-git-send-email-sgw@linux.intel.com>
Download mbox | patch
Permalink /patch/55557/
State New
Headers show

Comments

Saul Wold - Aug. 13, 2013, 5:11 p.m.
This shows an example of the config fragment support that
both the linux-yocto and busybox recipes use. This example
is specific to busybox.

By adding busybox CONFIG options into a .cfg file and then
adding that .cfg file to SRC_URI the merge_config.sh script will
correctly handle these CONFIG options during the do_configure task.

v2: fixed FILESEXTRAPATHS

Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
 meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg   | 1 +
 meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend | 5 +++++
 2 files changed, 6 insertions(+)
 create mode 100644 meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
 create mode 100644 meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
Laszlo Papp - Aug. 13, 2013, 5:23 p.m.
How will this know which files exactly to disregard in the busybox include
file (".inc")?

Could you please give that to the commit message as explanation?


On Tue, Aug 13, 2013 at 6:11 PM, Saul Wold <sgw@linux.intel.com> wrote:

> This shows an example of the config fragment support that
> both the linux-yocto and busybox recipes use. This example
> is specific to busybox.
>
> By adding busybox CONFIG options into a .cfg file and then
> adding that .cfg file to SRC_URI the merge_config.sh script will
> correctly handle these CONFIG options during the do_configure task.
>
> v2: fixed FILESEXTRAPATHS
>
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
>  meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg   | 1 +
>  meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend | 5 +++++
>  2 files changed, 6 insertions(+)
>  create mode 100644
> meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
>  create mode 100644
> meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
>
> diff --git a/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
> b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
> new file mode 100644
> index 0000000..42c6730
> --- /dev/null
> +++ b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
> @@ -0,0 +1 @@
> +CONFIG_RFKILL=n
> diff --git a/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
> b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
> new file mode 100644
> index 0000000..641f04a4
> --- /dev/null
> +++ b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
> @@ -0,0 +1,5 @@
> +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> +
> +SRC_URI += " \
> +           file://no_rfkill.cfg \
> +           "
> --
> 1.8.1.4
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
Laszlo Papp - Aug. 13, 2013, 5:23 p.m.
s/which files/which lines/


On Tue, Aug 13, 2013 at 6:23 PM, Laszlo Papp <lpapp@kde.org> wrote:

> How will this know which files exactly to disregard in the busybox include
> file (".inc")?
>
> Could you please give that to the commit message as explanation?
>
>
> On Tue, Aug 13, 2013 at 6:11 PM, Saul Wold <sgw@linux.intel.com> wrote:
>
>> This shows an example of the config fragment support that
>> both the linux-yocto and busybox recipes use. This example
>> is specific to busybox.
>>
>> By adding busybox CONFIG options into a .cfg file and then
>> adding that .cfg file to SRC_URI the merge_config.sh script will
>> correctly handle these CONFIG options during the do_configure task.
>>
>> v2: fixed FILESEXTRAPATHS
>>
>> Signed-off-by: Saul Wold <sgw@linux.intel.com>
>> ---
>>  meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg   | 1 +
>>  meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend | 5 +++++
>>  2 files changed, 6 insertions(+)
>>  create mode 100644
>> meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
>>  create mode 100644
>> meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
>>
>> diff --git a/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
>> b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
>> new file mode 100644
>> index 0000000..42c6730
>> --- /dev/null
>> +++ b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
>> @@ -0,0 +1 @@
>> +CONFIG_RFKILL=n
>> diff --git a/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
>> b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
>> new file mode 100644
>> index 0000000..641f04a4
>> --- /dev/null
>> +++ b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
>> @@ -0,0 +1,5 @@
>> +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>> +
>> +SRC_URI += " \
>> +           file://no_rfkill.cfg \
>> +           "
>> --
>> 1.8.1.4
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>
>
Mark Hatle - Aug. 13, 2013, 5:26 p.m.
On 8/13/13 12:11 PM, Saul Wold wrote:
> This shows an example of the config fragment support that
> both the linux-yocto and busybox recipes use. This example
> is specific to busybox.
>
> By adding busybox CONFIG options into a .cfg file and then
> adding that .cfg file to SRC_URI the merge_config.sh script will
> correctly handle these CONFIG options during the do_configure task.
>
> v2: fixed FILESEXTRAPATHS
>
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
>   meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg   | 1 +
>   meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend | 5 +++++
>   2 files changed, 6 insertions(+)
>   create mode 100644 meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
>   create mode 100644 meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
>
> diff --git a/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
> new file mode 100644
> index 0000000..42c6730
> --- /dev/null
> +++ b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
> @@ -0,0 +1 @@
> +CONFIG_RFKILL=n

Should be "# CONFIG_RFKILL is not set", I believe the =n will work, but it 
doesn't following the kconfig conventions.

--Mark

> diff --git a/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
> new file mode 100644
> index 0000000..641f04a4
> --- /dev/null
> +++ b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
> @@ -0,0 +1,5 @@
> +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> +
> +SRC_URI += " \
> +	    file://no_rfkill.cfg \
> +           "
>
Mark Hatle - Aug. 13, 2013, 5:33 p.m.
On 8/13/13 12:23 PM, Laszlo Papp wrote:
> s/which files/which lines/

The kernel configuration mechanism has a tool that will combine the original 
configuration, and any listed configuration fragments (.cfg files).  It will 
combine these, and then filter them in such a way that last-in wins.

See the Yocto Project Linux Kernel Development manual, section 2.2.3:

http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#changing-the-configuration

--Mark

> On Tue, Aug 13, 2013 at 6:23 PM, Laszlo Papp <lpapp@kde.org
> <mailto:lpapp@kde.org>> wrote:
>
>     How will this know which files exactly to disregard in the busybox include
>     file (".inc")?
>
>     Could you please give that to the commit message as explanation?
>
>
>     On Tue, Aug 13, 2013 at 6:11 PM, Saul Wold <sgw@linux.intel.com
>     <mailto:sgw@linux.intel.com>> wrote:
>
>         This shows an example of the config fragment support that
>         both the linux-yocto and busybox recipes use. This example
>         is specific to busybox.
>
>         By adding busybox CONFIG options into a .cfg file and then
>         adding that .cfg file to SRC_URI the merge_config.sh script will
>         correctly handle these CONFIG options during the do_configure task.
>
>         v2: fixed FILESEXTRAPATHS
>
>         Signed-off-by: Saul Wold <sgw@linux.intel.com <mailto:sgw@linux.intel.com>>
>         ---
>           meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg   | 1 +
>           meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend | 5 +++++
>           2 files changed, 6 insertions(+)
>           create mode 100644
>         meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
>           create mode 100644
>         meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
>
>         diff --git a/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
>         b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
>         new file mode 100644
>         index 0000000..42c6730
>         --- /dev/null
>         +++ b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
>         @@ -0,0 +1 @@
>         +CONFIG_RFKILL=n
>         diff --git a/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
>         b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
>         new file mode 100644
>         index 0000000..641f04a4
>         --- /dev/null
>         +++ b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
>         @@ -0,0 +1,5 @@
>         +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>         +
>         +SRC_URI += " \
>         +           file://no_rfkill.cfg \
>         +           "
>         --
>         1.8.1.4
>
>         _______________________________________________
>         Openembedded-core mailing list
>         Openembedded-core@lists.openembedded.org
>         <mailto:Openembedded-core@lists.openembedded.org>
>         http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
Darren Hart - Aug. 13, 2013, 5:40 p.m.
On Tue, 2013-08-13 at 12:26 -0500, Mark Hatle wrote:
> On 8/13/13 12:11 PM, Saul Wold wrote:
> > This shows an example of the config fragment support that
> > both the linux-yocto and busybox recipes use. This example
> > is specific to busybox.
> >
> > By adding busybox CONFIG options into a .cfg file and then
> > adding that .cfg file to SRC_URI the merge_config.sh script will
> > correctly handle these CONFIG options during the do_configure task.
> >
> > v2: fixed FILESEXTRAPATHS
> >
> > Signed-off-by: Saul Wold <sgw@linux.intel.com>
> > ---
> >   meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg   | 1 +
> >   meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend | 5 +++++
> >   2 files changed, 6 insertions(+)
> >   create mode 100644 meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
> >   create mode 100644 meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
> >
> > diff --git a/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
> > new file mode 100644
> > index 0000000..42c6730
> > --- /dev/null
> > +++ b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
> > @@ -0,0 +1 @@
> > +CONFIG_RFKILL=n
> 
> Should be "# CONFIG_RFKILL is not set", I believe the =n will work, but it 
> doesn't following the kconfig conventions.

Seconded. Or Thirded since I responded to V1 similarly. :-)

> 
> --Mark
> 
> > diff --git a/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
> > new file mode 100644
> > index 0000000..641f04a4
> > --- /dev/null
> > +++ b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
> > @@ -0,0 +1,5 @@
> > +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> > +
> > +SRC_URI += " \
> > +	    file://no_rfkill.cfg \
> > +           "
> >
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
Laszlo Papp - Aug. 13, 2013, 5:40 p.m.
On Tue, Aug 13, 2013 at 6:33 PM, Mark Hatle <mark.hatle@windriver.com>wrote:

> On 8/13/13 12:23 PM, Laszlo Papp wrote:
>
>> s/which files/which lines/
>>
>
> The kernel configuration mechanism has a tool that will combine the
> original configuration, and any listed configuration fragments (.cfg
> files).  It will combine these, and then filter them in such a way that
> last-in wins.
>
> See the Yocto Project Linux Kernel Development manual, section 2.2.3:
>
> http://www.yoctoproject.org/**docs/current/kernel-dev/**
> kernel-dev.html#changing-the-**configuration<http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#changing-the-configuration>


Could you please clarify how that is related to my question? What I wanna
understand is: I set something in the config as I wish, and then the
bitbake file is getting chopped respectively like with "ifdef/elif" etc in
C/C++, but this time inside the python script defined in the bitbake file.

I am well aware of that you can customize the defconfig, but my question
was about the python function.
Saul Wold - Aug. 13, 2013, 5:46 p.m.
On 08/13/2013 10:26 AM, Mark Hatle wrote:
> On 8/13/13 12:11 PM, Saul Wold wrote:
>> This shows an example of the config fragment support that
>> both the linux-yocto and busybox recipes use. This example
>> is specific to busybox.
>>
>> By adding busybox CONFIG options into a .cfg file and then
>> adding that .cfg file to SRC_URI the merge_config.sh script will
>> correctly handle these CONFIG options during the do_configure task.
>>
>> v2: fixed FILESEXTRAPATHS
>>
>> Signed-off-by: Saul Wold <sgw@linux.intel.com>
>> ---
>>   meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg   | 1 +
>>   meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend | 5 +++++
>>   2 files changed, 6 insertions(+)
>>   create mode 100644
>> meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
>>   create mode 100644
>> meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
>>
>> diff --git a/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
>> b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
>> new file mode 100644
>> index 0000000..42c6730
>> --- /dev/null
>> +++ b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
>> @@ -0,0 +1 @@
>> +CONFIG_RFKILL=n
>
> Should be "# CONFIG_RFKILL is not set", I believe the =n will work, but
> it doesn't following the kconfig conventions.
>
Yup, the commented out version works also, I will update the patch (v3), 
with


> --Mark
>
>> diff --git
>> a/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
>> b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
>> new file mode 100644
>> index 0000000..641f04a4
>> --- /dev/null
>> +++ b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
>> @@ -0,0 +1,5 @@
>> +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>> +
>> +SRC_URI += " \
>> +        file://no_rfkill.cfg \
>> +           "
>>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
Mark Hatle - Aug. 13, 2013, 5:58 p.m.
On 8/13/13 12:40 PM, Laszlo Papp wrote:
> On Tue, Aug 13, 2013 at 6:33 PM, Mark Hatle <mark.hatle@windriver.com
> <mailto:mark.hatle@windriver.com>> wrote:
>
>     On 8/13/13 12:23 PM, Laszlo Papp wrote:
>
>         s/which files/which lines/
>
>
>     The kernel configuration mechanism has a tool that will combine the original
>     configuration, and any listed configuration fragments (.cfg files).  It will
>     combine these, and then filter them in such a way that last-in wins.
>
>     See the Yocto Project Linux Kernel Development manual, section 2.2.3:
>
>     http://www.yoctoproject.org/__docs/current/kernel-dev/__kernel-dev.html#changing-the-__configuration
>     <http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#changing-the-configuration>
>
>
> Could you please clarify how that is related to my question? What I wanna
> understand is: I set something in the config as I wish, and then the bitbake
> file is getting chopped respectively like with "ifdef/elif" etc in C/C++, but
> this time inside the python script defined in the bitbake file.

You asked: How will this know which lines exactly to disregard in the busybox 
include file (".inc")?

My answer is that, according to the quoted documentation, the tooling, as 
described in the above URL, does this as a last-in processing, based on the 
filename(s) of the SRC_URI components.

> I am well aware of that you can customize the defconfig, but my question was
> about the python function.

Specifically for the busybox package, the python fragement "find_cfgs(d):" 
located in the busybox.inc file finds the .cfg files, and collects them into a 
list.  They are then processed by the 'merge_config.sh' script that is called as 
part of the do_configure task.

I believe the merge_config script is provided as part of the linux-libc-headers 
or linux-yocto package, but I may be incorrect on that.

--Mark
Bruce Ashfield - Aug. 13, 2013, 6:02 p.m.
On Tue, Aug 13, 2013 at 1:58 PM, Mark Hatle <mark.hatle@windriver.com> wrote:
> On 8/13/13 12:40 PM, Laszlo Papp wrote:
>>
>> On Tue, Aug 13, 2013 at 6:33 PM, Mark Hatle <mark.hatle@windriver.com
>> <mailto:mark.hatle@windriver.com>> wrote:
>>
>>     On 8/13/13 12:23 PM, Laszlo Papp wrote:
>>
>>         s/which files/which lines/
>>
>>
>>     The kernel configuration mechanism has a tool that will combine the
>> original
>>     configuration, and any listed configuration fragments (.cfg files).
>> It will
>>     combine these, and then filter them in such a way that last-in wins.
>>
>>     See the Yocto Project Linux Kernel Development manual, section 2.2.3:
>>
>>
>> http://www.yoctoproject.org/__docs/current/kernel-dev/__kernel-dev.html#changing-the-__configuration
>>
>>
>> <http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#changing-the-configuration>
>>
>>
>> Could you please clarify how that is related to my question? What I wanna
>> understand is: I set something in the config as I wish, and then the
>> bitbake
>> file is getting chopped respectively like with "ifdef/elif" etc in C/C++,
>> but
>> this time inside the python script defined in the bitbake file.
>
>
> You asked: How will this know which lines exactly to disregard in the
> busybox include file (".inc")?
>
> My answer is that, according to the quoted documentation, the tooling, as
> described in the above URL, does this as a last-in processing, based on the
> filename(s) of the SRC_URI components.
>
>
>> I am well aware of that you can customize the defconfig, but my question
>> was
>> about the python function.
>
>
> Specifically for the busybox package, the python fragement "find_cfgs(d):"
> located in the busybox.inc file finds the .cfg files, and collects them into
> a list.  They are then processed by the 'merge_config.sh' script that is
> called as part of the do_configure task.
>
> I believe the merge_config script is provided as part of the
> linux-libc-headers or linux-yocto package, but I may be incorrect on that.

close, it's from the kern-tools package, but it is an upstream kernel script. We
use it from kern-tools to avoid fetching the kernel to use it for busybox.

Bruce

>
> --Mark
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
Otavio Salvador - Aug. 13, 2013, 6:39 p.m.
On Tue, Aug 13, 2013 at 2:11 PM, Saul Wold <sgw@linux.intel.com> wrote:
> This shows an example of the config fragment support that
> both the linux-yocto and busybox recipes use. This example
> is specific to busybox.
>
> By adding busybox CONFIG options into a .cfg file and then
> adding that .cfg file to SRC_URI the merge_config.sh script will
> correctly handle these CONFIG options during the do_configure task.
>
> v2: fixed FILESEXTRAPATHS

This should be bellow --- line or it ends in the commit log.

> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
>  meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg   | 1 +
>  meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend | 5 +++++
>  2 files changed, 6 insertions(+)
>  create mode 100644 meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
>  create mode 100644 meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
>
> diff --git a/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
> new file mode 100644
> index 0000000..42c6730
> --- /dev/null
> +++ b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
> @@ -0,0 +1 @@
> +CONFIG_RFKILL=n
> diff --git a/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
> new file mode 100644
> index 0000000..641f04a4
> --- /dev/null
> +++ b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
> @@ -0,0 +1,5 @@
> +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> +
> +SRC_URI += " \
> +           file://no_rfkill.cfg \
> +           "
> --
> 1.8.1.4
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

Patch

diff --git a/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
new file mode 100644
index 0000000..42c6730
--- /dev/null
+++ b/meta-skeleton/recipes-core/busybox/busybox/no_rfkill.cfg
@@ -0,0 +1 @@ 
+CONFIG_RFKILL=n
diff --git a/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
new file mode 100644
index 0000000..641f04a4
--- /dev/null
+++ b/meta-skeleton/recipes-core/busybox/busybox_1.21.1.bbappend
@@ -0,0 +1,5 @@ 
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+SRC_URI += " \
+	    file://no_rfkill.cfg \
+           "