From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hetzner.pbcl.net (mail.pbcl.net [88.198.119.4]) by mail.openembedded.org (Postfix) with ESMTP id 9359560664 for ; Tue, 13 Aug 2013 10:18:04 +0000 (UTC) Received: from cpc6-cmbg17-2-0-cust487.5-4.cable.virginmedia.com ([86.30.57.232] helo=[172.30.1.45]) by hetzner.pbcl.net with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1V9Bfs-00076T-1V; Tue, 13 Aug 2013 12:18:00 +0200 Message-ID: <1376389073.10241.1.camel@phil-desktop.brightsign> From: Phil Blundell To: Laszlo Papp Date: Tue, 13 Aug 2013 11:17:53 +0100 In-Reply-To: References: <1375082184-14871-1-git-send-email-lpapp@kde.org> <10585858-000F-43F4-80AF-5622D08A91D7@gmail.com> X-Mailer: Evolution 3.4.4-1 Mime-Version: 1.0 Cc: openembedded-core Subject: Re: [PATCH] busybox-1.21.1/defconfig: disable rfkill X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Aug 2013 10:18:05 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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 > wrote: > On 13 August 2013 10:52, Laszlo Papp 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