[OE-core] [PATCH] busybox-1.21.1/defconfig: disable rfkill
Phil Blundell
pb at pbcl.net
Tue Aug 13 10:17:53 UTC 2013
There's no magic involved in the python function: all it does is
generate a config fragment which is then passed to merge_config.sh along
with everything else. If you supply your own fragment as Ross suggested
then it should override the values from the Python-generated one and
everything ought to work as you would expect.
p.
On Tue, 2013-08-13 at 11:00 +0100, Laszlo Papp wrote:
> Why are you referring to defconfig when I mentioned several times, the
> problem is the inc file and a python function; i.e. not the kernel,
> nor the busybox config?
>
>
> On Tue, Aug 13, 2013 at 10:58 AM, Burton, Ross <ross.burton at intel.com>
> wrote:
> On 13 August 2013 10:52, Laszlo Papp <lpapp at kde.org> wrote:
> > As we have already discussed that, it is not any clear at
> all without
> > example. Yes, the end user does not really care about the
> internal
> > implementation of the feature ....
> >
> > Please provide useful examples and tutorials how to use a
> feature especially
> > when a user (and apparently others posting here) is such
> clueless.
>
>
> Personally I've never touched busybox configuration so this is
> untested. However it claims to support configuration
> fragments as
> used by the kernel (as both busybox and the kernel use the
> same
> configuration system), so this section in the kernel
> documentation
> should be useful:
>
> http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#changing-the-configuration
>
> tl;dr: put a file such as myconfig.cfg in SRC_URI which
> contains the
> configuration variables you want set.
>
> Ross
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
More information about the Openembedded-core
mailing list