From: Phil Blundell <pb@pbcl.net>
To: Laszlo Papp <lpapp@kde.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] busybox-1.21.1/defconfig: disable rfkill
Date: Tue, 13 Aug 2013 11:17:53 +0100 [thread overview]
Message-ID: <1376389073.10241.1.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <CAOMwXhPqdK9WvKmPD6rO33x==c8Dt0z5DrMBEx_s8G+t4nrLpg@mail.gmail.com>
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@intel.com>
> wrote:
> On 13 August 2013 10:52, Laszlo Papp <lpapp@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@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2013-08-13 10:18 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 7:16 [PATCH] busybox-1.21.1/defconfig: disable rfkill Laszlo Papp
2013-07-29 7:20 ` Paul Barker
2013-07-29 7:22 ` Laszlo Papp
2013-07-29 10:00 ` Phil Blundell
2013-07-29 10:01 ` Laszlo Papp
2013-07-29 10:20 ` Phil Blundell
2013-07-29 10:22 ` Laszlo Papp
2013-07-29 10:30 ` Laszlo Papp
2013-07-29 10:38 ` Phil Blundell
2013-07-29 10:42 ` Laszlo Papp
2013-07-29 10:46 ` Paul Barker
2013-07-29 10:48 ` Laszlo Papp
2013-07-29 11:05 ` Laszlo Papp
2013-07-29 10:46 ` Burton, Ross
2013-07-29 10:50 ` Laszlo Papp
2013-07-29 10:35 ` Phil Blundell
2013-07-29 10:37 ` Laszlo Papp
2013-07-29 12:18 ` Laszlo Papp
2013-07-29 12:20 ` Laszlo Papp
2013-07-29 13:34 ` Bernhard Reutner-Fischer
2013-07-29 13:34 ` Laszlo Papp
2013-07-29 15:42 ` Bernhard Reutner-Fischer
2013-07-30 15:55 ` Laszlo Papp
2013-07-30 16:10 ` Phil Blundell
2013-07-30 16:21 ` Burton, Ross
2013-07-31 11:13 ` Laszlo Papp
2013-07-29 10:42 ` Burton, Ross
2013-07-29 10:44 ` Laszlo Papp
2013-07-29 11:09 ` Marcin Juszkiewicz
2013-07-29 11:14 ` Laszlo Papp
2013-07-31 22:36 ` Khem Raj
[not found] ` <CAOMwXhMPmoFo+bYz9NAijJevWvizNFm0rsbVn1fPNHCS4Kf7yw@mail.gmail.com>
2013-08-13 7:32 ` Laszlo Papp
2013-08-13 7:33 ` Laszlo Papp
2013-08-13 9:48 ` Burton, Ross
2013-08-13 9:52 ` Laszlo Papp
2013-08-13 9:55 ` Laszlo Papp
2013-08-13 9:58 ` Burton, Ross
2013-08-13 10:00 ` Laszlo Papp
2013-08-13 10:17 ` Phil Blundell [this message]
2013-08-13 10:14 ` Jack Mitchell
2013-08-13 10:19 ` Laszlo Papp
2013-08-13 10:35 ` Jack Mitchell
2013-08-13 10:39 ` Laszlo Papp
2013-08-14 8:35 ` Fathi Boudra
-- strict thread matches above, loose matches on Subject: below --
2013-07-28 22:31 Laszlo Papp
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=1376389073.10241.1.camel@phil-desktop.brightsign \
--to=pb@pbcl.net \
--cc=lpapp@kde.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