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 E292BE017B0 for ; Wed, 30 Oct 2013 06:05:11 -0700 (PDT) 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 r9UD59um015459 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 30 Oct 2013 06:05:09 -0700 (PDT) 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.347.0; Wed, 30 Oct 2013 06:05:08 -0700 Message-ID: <527103F6.3080806@windriver.com> Date: Wed, 30 Oct 2013 09:04:54 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Diego Sueiro , Andrea Adami References: <525FE3C9.3070003@windriver.com> <5260BDA6.4020807@windriver.com> <5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com> <52686723.4080305@windriver.com> <526B18BC.5050302@alphalem.com> <526ECFF3.4060207@windriver.com> In-Reply-To: Cc: "yocto@yoctoproject.org" Subject: Re: Custom defconfig is not used X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Oct 2013 13:05:12 -0000 Content-Type: multipart/alternative; boundary="------------090000020306000103090106" --------------090000020306000103090106 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 13-10-29 11:31 AM, Diego Sueiro wrote: > Bruce, > > I've created new build setup with this configuration: > > BB_VERSION = "1.18.0" > BUILD_SYS = "x86_64-linux" > NATIVELSBSTRING = "Ubuntu-12.10" > TARGET_SYS = "arm-poky-linux-gnueabi" > MACHINE = "beaglebone" > DISTRO = "poky" > DISTRO_VERSION = "1.4.2" > TUNE_FEATURES = "armv7a vfp neon" > TARGET_FPU = "vfp-neon" > meta > meta-yocto > meta-yocto-bsp = "dylan:4e399f08d596197859214fdb3b06403b87bf8789" > meta-oe = "dylan:a108b2203a997634f87ac687e81712badaf3c546" > common-bsp = "dylan:7fdf9c670a10c5031a2d5555c15c45e453de8c21" > meta-mine = "dylan:4e399f08d596197859214fdb3b06403b87bf8789" > > common-bsp comes from meta-beagleboard. > meta-oe needed to be added because of machine_kernel_pr.bbclass. FYI: I've created this exactly environment on my builder. I'll follow up shortly with the results of the two scenarios. Honestly, I hope it breaks .. that'll make it much easier to debug :) Bruce > > bblayers.conf: > > LCONF_VERSION = "6" > BBPATH = "${TOPDIR}" > BBFILES ?= "" > BBLAYERS ?= " \ > ${TOPDIR}/meta \ > ${TOPDIR}/meta-yocto \ > ${TOPDIR}/meta-yocto-bsp \ > ${TOPDIR}/meta-openembedded/meta-oe \ > ${TOPDIR}/meta-beagleboard/common-bsp \ > ${TOPDIR}/meta-mine \ > " > > meta-mine: > > conf/layer.conf: > > BBPATH .= ":${LAYERDIR}" > BBFILES += "${LAYERDIR}/recipes*/*/*.bb > ${LAYERDIR}/recipes*/*/*.bbappend" > BBFILE_COLLECTIONS += "my-layer" > BBFILE_PATTERN_my-layer := "^${LAYERDIR}/" > BBFILE_PRIORITY_my-layer = "10" > > recipes-kernel/linux/linux-mainline_3.8.bbappend (scenario 1): > > FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.8:" > COMPATIBLE_MACHINE_beaglebone = "(beaglebone)" > SRC_URI += " file://defconfig \ > " > > recipes-kernel/linux/linux-mainline-3.8/defconfig (scenario 1): > > http://pastebin.com/qd8B3C5K > > > recipes-kernel/linux/linux-mainline_3.8.bbappend (scenario 2): > > FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.8:" > inherit kernel > require recipes-kernel/linux/linux-yocto.inc > COMPATIBLE_MACHINE_beaglebone = "(beaglebone)" > SRC_URI += " file://config-addons.cfg \ > " > > recipes-kernel/linux/linux-mainline-3.8/config-addons.cfg > (scenario 2): > > CONFIG_WATCHDOG_NOWAYOUT=y > > CONFIG_NTFS_FS=y > CONFIG_NTFS_RW=y > > > > Results: > > * Scenario 1: Full defconfig replacement > > ${WORKDIR}/defconfig comes from meta-beagleboard instead of meta-mine > > ${S}/.config comes from meta-beagleboard instead of meta-mine > > * Scenario 2: Config fragments > > "bitbake linux-mainline" got stuck on do_patch > > log.do_patch: > > DEBUG: Executing shell function do_patch > > WARNING: no meta data branch found ... > > Switched to branch 'linux-3.8.y' > > [INFO] validating against known patches > (beaglebone-standard-meta) > > > > Regards, > > -- > *dS > Diego Sueiro > > /*long live rock 'n roll*/ > > > 2013/10/29 Diego Sueiro > > > 2013/10/29 Andrea Adami > > > I'll jump in one more time... > > Have you tried putting defconfig and patch under subdir? > > recipes-kernel/linux/linux-yocto-3.2/ > defconfig > my-own.patch > > I've recently added two similar entries for 3.10 and it works. > Afaik it was impossible to put a common patch under > /linux-yocto-.3.2 > at the time. > > > Andrea, > > I did it before and not worked. > I'll do it again just to make sure. > > > Regards, > > -- > *dS > Diego Sueiro > > /*long live rock 'n roll*/ > > > 2013/10/29 Andrea Adami > > > On Tue, Oct 29, 2013 at 11:33 AM, Diego Sueiro > > wrote: > > > > 2013/10/28 Bruce Ashfield > > >> > >> I'm using dylan for my yocto checkout (not oe-core > standalone, since > >> this is a yocto list/question), > > > > I thought that opemenbedded-core and poky were sharing the > same core > > components, classes and functions. > > > >> > >> My build shows: > >> > >> meta > >> meta-yocto > >> meta-yocto-bsp = > "dylan:3dc4505f0e744177ae4ddff1e1ce8b31b95dfaa6" > >> meta-ti = > "master:c14c386946e1ea341faeea292580e37d538d645d" > >> meta-alphalem = > "master:a5c0e8ff51297a4090cd47d669b4fc9c94696908" > >> meta-alphalem-bsp = > "master:56086e4dc618e975c9a46491793041f0d18e47a2" > >> > >> Mike indicated that he was using dylan for meta-ti, but > that doesn't > >> make a difference either, since for our purposed. It's > kernel.bbclass > >> and the yocto kernel processing that matters. > > > > I'll build a setup with yocto (dylan), meta-beagleboard > (dylan) and > > meta-mine to check if I can reproduce the issues. > > > >> > >> In meta-alphalem-bsp, I have linux-mainline_3.2.bbappend, > with the > >> following content: > >> > >> > cat linux-mainline_3.2.bbappend > >> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.2:" > >> > >> inherit kernel > >> require recipes-kernel/linux/linux-yocto.inc > >> > >> COMPATIBLE_MACHINE = "(beagleboard)" > >> > >> SRC_URI_append = " file://defconfig" > >> SRC_URI_append = " file://my_frag.cfg" > >> > >> And I added a fragment which has: > >> > >> > cat my_frag.cfg > >> CONFIG_WATCHDOG_NOWAYOUT=y > >> CONFIG_NTFS_FS=y > >> CONFIG_NTFS_RW=y > >> > >> When both are applied to the kernel build, we should see > CONFIG_NTFS_FS > >> transition from =m to =y: > >> > >> > grep CONFIG_NTFS_FS * > >> defconfig:CONFIG_NTFS_FS=m > >> my_frag.cfg:CONFIG_NTFS_FS=y > >> > >> After invoking linux-mainline's configure task, I see the > following: > >> > >> > grep CONFIG_NTFS_FS linux-beagleboard-standard-build/.config > >> CONFIG_NTFS_FS=y > >> > >> And other elements of the defconfig and fragment are > properly applied > >> to the configuration phase. > >> > >> I'm also seeing good results on master, which means that > I'm at a > >> standstill to reproduce any problems. > >> > >> Diego: can you confirm for me what triggers you are seeing > that shows > >> the defconfig and fragment are not used. I assume the > config options > >> are not present, but I just want to be sure. > > > > For the full defconfig replacement after doing a > do_configure I've checked > > .config on ${S} and it did not included my CONFIGS. > > For config fragment it got stuck on do_patch task. > > > > > > > > Regards, > > > > -- > > *dS > > Diego Sueiro > > > > /*long live rock 'n roll*/ > > > > _______________________________________________ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > > > I'll jump in one more time... > > Have you tried putting defconfig and patch under subdir? > > recipes-kernel/linux/linux-yocto-3.2/ > defconfig > my-own.patch > > I've recently added two similar entries for 3.10 and it works. > Afaik it was impossible to put a common patch under > /linux-yocto-.3.2 > at the time. > > Regards > > Andrea > > > --------------090000020306000103090106 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit
On 13-10-29 11:31 AM, Diego Sueiro wrote:
Bruce,

