From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 28F0EE006AB for ; Wed, 17 Aug 2011 08:18:11 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail.windriver.com (8.14.3/8.14.3) with ESMTP id p7HFI8Pk019889 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 17 Aug 2011 08:18:08 -0700 (PDT) Received: from [128.224.147.214] (128.224.147.214) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.1.255.0; Wed, 17 Aug 2011 08:18:08 -0700 Message-ID: <4E4BDBAE.1060402@windriver.com> Date: Wed, 17 Aug 2011 11:18:06 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11 ThunderBrowse/3.8 MIME-Version: 1.0 To: Chris Tapp References: <56EF2FAC-D4B5-4EC7-ADC1-6AE0848A51FD@keylevel.com> <4E45D1F2.6040902@windriver.com> <84AA8A6F-7556-4965-93ED-BDD4322047B3@keylevel.com> In-Reply-To: <84AA8A6F-7556-4965-93ED-BDD4322047B3@keylevel.com> Cc: yocto@yoctoproject.org Subject: Re: Configuring a layer to support multiple targets X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2011 15:18:11 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 11-08-17 03:59 AM, Chris Tapp wrote: > On 13 Aug 2011, at 02:22, Bruce Ashfield wrote: > >> What's your yocto release / base kernel ? IF you happen to >> be using linux-yocto there are several ways to avoid using >> defconfigs at all, and share your common base of kernel >> configuration items. > > Plan is to move to linux-yocto (currently using wrs). How do I configure > it without using a defconfig? I depends on how you host your BSP, and the release. In yocto 1.1, there's new functionality that makes it easier to graft a BSP onto the tree without needing to have the BSP merged somewhere. But to configure and work without a defconfig, you simply need a BSP that branches from yocto/standard/base. Even the autogenerated descriptions in 1.0 will automatically include the standard kernel configs and settings and pass them to your BSP. Once this is in place, you simply need a config fragment (a .cfg file) for your board that adds/modifies the base configuration. > > Also, is it possible to use a .config rather than a defconfig? I've got > a lot of stuff turned off to reduce the size of the kernel, but a > defconfig doesn't quite do. For example, if I have > > # CONFIG_USB_SERIAL is not set > > in a defconfig, then this gets in to the .config at build time. However, > this doesn't disable any dependencies that are enabled in linux-wrs. > This means that modules for the likes of the ftdi and pl2303 USB serial > devices are still included in the kernel image. > > The use of a complete .config would stop this. In this sense, the defconfig is simply a name to trigger specific processing. Just capture and call your .config 'defconfig' and you'll get a translation of those settings into the build. Bruce > > > Chris Tapp > > opensource@keylevel.com > www.keylevel.com > > > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto