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 51286E003D6 for ; Wed, 28 Nov 2012 06:27:29 -0800 (PST) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.14.5/8.14.3) with ESMTP id qASERNPt015041 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 28 Nov 2012 06:27:23 -0800 (PST) Received: from [128.224.146.67] (128.224.146.67) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.2.318.4; Wed, 28 Nov 2012 06:27:22 -0800 Message-ID: <50B61F47.5050104@windriver.com> Date: Wed, 28 Nov 2012 09:27:19 -0500 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2 MIME-Version: 1.0 To: Yu Pan References: <50B4DB1F.2070904@windriver.com> In-Reply-To: Cc: yocto@yoctoproject.org Subject: Re: Preempt-rt kernel build for beagleboard 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, 28 Nov 2012 14:27:34 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 12-11-28 01:07 AM, Yu Pan wrote: > Hi Bruce, > > Thanks for commenting :-) > > You shouldn't have needed to do this part, since the board already has > a preempt-rt BSP description: > > http://git.yoctoproject.org/__cgit/cgit.cgi/linux-yocto-3.4/__tree/meta/cfg/kernel-cache/__bsp/beagleboard/beagleboard-__preempt-rt.scc?h=meta > > > And when you build the linux-yocto-rt kernel with that board, that > description should be found, and it enables all the base options > already. > > If you look in your build, what does the file 'linux/meta/top_tgt' > contain ? > > > This was what puzzles me as well. I thought bitbake should pickup what It's the kern-tools that find the .scc file based on information passed in from bitbake, in this case, the board name and the kernel type. > is specified in beagleboard-preempt-rt.scc to produce the .config in the > kernel build directory. But it did not, at least for the PREEMPT part. > Below is the PREEMPT related configs in the .config without manually > doing the menuconfig: > > # CONFIG_PREEMPT_RCU is not set > CONFIG_PREEMPT_NONE=y > # CONFIG_PREEMPT_VOLUNTARY is not set > # CONFIG_PREEMPT__LL is not set > # CONFIG_PREEMPT_RTB is not set > # CONFIG_PREEMPT_RT_FULL is not set > > Follow your pointer, I checked linux/meta/top_tgt, it indeed points to > meta/cfg/kernel-cache/bsp/beagleboard/beagleboard-preempt-rt.scc, which And this means that the right one was found. > includes ktypes/preempt-rt (why not ktypes/preempt-rt.scc?). In > ktypes/preempt-rt.cfg (included by ktypes/preempt-rt.scc), > CONFIG_PREEMPT_RT_FULL=y is there. So why not this configuration > fragment not picked up in the final .config? It should always make it into the final .config, are you working on master ? I'll run my own tests here to see if I can reproduce the failure. Master should also have a better Kconfig audit report, are you seeing any messages about Kconfig options being dropped ? Cheers, Bruce > > Cheers > Pan Yu