I've created new build setup with this configuration:
BB_VERSION        = "1.18.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-12.10"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "beaglebone"
DISTRO            = "poky"
DISTRO_VERSION    = "1.4.2"
TUNE_FEATURES     = "armv7a vfp neon"
TARGET_FPU        = "vfp-neon"
meta              
meta-yocto        
meta-yocto-bsp    = "dylan:4e399f08d596197859214fdb3b06403b87bf8789"
meta-oe           = "dylan:a108b2203a997634f87ac687e81712badaf3c546"
common-bsp        = "dylan:7fdf9c670a10c5031a2d5555c15c45e453de8c21"
meta-mine         = "dylan:4e399f08d596197859214fdb3b06403b87bf8789"

common-bsp comes from meta-beagleboard.
meta-oe needed to be added because of machine_kernel_pr.bbclass.

FYI: I've created this exactly environment on my builder. I'll follow up
shortly with the results of the two scenarios.

Honestly, I hope it breaks .. that'll make it much easier to debug :)

Bruce


bblayers.conf:
LCONF_VERSION = "6"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
  ${TOPDIR}/meta \
  ${TOPDIR}/meta-yocto \
  ${TOPDIR}/meta-yocto-bsp \
  ${TOPDIR}/meta-openembedded/meta-oe \
  ${TOPDIR}/meta-beagleboard/common-bsp \
  ${TOPDIR}/meta-mine \
  "

