<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 13-10-29 11:31 AM, Diego Sueiro
wrote:<br>
</div>
<blockquote
cite="mid:CAMCfZKHaRRVcx5YG+7DJ10-4DE_n9titOG7+aB3R+4H8iZjGvw@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div dir="ltr">Bruce,
<div><br>
</div>
<div>I've created new build setup with this configuration:<br>
</div>
<div>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div>
<div>BB_VERSION = "1.18.0"</div>
<div>BUILD_SYS = "x86_64-linux"</div>
<div>NATIVELSBSTRING = "Ubuntu-12.10"</div>
<div>TARGET_SYS = "arm-poky-linux-gnueabi"</div>
<div>MACHINE = "beaglebone"</div>
<div>DISTRO = "poky"</div>
<div>DISTRO_VERSION = "1.4.2"</div>
<div>TUNE_FEATURES = "armv7a vfp neon"</div>
<div>TARGET_FPU = "vfp-neon"</div>
<div>meta </div>
<div>meta-yocto </div>
<div>meta-yocto-bsp =
"dylan:4e399f08d596197859214fdb3b06403b87bf8789"</div>
<div>meta-oe =
"dylan:a108b2203a997634f87ac687e81712badaf3c546"</div>
<div>common-bsp =
"dylan:7fdf9c670a10c5031a2d5555c15c45e453de8c21"</div>
<div>meta-mine =
"dylan:4e399f08d596197859214fdb3b06403b87bf8789"</div>
</div>
<div><br>
</div>
</blockquote>
</div>
<div>common-bsp comes from meta-beagleboard.</div>
<div>meta-oe needed to be added because
of machine_kernel_pr.bbclass.<br>
</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">bblayers.conf:</div>
<div class="gmail_extra">
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div class="gmail_extra">
<div class="gmail_extra">LCONF_VERSION = "6"<br>
</div>
<div class="gmail_extra">BBPATH = "${TOPDIR}"<br>
</div>
<div class="gmail_extra">BBFILES ?= ""</div>
<div class="gmail_extra">BBLAYERS ?= " \<br>
</div>
<div class="gmail_extra">
${TOPDIR}/meta \</div>
<div class="gmail_extra"> ${TOPDIR}/meta-yocto \</div>
<div class="gmail_extra"> ${TOPDIR}/meta-yocto-bsp \</div>
<div class="gmail_extra">
${TOPDIR}/meta-openembedded/meta-oe \</div>
<div class="gmail_extra">
${TOPDIR}/meta-beagleboard/common-bsp \</div>
<div class="gmail_extra"> ${TOPDIR}/meta-mine \</div>
<div class="gmail_extra"> "</div>
<div><br>
</div>
</div>
</blockquote>
</div>
<div class="gmail_extra">meta-mine:<br>
</div>
<div class="gmail_extra">
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div class="gmail_extra">conf/layer.conf:</div>
</blockquote>
</div>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div class="gmail_extra">
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div class="gmail_extra">
<div class="gmail_extra">BBPATH .= ":${LAYERDIR}"<br>
</div>
<div class="gmail_extra">BBFILES +=
"${LAYERDIR}/recipes*/*/*.bb
${LAYERDIR}/recipes*/*/*.bbappend"<br>
</div>
<div class="gmail_extra">BBFILE_COLLECTIONS +=
"my-layer"<br>
</div>
<div class="gmail_extra">BBFILE_PATTERN_my-layer :=
"^${LAYERDIR}/"</div>
<div class="gmail_extra">BBFILE_PRIORITY_my-layer = "10"</div>
<div class="gmail_extra"><br>
</div>
</div>
</blockquote>
</div>
</blockquote>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div class="gmail_extra">recipes-kernel/linux/linux-mainline_3.8.bbappend
(scenario 1):<br>
</div>
</blockquote>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div class="gmail_extra" style="">
<div class="gmail_extra">FILESEXTRAPATHS_prepend :=
"${THISDIR}/${PN}-3.8:"</div>
<div class="gmail_extra">COMPATIBLE_MACHINE_beaglebone =
"(beaglebone)"<br>
</div>
<div class="gmail_extra">SRC_URI += " <a class="moz-txt-link-freetext" href="file://defconfig">file://defconfig</a> \<br>
</div>
<div class="gmail_extra"> "</div>
</div>
</blockquote>
</blockquote>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">recipes-kernel/linux/linux-mainline-3.8/defconfig
(scenario 1):<br>
</blockquote>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px"><a moz-do-not-send="true"
href="http://pastebin.com/qd8B3C5K">http://pastebin.com/qd8B3C5K</a><br>
</blockquote>
</blockquote>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">recipes-kernel/linux/linux-mainline_3.8.bbappend
(scenario 2):<br>
</div>
</blockquote>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div class="gmail_extra">
<div class="gmail_extra">FILESEXTRAPATHS_prepend :=
"${THISDIR}/${PN}-3.8:"</div>
<div class="gmail_extra">inherit kernel<br>
</div>
<div class="gmail_extra">require
recipes-kernel/linux/linux-yocto.inc</div>
<div class="gmail_extra">COMPATIBLE_MACHINE_beaglebone =
"(beaglebone)"<br>
</div>
<div class="gmail_extra">SRC_URI += "
<a class="moz-txt-link-freetext" href="file://config-addons.cfg">file://config-addons.cfg</a> \<br>
</div>
<div class="gmail_extra"> "</div>
</div>
</blockquote>
</blockquote>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
recipes-kernel/linux/linux-mainline-3.8/config-addons.cfg
(scenario 2):</blockquote>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
</blockquote>
</blockquote>
</blockquote>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">CONFIG_WATCHDOG_NOWAYOUT=y<br>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
</blockquote>
CONFIG_NTFS_FS=y<br>
CONFIG_NTFS_RW=y</blockquote>
</blockquote>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Results:</div>
<div class="gmail_extra">
<div>
<ul style="">
<li style="">Scenario 1: Full defconfig replacement</li>
</ul>
</div>
</div>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div class="gmail_extra">
<div style="">${WORKDIR}/defconfig comes from
meta-beagleboard instead of meta-mine<br>
</div>
</div>
</blockquote>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div class="gmail_extra">
<div style="">${S}/.config comes from meta-beagleboard
instead of meta-mine</div>
</div>
</blockquote>
</div>
</blockquote>
<br>
I've confirmed this behaviour on dylan when I exactly reproduced<br>
your configuration. The more interesting one is scenario 2, so I'm<br>
trying it out, before looking at #1 in more detail.<br>
<br>
Bruce<br>
<br>
<blockquote
cite="mid:CAMCfZKHaRRVcx5YG+7DJ10-4DE_n9titOG7+aB3R+4H8iZjGvw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<ul style="">
<li style="">Scenario 2: Config fragments</li>
</ul>
</div>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div class="gmail_extra">"bitbake linux-mainline" got stuck on
do_patch</div>
</blockquote>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div class="gmail_extra">log.do_patch:</div>
</blockquote>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div class="gmail_extra">
DEBUG: Executing shell function do_patch<br>
</div>
</blockquote>
</blockquote>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div class="gmail_extra">
<div class="gmail_extra" style="">WARNING: no meta data
branch found ...</div>
</div>
</blockquote>
</blockquote>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div class="gmail_extra">
<div class="gmail_extra" style="">Switched to branch
'linux-3.8.y'</div>
</div>
</blockquote>
</blockquote>
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<blockquote style="margin:0px 0px 0px
40px;border:none;padding:0px">
<div class="gmail_extra">
<div class="gmail_extra" style="">[INFO] validating
against known patches (beaglebone-standard-meta)</div>
</div>
</blockquote>
</blockquote>
<div class="gmail_extra">
<div>
<br>
</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div dir="ltr">
<div>Regards,</div>
<div><br>
</div>
--<br>
*dS<br>
Diego Sueiro<br>
<br>
/*long live rock 'n roll*/<br>
</div>
</div>
<br>
<br>
<div class="gmail_quote">2013/10/29 Diego Sueiro <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:diego.sueiro@gmail.com" target="_blank">diego.sueiro@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">
<div class="gmail_extra"
style="font-family:arial,sans-serif;font-size:13px">
<div>
<div>
<div class="gmail_quote">2013/10/29 Andrea Adami <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:andrea.adami@gmail.com"
target="_blank">andrea.adami@gmail.com</a>></span><br>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="overflow:hidden">I'll jump in one
more time...<br>
<br>
Have you tried putting defconfig and patch
under <machine> subdir?<br>
<br>
recipes-kernel/linux/linux-yocto-3.2/<machine><br>
defconfig<br>
my-own.patch<br>
<br>
I've recently added two similar entries for
3.10 and it works.<br>
Afaik it was impossible to put a common
patch under /linux-yocto-.3.2<br>
at the time.</div>
</blockquote>
</div>
<br>
</div>
</div>
Andrea,</div>
<div>
<div class="gmail_extra"
style="font-family:arial,sans-serif;font-size:13px">
<br>
</div>
<div class="gmail_extra"
style="font-family:arial,sans-serif;font-size:13px">
I did it before and not worked.</div>
<div class="gmail_extra"
style="font-family:arial,sans-serif;font-size:13px">I'll
do it again just to make sure.</div>
</div>
<div style="font-family:arial,sans-serif;font-size:13px">
<div><img moz-do-not-send="true"
src="https://mail.google.com/mail/u/0/images/cleardot.gif"
style="max-width: 100%;"></div>
</div>
<div>
<div
style="font-family:arial,sans-serif;font-size:13px">
<div class="gmail_extra">
<br>
<br clear="all">
<div>
<div dir="ltr">
<div>Regards,</div>
<div><br>
</div>
--<br>
*dS<br>
Diego Sueiro<br>
<br>
/*long live rock 'n roll*/</div>
</div>
</div>
</div>
</div>
<div>
<div>
<div class="gmail_extra">
<div>
<div dir="ltr">
<br>
</div>
</div>
<br>
<div class="gmail_quote">2013/10/29 Andrea Adami <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:andrea.adami@gmail.com"
target="_blank">andrea.adami@gmail.com</a>></span><br>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>
<div>On Tue, Oct 29, 2013 at 11:33 AM, Diego
Sueiro <<a moz-do-not-send="true"
href="mailto:diego.sueiro@gmail.com"
target="_blank">diego.sueiro@gmail.com</a>>
wrote:<br>
><br>
> 2013/10/28 Bruce Ashfield <<a
moz-do-not-send="true"
href="mailto:bruce.ashfield@windriver.com"
target="_blank">bruce.ashfield@windriver.com</a>><br>
>><br>
>> I'm using dylan for my yocto
checkout (not oe-core standalone, since<br>
>> this is a yocto list/question),<br>
><br>
> I thought that opemenbedded-core and
poky were sharing the same core<br>
> components, classes and functions.<br>
><br>
>><br>
>> My build shows:<br>
>><br>
>> meta<br>
>> meta-yocto<br>
>> meta-yocto-bsp =
"dylan:3dc4505f0e744177ae4ddff1e1ce8b31b95dfaa6"<br>
>> meta-ti =
"master:c14c386946e1ea341faeea292580e37d538d645d"<br>
>> meta-alphalem =
"master:a5c0e8ff51297a4090cd47d669b4fc9c94696908"<br>
>> meta-alphalem-bsp =
"master:56086e4dc618e975c9a46491793041f0d18e47a2"<br>
>><br>
>> Mike indicated that he was using
dylan for meta-ti, but that doesn't<br>
>> make a difference either, since
for our purposed. It's kernel.bbclass<br>
>> and the yocto kernel processing
that matters.<br>
><br>
> I'll build a setup with yocto
(dylan), meta-beagleboard (dylan) and<br>
> meta-mine to check if I can reproduce
the issues.<br>
><br>
>><br>
>> In meta-alphalem-bsp, I have
linux-mainline_3.2.bbappend, with the<br>
>> following content:<br>
>><br>
>> > cat
linux-mainline_3.2.bbappend<br>
>> FILESEXTRAPATHS_prepend :=
"${THISDIR}/${PN}-3.2:"<br>
>><br>
>> inherit kernel<br>
>> require
recipes-kernel/linux/linux-yocto.inc<br>
>><br>
>> COMPATIBLE_MACHINE =
"(beagleboard)"<br>
>><br>
>> SRC_URI_append = <a class="moz-txt-link-rfc2396E" href="file://defconfig">"
file://defconfig"</a><br>
>> SRC_URI_append = <a class="moz-txt-link-rfc2396E" href="file://my_frag.cfg">"
file://my_frag.cfg"</a><br>
>><br>
>> And I added a fragment which has:<br>
>><br>
>> > cat my_frag.cfg<br>
>> CONFIG_WATCHDOG_NOWAYOUT=y<br>
>> CONFIG_NTFS_FS=y<br>
>> CONFIG_NTFS_RW=y<br>
>><br>
>> When both are applied to the
kernel build, we should see CONFIG_NTFS_FS<br>
>> transition from =m to =y:<br>
>><br>
>> > grep CONFIG_NTFS_FS *<br>
>> defconfig:CONFIG_NTFS_FS=m<br>
>> my_frag.cfg:CONFIG_NTFS_FS=y<br>
>><br>
>> After invoking linux-mainline's
configure task, I see the following:<br>
>><br>
>> > grep CONFIG_NTFS_FS
linux-beagleboard-standard-build/.config<br>
>> CONFIG_NTFS_FS=y<br>
>><br>
>> And other elements of the
defconfig and fragment are properly
applied<br>
>> to the configuration phase.<br>
>><br>
>> I'm also seeing good results on
master, which means that I'm at a<br>
>> standstill to reproduce any
problems.<br>
>><br>
>> Diego: can you confirm for me
what triggers you are seeing that shows<br>
>> the defconfig and fragment are
not used. I assume the config options<br>
>> are not present, but I just want
to be sure.<br>
><br>
> For the full defconfig replacement
after doing a do_configure I've checked<br>
> .config on ${S} and it did not
included my CONFIGS.<br>
> For config fragment it got stuck on
do_patch task.<br>
><br>
><br>
><br>
> Regards,<br>
><br>
> --<br>
> *dS<br>
> Diego Sueiro<br>
><br>
> /*long live rock 'n roll*/<br>
><br>
</div>
</div>
<div>>
_______________________________________________<br>
> yocto mailing list<br>
> <a moz-do-not-send="true"
href="mailto:yocto@yoctoproject.org"
target="_blank">yocto@yoctoproject.org</a><br>
> <a moz-do-not-send="true"
href="https://lists.yoctoproject.org/listinfo/yocto"
target="_blank">https://lists.yoctoproject.org/listinfo/yocto</a><br>
><br>
<br>
</div>
I'll jump in one more time...<br>
<br>
Have you tried putting defconfig and patch
under <machine> subdir?<br>
<br>
recipes-kernel/linux/linux-yocto-3.2/<machine><br>
defconfig<br>
my-own.patch<br>
<br>
I've recently added two similar entries for
3.10 and it works.<br>
Afaik it was impossible to put a common patch
under /linux-yocto-.3.2<br>
at the time.<br>
<br>
Regards<br>
<span><font color="#888888"><br>
Andrea<br>
</font></span></blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>