meta-mine:
conf/layer.conf:
BBPATH .= ":${LAYERDIR}"
BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
BBFILE_COLLECTIONS += "my-layer"
BBFILE_PATTERN_my-layer := "^${LAYERDIR}/"
BBFILE_PRIORITY_my-layer = "10"

recipes-kernel/linux/linux-mainline_3.8.bbappend (scenario 1):
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.8:"
COMPATIBLE_MACHINE_beaglebone = "(beaglebone)"
SRC_URI += " file://defconfig \
             "
recipes-kernel/linux/linux-mainline-3.8/defconfig (scenario 1):
http://pastebin.com/qd8B3C5K

recipes-kernel/linux/linux-mainline_3.8.bbappend (scenario 2):
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.8:"
inherit kernel
require recipes-kernel/linux/linux-yocto.inc
COMPATIBLE_MACHINE_beaglebone = "(beaglebone)"
SRC_URI += " file://config-addons.cfg \
             "
recipes-kernel/linux/linux-mainline-3.8/config-addons.cfg (scenario 2):
CONFIG_WATCHDOG_NOWAYOUT=y
CONFIG_NTFS_FS=y
CONFIG_NTFS_RW=y


Results:
  • Scenario 1: Full defconfig replacement
${WORKDIR}/defconfig comes from meta-beagleboard instead of meta-mine
${S}/.config comes from meta-beagleboard instead of meta-mine
  • Scenario 2: Config fragments
"bitbake linux-mainline" got stuck on do_patch
log.do_patch:
DEBUG: Executing shell function do_patch
WARNING: no meta data branch found ...
Switched to branch 'linux-3.8.y'
[INFO] validating against known patches  (beaglebone-standard-meta)


Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/


2013/10/29 Diego Sueiro <diego.sueiro@gmail.com>
2013/10/29 Andrea Adami <andrea.adami@gmail.com>
I'll jump in one more time...

Have you tried putting defconfig and patch under <machine> subdir?

recipes-kernel/linux/linux-yocto-3.2/<machine>
defconfig
my-own.patch

I've recently added two similar entries for 3.10 and it works.
Afaik it was impossible to put a common patch under /linux-yocto-.3.2
at the time.

Andrea,

I did it before and not worked.
I'll do it again just to make sure.


Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/


2013/10/29 Andrea Adami <andrea.adami@gmail.com>
On Tue, Oct 29, 2013 at 11:33 AM, Diego Sueiro <diego.sueiro@gmail.com> wrote:
>
> 2013/10/28 Bruce Ashfield <bruce.ashfield@windriver.com>
>>
>> I'm using dylan for my yocto checkout (not oe-core standalone, since
>> this is a yocto list/question),
>
> I thought that opemenbedded-core and poky were sharing the same core
> components, classes and functions.
>
>>
>> My build shows:
>>
>> meta
>> meta-yocto
>> meta-yocto-bsp    = "dylan:3dc4505f0e744177ae4ddff1e1ce8b31b95dfaa6"
>> meta-ti           = "master:c14c386946e1ea341faeea292580e37d538d645d"
>> meta-alphalem     = "master:a5c0e8ff51297a4090cd47d669b4fc9c94696908"
>> meta-alphalem-bsp = "master:56086e4dc618e975c9a46491793041f0d18e47a2"
>>
>> Mike indicated that he was using dylan for meta-ti, but that doesn't
>> make a difference either, since for our purposed. It's kernel.bbclass
>> and the yocto kernel processing that matters.
>
> I'll build a setup with yocto (dylan), meta-beagleboard (dylan) and
> meta-mine to check if I can reproduce the issues.
>
>>
>> In meta-alphalem-bsp, I have linux-mainline_3.2.bbappend, with the
>> following content:
>>
>> > cat linux-mainline_3.2.bbappend
>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.2:"
>>
>> inherit kernel
>> require recipes-kernel/linux/linux-yocto.inc
>>
>> COMPATIBLE_MACHINE = "(beagleboard)"
>>
>> SRC_URI_append = " file://defconfig"
>> SRC_URI_append = " file://my_frag.cfg"
>>
>> And I added a fragment which has:
>>
>> > cat my_frag.cfg
>> CONFIG_WATCHDOG_NOWAYOUT=y
>> CONFIG_NTFS_FS=y
>> CONFIG_NTFS_RW=y
>>
>> When both are applied to the kernel build, we should see CONFIG_NTFS_FS
>> transition from =m to =y:
>>
>> > grep CONFIG_NTFS_FS *
>> defconfig:CONFIG_NTFS_FS=m
>> my_frag.cfg:CONFIG_NTFS_FS=y
>>
>> After invoking linux-mainline's configure task, I see the following:
>>
>> > grep CONFIG_NTFS_FS linux-beagleboard-standard-build/.config
>> CONFIG_NTFS_FS=y
>>
>> And other elements of the defconfig and fragment are properly applied
>> to the configuration phase.
>>
>> I'm also seeing good results on master, which means that I'm at a
>> standstill to reproduce any problems.
>>
>> Diego: can you confirm for me what triggers you are seeing that shows
>> the defconfig and fragment are not used. I assume the config options
>> are not present, but I just want to be sure.
>
> For the full defconfig replacement after doing a do_configure I've checked
> .config on ${S} and it did not included my CONFIGS.
> For config fragment it got stuck on do_patch task.
>
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

I'll jump in one more time...

Have you tried putting defconfig and patch under <machine> subdir?

recipes-kernel/linux/linux-yocto-3.2/<machine>
defconfig
my-own.patch

I've recently added two similar entries for 3.10 and it works.
Afaik it was impossible to put a common patch under /linux-yocto-.3.2
at the time.

Regards

Andrea



--------------090000020306000103090106--