From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <diego.sueiro@gmail.com>
Received: from mail-ie0-f174.google.com (mail-ie0-f174.google.com
	[209.85.223.174])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 3D0E3E01706
	for <yocto@yoctoproject.org>; Tue, 15 Oct 2013 14:08:07 -0700 (PDT)
Received: by mail-ie0-f174.google.com with SMTP id qd12so11129682ieb.5
	for <yocto@yoctoproject.org>; Tue, 15 Oct 2013 14:08:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:from:date:message-id:subject:to:content-type;
	bh=lA5CQSrzwh8db6NGVfMSgcD0iY5kfzUnBMFGl89UPY0=;
	b=lGCtL3enjaorwZEv0VvT/Ou9aPaAjSXCeGAaEfEAEhMLFlMNgqnaHUY8scytLfonvD
	joLpkNyZczdzLx7Q0LI9SyhpUMDYMnjJ0On9n90BWzxxXNvFT94Td9++6nMLE1vw0lW0
	ek2Q/2ccI+7GVCenznq6+/zTRT4ITWeJ83AX0QAXdivJwcBTbAZnay+ss/D+YVjAaEXL
	kwcntytxuNYOY4BK7U0r4VOCLqafkcwawEYKXbAc7GXRU12JjTAdf/0jiK9dGwbzYqWq
	flgaakf36+wcdcOoqWUhBBGGU7D1x8Jzf8skoVwFqXj8uTrAq7eV4A0FxvZbJydxaB6H
	jCpQ==
X-Received: by 10.50.13.66 with SMTP id f2mr19121605igc.17.1381871286576; Tue,
	15 Oct 2013 14:08:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.26.233 with HTTP; Tue, 15 Oct 2013 14:07:46 -0700 (PDT)
From: Diego Sueiro <diego.sueiro@gmail.com>
Date: Tue, 15 Oct 2013 18:07:46 -0300
Message-ID: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: 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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Oct 2013 21:08:08 -0000
Content-Type: multipart/alternative; boundary=089e0118460e29731104e8cdfbb7

--089e0118460e29731104e8cdfbb7
Content-Type: text/plain; charset=ISO-8859-1

Folks,

I created the following bbapend recipe for linux-mainline_3.8.bb (from
meta-beagleboard on dylan branch) for beaglebone.
meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:

FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI += " file://0019-mine.patch \
             file://defconfig \
             "

But the defconfig and .config files on ${S} and ${WORKDIR} used are from
meta-beagleboad, not from my bbappend.

I tried to follow the instructions to add config fragments on the page
below but it did not worked too.
http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#changing-the-configuration

The strange thing is: My patch is applied but my defconfig, or config
fragment is not used.
I just want to add CONFIG_WATCHDOG_NOWAYOUT=y.

I already did a cleasstate but no success.

Any hints?


Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/

--089e0118460e29731104e8cdfbb7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Folks,<div><br></div><div style>I created the following bb=
apend recipe for <a href=3D"http://linux-mainline_3.8.bb">linux-mainline_3.=
8.bb</a> (from meta-beagleboard on dylan branch) for beaglebone.</div><div =
style>

meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:<br></div><block=
quote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><div style>=
<div style>FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/files:&quot;</div>

</div><div style><div style>SRC_URI +=3D &quot; file://0019-mine.patch \<br=
></div></div><div style><div style>=A0 =A0 =A0 =A0 =A0 =A0 =A0file://defcon=
fig \</div></div><div style><div style>=A0 =A0 =A0 =A0 =A0 =A0 =A0&quot;</d=
iv></div></blockquote><div style>

<div style>But the defconfig and .config files on ${S} and ${WORKDIR} used =
are from meta-beagleboad, not from my bbappend.</div></div><div><br></div><=
div>I tried to follow the instructions to add config fragments on the page =
below but it did not worked too.</div>

<div><a href=3D"http://www.yoctoproject.org/docs/current/kernel-dev/kernel-=
dev.html#changing-the-configuration">http://www.yoctoproject.org/docs/curre=
nt/kernel-dev/kernel-dev.html#changing-the-configuration</a></div><div><br>

</div><div style>The strange thing is: My patch is applied but my defconfig=
, or config fragment is not used.</div><div style>I just want to add=A0CONF=
IG_WATCHDOG_NOWAYOUT=3Dy.</div><div style><br></div><div style>I already di=
d a cleasstate but no=A0success.</div>

<div style><br></div><div style>Any hints?</div><div><br></div><div><br cle=
ar=3D"all"><div><div dir=3D"ltr"><div>Regards,</div><div><br></div>--<br>*d=
S<br>Diego Sueiro<br><br>/*long live rock &#39;n roll*/<br></div></div>
</div></div>

--089e0118460e29731104e8cdfbb7--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <katutxakurra@gmail.com>
Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com
	[209.85.223.176])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 85EE6E01708
	for <yocto@yoctoproject.org>; Tue, 15 Oct 2013 14:29:55 -0700 (PDT)
Received: by mail-ie0-f176.google.com with SMTP id u16so8876287iet.35
	for <yocto@yoctoproject.org>; Tue, 15 Oct 2013 14:29:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=j+ubMPD6svQED9gDlipRi//tlw+Np7qP0kKQtIHDkns=;
	b=C3Kz58/cgZpM3Xe/ytXx6v61uzRHpWr2tn8qjOH4vYLXs2LOrx416zCA+IOyH/oioQ
	2ff2oFlZx3pYfiRpLi7IpC+BXeNYw/cczXXfnHrR4dfeghh4fMzrmxbvGR/PFQWRbMpc
	Wk5wx1UdDM5hJoq6kBPREV6OyfyzDWSP98Arwqq1TDbp07ldzfC2R1NSvMYThl85F6Su
	g3D4PwtXzTU638mxExD9uQfdL3bJXhkAjlKq6XCfxEYZ2e1ovM/cJ+R7qgzCc8zWjRvw
	OW0fKayvLDRi0mcGLWcaRv+g1Tgw9sfILpp6xOpgC8GkEVI/kppDCCG1JR0XDi2sUZFz
	C7/g==
MIME-Version: 1.0
X-Received: by 10.50.153.50 with SMTP id vd18mr18888594igb.6.1381872595207;
	Tue, 15 Oct 2013 14:29:55 -0700 (PDT)
Received: by 10.50.231.161 with HTTP; Tue, 15 Oct 2013 14:29:55 -0700 (PDT)
In-Reply-To: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
Date: Tue, 15 Oct 2013 22:29:55 +0100
Message-ID: <CAM1ZcoVTQ0O1go2bN8u20JZCbn8=Lp5rOjVmntmux5z+TYT7gg@mail.gmail.com>
From: Katu Txakur <katutxakurra@gmail.com>
To: Diego Sueiro <diego.sueiro@gmail.com>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Oct 2013 21:29:56 -0000
Content-Type: multipart/alternative; boundary=089e013a009e298daf04e8ce4998

--089e013a009e298daf04e8ce4998
Content-Type: text/plain; charset=ISO-8859-1

Hi Diego,

I may be wrong here, but I had a similar issue and I gave up. As I
understand from
https://www.yoctoproject.org/sites/yoctoproject.org/files/elc2013-kernel-lab.pdf
if you are not using the linux-yocto kernel you need the whole defconfig.
Anyway, reading the kernel lab is probably a good idea.

good luck,
Katu


2013/10/15 Diego Sueiro <diego.sueiro@gmail.com>

> Folks,
>
> I created the following bbapend recipe for linux-mainline_3.8.bb (from
> meta-beagleboard on dylan branch) for beaglebone.
> meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> SRC_URI += " file://0019-mine.patch \
>              file://defconfig \
>              "
>
> But the defconfig and .config files on ${S} and ${WORKDIR} used are from
> meta-beagleboad, not from my bbappend.
>
> I tried to follow the instructions to add config fragments on the page
> below but it did not worked too.
>
> http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#changing-the-configuration
>
> The strange thing is: My patch is applied but my defconfig, or config
> fragment is not used.
> I just want to add CONFIG_WATCHDOG_NOWAYOUT=y.
>
> I already did a cleasstate but no success.
>
> Any hints?
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>

--089e013a009e298daf04e8ce4998
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Diego,<div><br></div><div>I may be wrong here, but I ha=
d a similar issue and I gave up. As I understand from</div><div><a href=3D"=
https://www.yoctoproject.org/sites/yoctoproject.org/files/elc2013-kernel-la=
b.pdf">https://www.yoctoproject.org/sites/yoctoproject.org/files/elc2013-ke=
rnel-lab.pdf</a><br>
</div><div>if you are not using the linux-yocto kernel you need the whole d=
efconfig. Anyway, reading the kernel lab is probably a good idea.</div><div=
><br></div><div>good luck,</div><div>Katu</div></div><div class=3D"gmail_ex=
tra">
<br><br><div class=3D"gmail_quote">2013/10/15 Diego Sueiro <span dir=3D"ltr=
">&lt;<a href=3D"mailto:diego.sueiro@gmail.com" target=3D"_blank">diego.sue=
iro@gmail.com</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">Folks,<div><br></div><div>I created the following bbapend =
recipe for <a href=3D"http://linux-mainline_3.8.bb" target=3D"_blank">linux=
-mainline_3.8.bb</a> (from meta-beagleboard on dylan branch) for beaglebone=
.</div>
<div>

meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:<br></div><block=
quote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><div><div>F=
ILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/files:&quot;</div>

</div><div><div>SRC_URI +=3D &quot; file://0019-mine.patch \<br></div></div=
><div><div>=A0 =A0 =A0 =A0 =A0 =A0 =A0file://defconfig \</div></div><div><d=
iv>=A0 =A0 =A0 =A0 =A0 =A0 =A0&quot;</div></div></blockquote><div>

<div>But the defconfig and .config files on ${S} and ${WORKDIR} used are fr=
om meta-beagleboad, not from my bbappend.</div></div><div><br></div><div>I =
tried to follow the instructions to add config fragments on the page below =
but it did not worked too.</div>


<div><a href=3D"http://www.yoctoproject.org/docs/current/kernel-dev/kernel-=
dev.html#changing-the-configuration" target=3D"_blank">http://www.yoctoproj=
ect.org/docs/current/kernel-dev/kernel-dev.html#changing-the-configuration<=
/a></div>
<div><br>

</div><div>The strange thing is: My patch is applied but my defconfig, or c=
onfig fragment is not used.</div><div>I just want to add=A0CONFIG_WATCHDOG_=
NOWAYOUT=3Dy.</div><div><br></div><div>I already did a cleasstate but no=A0=
success.</div>


<div><br></div><div>Any hints?</div><div><br></div><div><br clear=3D"all"><=
div><div dir=3D"ltr"><div>Regards,</div><div><br></div>--<br>*dS<br>Diego S=
ueiro<br><br>/*long live rock &#39;n roll*/<br></div></div>
</div></div>
<br>_______________________________________________<br>
yocto mailing list<br>
<a href=3D"mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a><br>
<a href=3D"https://lists.yoctoproject.org/listinfo/yocto" target=3D"_blank"=
>https://lists.yoctoproject.org/listinfo/yocto</a><br>
<br></blockquote></div><br></div>

--089e013a009e298daf04e8ce4998--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <rstreif@linuxfoundation.org>
Received: from mail-ea0-f181.google.com (mail-ea0-f181.google.com
	[209.85.215.181])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 9B0D3E01708
	for <yocto@yoctoproject.org>; Tue, 15 Oct 2013 14:49:18 -0700 (PDT)
Received: by mail-ea0-f181.google.com with SMTP id d10so4321070eaj.12
	for <yocto@yoctoproject.org>; Tue, 15 Oct 2013 14:49:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=linuxfoundation.org; s=google;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=E1NN/fhaTeRepONMuDHLRtOfTAqxrZoZw2nWVKAIN3c=;
	b=AXuFpODrJkJF+gTnMCuU7IRTOk7iJBN6Xte4cB2iuN5JF8lI0KQhxfpdzN5GMZY3Gf
	EbwEhTBx8cJn5GxAit1+3Z02rrMTxXhalTgKLgXjaNWYyIagGPqWjWMT+NjzEo/zZO95
	gmvHFf4/ncRjHOzdKsBuOscRNOcH+HdYIzPhQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type;
	bh=E1NN/fhaTeRepONMuDHLRtOfTAqxrZoZw2nWVKAIN3c=;
	b=UwyHTl2xeMvwHdtUF3bjXzc11+RN4R7ZqMEb4njKnaOpGWYTh26GI3fuBcA6Iq/bsN
	4O4DWvKqMavGwmOSk6z+wfdnhVRAQ7V1h/r7cSB6QPbDNXVysjaYBLdzB2wWOBcIltNN
	UR85XaBsuuxkX+M8hAtSlQ6hobQax65eV8oHdLguhoiGmxixU9CB5EYQM7rWuaVEjm/x
	hSAYopEv3Cbnf6MVyYkHgRnm3p7thcWS11bFbLDWs9kbvRtlwc+4RKNA078T7/1fahh5
	H9k5IEcEPutKt5F6id584dWI7PtUDDjpdS7FfxCRGk/guAF9M7OE2L/L70nTe7ZbPSPA
	Rh2g==
X-Gm-Message-State: ALoCoQmQ9Ir3yj8GqVKKfBF06xSXUjWUx6i92EM/8cjpn7afTZ/euzDWdEP1JjLTcK4RNpNkPrKo
MIME-Version: 1.0
X-Received: by 10.14.183.2 with SMTP id p2mr3847542eem.44.1381873757534; Tue,
	15 Oct 2013 14:49:17 -0700 (PDT)
Received: by 10.223.131.3 with HTTP; Tue, 15 Oct 2013 14:49:17 -0700 (PDT)
In-Reply-To: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
Date: Tue, 15 Oct 2013 14:49:17 -0700
Message-ID: <CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
From: Rudolf Streif <rstreif@linuxfoundation.org>
To: Diego Sueiro <diego.sueiro@gmail.com>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Oct 2013 21:49:20 -0000
Content-Type: multipart/alternative; boundary=047d7b343dc471453e04e8ce8eb2

--047d7b343dc471453e04e8ce8eb2
Content-Type: text/plain; charset=ISO-8859-1

Diego,

You are appending a kernel recipe that uses the Linux Yocto tooling. The
defconfig is essentially comprised of many different pieces from the meta
branch of the Yocto kernel repository and optional configuration fragments
that you provide. This tooling will not recognize a defconfig file you
provide but it does recognize configuration fragments to be added to
.config.

You need to put

CONFIG_WATCHDOG_NOWAYOUT=y

into a file that ends with .cfg eg. watchdog.cfg and then modify your
bbappend to

FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI += " file://0019-mine.patch \
             file://watchdog.cfg \
             "

Rudi



On Tue, Oct 15, 2013 at 2:07 PM, Diego Sueiro <diego.sueiro@gmail.com>wrote:

> Folks,
>
> I created the following bbapend recipe for linux-mainline_3.8.bb (from
> meta-beagleboard on dylan branch) for beaglebone.
> meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> SRC_URI += " file://0019-mine.patch \
>              file://defconfig \
>              "
>
> But the defconfig and .config files on ${S} and ${WORKDIR} used are from
> meta-beagleboad, not from my bbappend.
>
> I tried to follow the instructions to add config fragments on the page
> below but it did not worked too.
>
> http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#changing-the-configuration
>
> The strange thing is: My patch is applied but my defconfig, or config
> fragment is not used.
> I just want to add CONFIG_WATCHDOG_NOWAYOUT=y.
>
> I already did a cleasstate but no success.
>
> Any hints?
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>

--047d7b343dc471453e04e8ce8eb2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Diego,<div><br></div><div>You are appending a kernel recip=
e that uses the Linux Yocto tooling. The defconfig is essentially comprised=
 of many different pieces from the meta branch of the Yocto kernel reposito=
ry and optional configuration fragments that you provide. This tooling will=
 not recognize a defconfig file you provide but it does recognize configura=
tion fragments to be added to .config.</div>
<div><br></div><div>You need to put=A0</div><div><br></div><div><span style=
=3D"font-family:arial,sans-serif;font-size:13.333333969116211px">CONFIG_WAT=
CHDOG_NOWAYOUT=3D</span><span style=3D"font-family:arial,sans-serif;font-si=
ze:13.333333969116211px">y</span><br>
</div><div><span style=3D"font-family:arial,sans-serif;font-size:13.3333339=
69116211px"><br></span></div><div><span style=3D"font-family:arial,sans-ser=
if;font-size:13.333333969116211px">into a file that ends with .cfg eg. watc=
hdog.cfg and then modify your bbappend to</span></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:13.3333339691162=
11px"><br></span></div><div><div style=3D"font-family:arial,sans-serif;font=
-size:13.333333969116211px">FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/f=
iles:&quot;</div>
<div style=3D"font-family:arial,sans-serif;font-size:13.333333969116211px">=
SRC_URI +=3D &quot; file://0019-mine.patch \<br></div><div style=3D"font-fa=
mily:arial,sans-serif;font-size:13.333333969116211px">=A0 =A0 =A0 =A0 =A0 =
=A0 =A0file://watchdog.cfg \</div>
<div style=3D"font-family:arial,sans-serif;font-size:13.333333969116211px">=
=A0 =A0 =A0 =A0 =A0 =A0 =A0&quot;</div></div><div><span style=3D"font-famil=
y:arial,sans-serif;font-size:13.333333969116211px"><br></span></div><div><s=
pan style=3D"font-family:arial,sans-serif;font-size:13.333333969116211px">R=
udi</span></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:13.3333339691162=
11px"><br></span></div><div class=3D"gmail_extra"><br><br><div class=3D"gma=
il_quote">On Tue, Oct 15, 2013 at 2:07 PM, Diego Sueiro <span dir=3D"ltr">&=
lt;<a href=3D"mailto:diego.sueiro@gmail.com" target=3D"_blank">diego.sueiro=
@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Folks,<div><br></div><div>I=
 created the following bbapend recipe for <a href=3D"http://linux-mainline_=
3.8.bb" target=3D"_blank">linux-mainline_3.8.bb</a> (from meta-beagleboard =
on dylan branch) for beaglebone.</div>
<div>

meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:<br></div><block=
quote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><div><div>F=
ILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/files:&quot;</div>

</div><div><div>SRC_URI +=3D &quot; file://0019-mine.patch \<br></div></div=
><div><div>=A0 =A0 =A0 =A0 =A0 =A0 =A0file://defconfig \</div></div><div><d=
iv>=A0 =A0 =A0 =A0 =A0 =A0 =A0&quot;</div></div></blockquote><div>

<div>But the defconfig and .config files on ${S} and ${WORKDIR} used are fr=
om meta-beagleboad, not from my bbappend.</div></div><div><br></div><div>I =
tried to follow the instructions to add config fragments on the page below =
but it did not worked too.</div>


<div><a href=3D"http://www.yoctoproject.org/docs/current/kernel-dev/kernel-=
dev.html#changing-the-configuration" target=3D"_blank">http://www.yoctoproj=
ect.org/docs/current/kernel-dev/kernel-dev.html#changing-the-configuration<=
/a></div>
<div><br>

</div><div>The strange thing is: My patch is applied but my defconfig, or c=
onfig fragment is not used.</div><div>I just want to add=A0CONFIG_WATCHDOG_=
NOWAYOUT=3Dy.</div><div><br></div><div>I already did a cleasstate but no=A0=
success.</div>


<div><br></div><div>Any hints?</div><div><br></div><div><br clear=3D"all"><=
div><div dir=3D"ltr"><div>Regards,</div><div><br></div>--<br>*dS<br>Diego S=
ueiro<br><br>/*long live rock &#39;n roll*/<br></div></div>
</div></div>
<br>_______________________________________________<br>
yocto mailing list<br>
<a href=3D"mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a><br>
<a href=3D"https://lists.yoctoproject.org/listinfo/yocto" target=3D"_blank"=
>https://lists.yoctoproject.org/listinfo/yocto</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div><div dir=3D"ltr=
"><div><font face=3D"garamond, serif"><span style=3D"border-collapse:collap=
se;color:rgb(102,102,102);font-family:arial,sans-serif;font-size:13px"><br>=
</span></font></div>
</div>
</div></div>

--047d7b343dc471453e04e8ce8eb2--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <andrea.adami@gmail.com>
Received: from mail-lb0-f176.google.com (mail-lb0-f176.google.com
	[209.85.217.176])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 0AE4CE0170D
	for <yocto@yoctoproject.org>; Tue, 15 Oct 2013 14:55:07 -0700 (PDT)
Received: by mail-lb0-f176.google.com with SMTP id y6so37047lbh.21
	for <yocto@yoctoproject.org>; Tue, 15 Oct 2013 14:55:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=Tc4s+DBKIQ2chMc4QsUH/t8uV0rxTnY9rhsYgr4GKHE=;
	b=QXZ1+CrE8GbFlVb60XK7yr8xud0V+HAkpxhV4pvEncIsHqnLUMknnxxk62jT0dbjb8
	0+HpA5l4g8AEtdwu0/f/NlQCVB6OVyjBocFKoQ0FM0Z4N5nl37q5rwWNkVm6lMNdMOSk
	a/Oh9KnktkcoErO6HXQ4/f+RcDOsGIdbBOWBQj5863klxpWokBnx9M8c7DQP7MzuhId6
	lsDQoEBwSO63YsNPZmhP/NvA/QZowjsViL4hNHGti6RznGN/wEOkh+MX3lf6UqDizMkC
	yAIyEhD+iFk3D8tpcWm5nX9yNKoD2zs7KC7Hj4AqMf6N0EqWJg96EdehaNqocmljtUJg
	J4eQ==
MIME-Version: 1.0
X-Received: by 10.112.51.166 with SMTP id l6mr34658lbo.5.1381874105950; Tue,
	15 Oct 2013 14:55:05 -0700 (PDT)
Received: by 10.112.52.74 with HTTP; Tue, 15 Oct 2013 14:55:05 -0700 (PDT)
In-Reply-To: <CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
Date: Tue, 15 Oct 2013 23:55:05 +0200
Message-ID: <CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
From: Andrea Adami <andrea.adami@gmail.com>
To: Rudolf Streif <rstreif@linuxfoundation.org>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Oct 2013 21:55:08 -0000
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I guess you're setting a wrong FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

See this example, using simple defconfig for some devices and an
experimental configuration (WIP ;) fo others using fragments.

http://cgit.openembedded.org/meta-handheld/tree/recipes-kernel/linux/linux-yocto_3.10.bbappend

Cheers

Andrea


On Tue, Oct 15, 2013 at 11:49 PM, Rudolf Streif
<rstreif@linuxfoundation.org> wrote:
> Diego,
>
> You are appending a kernel recipe that uses the Linux Yocto tooling. The
> defconfig is essentially comprised of many different pieces from the meta
> branch of the Yocto kernel repository and optional configuration fragments
> that you provide. This tooling will not recognize a defconfig file you
> provide but it does recognize configuration fragments to be added to
> .config.
>
> You need to put
>
> CONFIG_WATCHDOG_NOWAYOUT=y
>
> into a file that ends with .cfg eg. watchdog.cfg and then modify your
> bbappend to
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> SRC_URI += " file://0019-mine.patch \
>              file://watchdog.cfg \
>              "
>
> Rudi
>
>
>
> On Tue, Oct 15, 2013 at 2:07 PM, Diego Sueiro <diego.sueiro@gmail.com>
> wrote:
>>
>> Folks,
>>
>> I created the following bbapend recipe for linux-mainline_3.8.bb (from
>> meta-beagleboard on dylan branch) for beaglebone.
>> meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
>>
>> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>> SRC_URI += " file://0019-mine.patch \
>>              file://defconfig \
>>              "
>>
>> But the defconfig and .config files on ${S} and ${WORKDIR} used are from
>> meta-beagleboad, not from my bbappend.
>>
>> I tried to follow the instructions to add config fragments on the page
>> below but it did not worked too.
>>
>> http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#changing-the-configuration
>>
>> The strange thing is: My patch is applied but my defconfig, or config
>> fragment is not used.
>> I just want to add CONFIG_WATCHDOG_NOWAYOUT=y.
>>
>> I already did a cleasstate but no success.
>>
>> Any hints?
>>
>>
>> Regards,
>>
>> --
>> *dS
>> Diego Sueiro
>>
>> /*long live rock 'n roll*/
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
>
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>


From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <diego.sueiro@gmail.com>
Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com
	[209.85.223.170])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 99E33E01661
	for <yocto@yoctoproject.org>; Wed, 16 Oct 2013 10:25:59 -0700 (PDT)
Received: by mail-ie0-f170.google.com with SMTP id at1so1924629iec.1
	for <yocto@yoctoproject.org>; Wed, 16 Oct 2013 10:25:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=j2l1bOk0JjZ5Aq/SNkdHjbKIYAGCG1N3uLwtGRinwDo=;
	b=WxakotJY9OWPEXL7cJrxIGOWtn4kGTbNspwjdOJZ/ii3aTDc1mcpGXu8m8w4iFOKwK
	d6yP7uCH36Ruu+lHUs75zFoELiHig+5OpL+inpAygx3YgrahxBFERIXluuNEnXkhFdef
	AgytDff8Hm0lmoKNy5YBRqS5m4NLQ4Yd0wYkiL0efF319Zr2LsK0HMTys8B+zoKU44SP
	EiqaGZm8dizKwLOg29MxdgjRxkfqOJDow4m1/5sgw8fFqjeSVrkqxSJ4tMIsu0FIBeEJ
	2XKSrSkqhq5QenJz5M2QjeEpOyXxmpCnJCR7TjJ6t0X/BU+2ZLL/CbMlYCMMUcDpB22g
	CGdQ==
X-Received: by 10.50.26.36 with SMTP id i4mr3067273igg.33.1381944358385; Wed,
	16 Oct 2013 10:25:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.26.233 with HTTP; Wed, 16 Oct 2013 10:25:38 -0700 (PDT)
In-Reply-To: <CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
From: Diego Sueiro <diego.sueiro@gmail.com>
Date: Wed, 16 Oct 2013 14:25:38 -0300
Message-ID: <CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
To: Andrea Adami <andrea.adami@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Rudolf Streif <rstreif@linuxfoundation.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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2013 17:26:00 -0000
Content-Type: multipart/alternative; boundary=047d7bd76fe094cf9604e8defe5e

--047d7bd76fe094cf9604e8defe5e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Guys,

As I told before, I already tried the config fragment strategy and it did
not worked too.

Looking at linux-mailine-3.8.bb from meta-beagleboard[1] it just inherits
kernel and not inherits linux-yocto or requires linux-yocto.inc. So I
believe that the config fragment will not work. But I can be wrong.

On directory "meta-mine/recipes-kernel/linux/" I have this:

.
=E2=94=9C=E2=94=80=E2=94=80 files
=E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 mine.patch
=E2=94=82   =E2=94=94=E2=94=80=E2=94=80 defconfig
=E2=94=94=E2=94=80=E2=94=80 linux-mainline_3.8.bbappend


And my linux-mainline_3.8.bbappend recipe:

FILESEXTRAPATHS_prepend :=3D "${THISDIR}/files:"
SRC_URI +=3D " file://mine.patch \
             file://defconfig \
             "

The mine.patch is applied but defconfig not.

I've already tried to use another FILESEXTRAPATHS layout like[2],but no
success too.

How can I have the "bb" command listed on the following link?
http://www.crashcourse.ca/wiki/index.php/OE_FILESEXTRAPATHS


[1] -
 https://github.com/beagleboard/meta-beagleboard/blob/dylan/common-bsp/reci=
pes-kernel/linux/linux-mainline_3.8.bb
[2] -
http://cgit.openembedded.org/meta-handheld/tree/recipes-kernel/linux/linux-=
yocto_3.10.bbappend

Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/


2013/10/15 Andrea Adami <andrea.adami@gmail.com>

> Hi,
>
> I guess you're setting a wrong FILESEXTRAPATHS_prepend :=3D
> "${THISDIR}/files:"
>
> See this example, using simple defconfig for some devices and an
> experimental configuration (WIP ;) fo others using fragments.
>
>
> http://cgit.openembedded.org/meta-handheld/tree/recipes-kernel/linux/linu=
x-yocto_3.10.bbappend
>
> Cheers
>
> Andrea
>
>
> On Tue, Oct 15, 2013 at 11:49 PM, Rudolf Streif
> <rstreif@linuxfoundation.org> wrote:
> > Diego,
> >
> > You are appending a kernel recipe that uses the Linux Yocto tooling. Th=
e
> > defconfig is essentially comprised of many different pieces from the me=
ta
> > branch of the Yocto kernel repository and optional configuration
> fragments
> > that you provide. This tooling will not recognize a defconfig file you
> > provide but it does recognize configuration fragments to be added to
> > .config.
> >
> > You need to put
> >
> > CONFIG_WATCHDOG_NOWAYOUT=3Dy
> >
> > into a file that ends with .cfg eg. watchdog.cfg and then modify your
> > bbappend to
> >
> > FILESEXTRAPATHS_prepend :=3D "${THISDIR}/files:"
> > SRC_URI +=3D " file://0019-mine.patch \
> >              file://watchdog.cfg \
> >              "
> >
> > Rudi
> >
> >
> >
> > On Tue, Oct 15, 2013 at 2:07 PM, Diego Sueiro <diego.sueiro@gmail.com>
> > wrote:
> >>
> >> Folks,
> >>
> >> I created the following bbapend recipe for linux-mainline_3.8.bb (from
> >> meta-beagleboard on dylan branch) for beaglebone.
> >> meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
> >>
> >> FILESEXTRAPATHS_prepend :=3D "${THISDIR}/files:"
> >> SRC_URI +=3D " file://0019-mine.patch \
> >>              file://defconfig \
> >>              "
> >>
> >> But the defconfig and .config files on ${S} and ${WORKDIR} used are fr=
om
> >> meta-beagleboad, not from my bbappend.
> >>
> >> I tried to follow the instructions to add config fragments on the page
> >> below but it did not worked too.
> >>
> >>
> http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#chang=
ing-the-configuration
> >>
> >> The strange thing is: My patch is applied but my defconfig, or config
> >> fragment is not used.
> >> I just want to add CONFIG_WATCHDOG_NOWAYOUT=3Dy.
> >>
> >> I already did a cleasstate but no success.
> >>
> >> Any hints?
> >>
> >>
> >> Regards,
> >>
> >> --
> >> *dS
> >> Diego Sueiro
> >>
> >> /*long live rock 'n roll*/
> >>
> >> _______________________________________________
> >> yocto mailing list
> >> yocto@yoctoproject.org
> >> https://lists.yoctoproject.org/listinfo/yocto
> >>
> >
> >
> >
> >
> >
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
>

--047d7bd76fe094cf9604e8defe5e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Guys,<div><br></div><div style>As I told before, I already=
 tried the config fragment strategy and it did not worked too.</div><div st=
yle><br></div><div style>Looking at <a href=3D"http://linux-mailine-3.8.bb"=
>linux-mailine-3.8.bb</a> from meta-beagleboard[1] it just inherits kernel =
and not inherits linux-yocto or requires linux-yocto.inc. So I believe that=
 the config fragment will not work. But I can be wrong.</div>

<div style><br></div><div style>On directory &quot;meta-mine/recipes-kernel=
/linux/&quot; I have this:</div><div style><blockquote style=3D"margin:0px =
0px 0px 40px;border:none;padding:0px"><div style><div>.</div><div>=E2=94=9C=
=E2=94=80=E2=94=80 files</div>

<div>=E2=94=82 =C2=A0 =E2=94=9C=E2=94=80=E2=94=80 mine.patch</div><div>=E2=
=94=82 =C2=A0 =E2=94=94=E2=94=80=E2=94=80 defconfig</div><div>=E2=94=94=E2=
=94=80=E2=94=80 linux-mainline_3.8.bbappend<br></div></div></blockquote><di=
v style><br></div>And my=C2=A0linux-mainline_3.8.bbappend recipe:</div><div=
 style><blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px=
">

<div style><div>FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/files:&quot;<=
/div><div>SRC_URI +=3D &quot; file://mine.patch \<br></div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0file://defconfig \</div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;</div></div></blockquote>

The mine.patch is applied but defconfig not.</div><div style><br></div><div=
 style>I&#39;ve already tried to use another FILESEXTRAPATHS layout like[2]=
,but no success too.</div><div style><br></div><div style>How can I have th=
e &quot;bb&quot; command listed on the following link?</div>

<div style><a href=3D"http://www.crashcourse.ca/wiki/index.php/OE_FILESEXTR=
APATHS">http://www.crashcourse.ca/wiki/index.php/OE_FILESEXTRAPATHS</a><br>=
</div><div style><br></div><div class=3D"gmail_extra"><br clear=3D"all"><di=
v>

<div dir=3D"ltr"><div>[1] -<a href=3D"=C2=A0https://github.com/beagleboard/=
meta-beagleboard/blob/dylan/common-bsp/recipes-kernel/linux/linux-mainline_=
3.8.bb">=C2=A0https://github.com/beagleboard/meta-beagleboard/blob/dylan/co=
mmon-bsp/recipes-kernel/linux/linux-mainline_3.8.bb</a></div>

<div>[2] -=C2=A0<a href=3D"http://cgit.openembedded.org/meta-handheld/tree/=
recipes-kernel/linux/linux-yocto_3.10.bbappend">http://cgit.openembedded.or=
g/meta-handheld/tree/recipes-kernel/linux/linux-yocto_3.10.bbappend</a></di=
v>
<div>
<br></div><div>Regards,</div><div><br></div>--<br>*dS<br>Diego Sueiro<br><b=
r>/*long live rock &#39;n roll*/<br></div></div>
<br><br><div class=3D"gmail_quote">2013/10/15 Andrea Adami <span dir=3D"ltr=
">&lt;<a href=3D"mailto:andrea.adami@gmail.com" target=3D"_blank">andrea.ad=
ami@gmail.com</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,20=
4,204);border-left-style:solid;padding-left:1ex">

Hi,<br>
<br>
I guess you&#39;re setting a wrong FILESEXTRAPATHS_prepend :=3D &quot;${THI=
SDIR}/files:&quot;<br>
<br>
See this example, using simple defconfig for some devices and an<br>
experimental configuration (WIP ;) fo others using fragments.<br>
<br>
<a href=3D"http://cgit.openembedded.org/meta-handheld/tree/recipes-kernel/l=
inux/linux-yocto_3.10.bbappend" target=3D"_blank">http://cgit.openembedded.=
org/meta-handheld/tree/recipes-kernel/linux/linux-yocto_3.10.bbappend</a><b=
r>


<br>
Cheers<br>
<span class=3D""><font color=3D"#888888"><br>
Andrea<br>
</font></span><div class=3D""><div class=3D"h5"><br>
<br>
On Tue, Oct 15, 2013 at 11:49 PM, Rudolf Streif<br>
&lt;<a href=3D"mailto:rstreif@linuxfoundation.org">rstreif@linuxfoundation.=
org</a>&gt; wrote:<br>
&gt; Diego,<br>
&gt;<br>
&gt; You are appending a kernel recipe that uses the Linux Yocto tooling. T=
he<br>
&gt; defconfig is essentially comprised of many different pieces from the m=
eta<br>
&gt; branch of the Yocto kernel repository and optional configuration fragm=
ents<br>
&gt; that you provide. This tooling will not recognize a defconfig file you=
<br>
&gt; provide but it does recognize configuration fragments to be added to<b=
r>
&gt; .config.<br>
&gt;<br>
&gt; You need to put<br>
&gt;<br>
&gt; CONFIG_WATCHDOG_NOWAYOUT=3Dy<br>
&gt;<br>
&gt; into a file that ends with .cfg eg. watchdog.cfg and then modify your<=
br>
&gt; bbappend to<br>
&gt;<br>
&gt; FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/files:&quot;<br>
&gt; SRC_URI +=3D &quot; file://0019-mine.patch \<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0file://watchdog.cfg \<=
br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;<br>
&gt;<br>
&gt; Rudi<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; On Tue, Oct 15, 2013 at 2:07 PM, Diego Sueiro &lt;<a href=3D"mailto:di=
ego.sueiro@gmail.com">diego.sueiro@gmail.com</a>&gt;<br>
&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Folks,<br>
&gt;&gt;<br>
&gt;&gt; I created the following bbapend recipe for <a href=3D"http://linux=
-mainline_3.8.bb" target=3D"_blank">linux-mainline_3.8.bb</a> (from<br>
&gt;&gt; meta-beagleboard on dylan branch) for beaglebone.<br>
&gt;&gt; meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:<br>
&gt;&gt;<br>
&gt;&gt; FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/files:&quot;<br>
&gt;&gt; SRC_URI +=3D &quot; file://0019-mine.patch \<br>
&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0file://defconfig \=
<br>
&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;<br>
&gt;&gt;<br>
&gt;&gt; But the defconfig and .config files on ${S} and ${WORKDIR} used ar=
e from<br>
&gt;&gt; meta-beagleboad, not from my bbappend.<br>
&gt;&gt;<br>
&gt;&gt; I tried to follow the instructions to add config fragments on the =
page<br>
&gt;&gt; below but it did not worked too.<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"http://www.yoctoproject.org/docs/current/kernel-dev/ker=
nel-dev.html#changing-the-configuration" target=3D"_blank">http://www.yocto=
project.org/docs/current/kernel-dev/kernel-dev.html#changing-the-configurat=
ion</a><br>


&gt;&gt;<br>
&gt;&gt; The strange thing is: My patch is applied but my defconfig, or con=
fig<br>
&gt;&gt; fragment is not used.<br>
&gt;&gt; I just want to add CONFIG_WATCHDOG_NOWAYOUT=3Dy.<br>
&gt;&gt;<br>
&gt;&gt; I already did a cleasstate but no success.<br>
&gt;&gt;<br>
&gt;&gt; Any hints?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Regards,<br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; *dS<br>
&gt;&gt; Diego Sueiro<br>
&gt;&gt;<br>
&gt;&gt; /*long live rock &#39;n roll*/<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; yocto mailing list<br>
&gt;&gt; <a href=3D"mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</=
a><br>
&gt;&gt; <a href=3D"https://lists.yoctoproject.org/listinfo/yocto" target=
=3D"_blank">https://lists.yoctoproject.org/listinfo/yocto</a><br>
&gt;&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; yocto mailing list<br>
&gt; <a href=3D"mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a><b=
r>
&gt; <a href=3D"https://lists.yoctoproject.org/listinfo/yocto" target=3D"_b=
lank">https://lists.yoctoproject.org/listinfo/yocto</a><br>
&gt;<br>
</div></div></blockquote></div><br></div></div>

--047d7bd76fe094cf9604e8defe5e--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <diego.sueiro@gmail.com>
Received: from mail-ie0-f173.google.com (mail-ie0-f173.google.com
	[209.85.223.173])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 79C87E015BA
	for <yocto@yoctoproject.org>; Wed, 16 Oct 2013 11:19:56 -0700 (PDT)
Received: by mail-ie0-f173.google.com with SMTP id u16so2020837iet.18
	for <yocto@yoctoproject.org>; Wed, 16 Oct 2013 11:19:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=qBbvfpBYbScp74o2LuaxKx6YY/yWWLsv7JLJJeqGWws=;
	b=jHvq3hg7BhbwuPTl3PRj8fJX6Qidokvos8znWP+/awRgrRl4IthA8NEpg5JLbgOKpv
	qukxLhR9IqGffG6jnLsjQSKXf5i9JZ6ZxtscdZcYOUlSeIL+P0mxzTgV0cfmtLpuMU2a
	Pyoi95z1E9YWC/TxCDQD7JKIwGKoSYvCWdyL5DRxUlVN5u7L1fCk2HmQGFL5udlBvgXK
	9B4cas9StBRnUtPSeZIHF4KuwbeFGShndc17UPYhbl034o4rqzhloAIomyaT0xYSHYtc
	qFCXYkthADQrNg0dj1+5xsleiHcr+tMv7VJeIlhMJ3ORJl9ANtezycU6+8n2u3GfS39s
	lovQ==
X-Received: by 10.50.13.66 with SMTP id f2mr23115784igc.17.1381947595949; Wed,
	16 Oct 2013 11:19:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.26.233 with HTTP; Wed, 16 Oct 2013 11:19:35 -0700 (PDT)
In-Reply-To: <CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
From: Diego Sueiro <diego.sueiro@gmail.com>
Date: Wed, 16 Oct 2013 15:19:35 -0300
Message-ID: <CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
To: Andrea Adami <andrea.adami@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Rudolf Streif <rstreif@linuxfoundation.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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2013 18:19:57 -0000
Content-Type: multipart/alternative; boundary=089e0118460e8e112d04e8dfbf27

--089e0118460e8e112d04e8dfbf27
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Folks,

Looking at log.do_unpack it shows:

...
NOTE:
Unpacking <...>/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-main=
line-3.8/beaglebone/defconfig
to <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-=
gnueabi/linux-mainline/3.8.13-r23a/
...

NOTE: Unpacking
<...>/meta-mine/recipes-kernel/linux/linux-mainline-3.8/mine.patch to
<...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnu=
eabi/linux-mainline/3.8.13-r23a/
NOTE:
Unpacking <...>/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-main=
line-3.8/beaglebone/defconfig
to <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-=
gnueabi/linux-mainline/3.8.13-r23a/


Note that it copies defconfig from meta-beagleboard and in the end, instead
copying mine, it is copying from meta-beagleboard again.

My layer has the priority higher than meta-beagleboard.



Abra=C3=A7os,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br

Engenheiro de Controle e Automa=C3=A7=C3=A3o
UNIVERSIDADE FEDERAL DE ITAJUB=C3=80

/*long live rock 'n roll*/


2013/10/16 Diego Sueiro <diego.sueiro@gmail.com>

> Guys,
>
> As I told before, I already tried the config fragment strategy and it did
> not worked too.
>
> Looking at linux-mailine-3.8.bb from meta-beagleboard[1] it just inherits
> kernel and not inherits linux-yocto or requires linux-yocto.inc. So I
> believe that the config fragment will not work. But I can be wrong.
>
> On directory "meta-mine/recipes-kernel/linux/" I have this:
>
> .
> =E2=94=9C=E2=94=80=E2=94=80 files
> =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 mine.patch
> =E2=94=82   =E2=94=94=E2=94=80=E2=94=80 defconfig
> =E2=94=94=E2=94=80=E2=94=80 linux-mainline_3.8.bbappend
>
>
> And my linux-mainline_3.8.bbappend recipe:
>
> FILESEXTRAPATHS_prepend :=3D "${THISDIR}/files:"
> SRC_URI +=3D " file://mine.patch \
>              file://defconfig \
>              "
>
> The mine.patch is applied but defconfig not.
>
> I've already tried to use another FILESEXTRAPATHS layout like[2],but no
> success too.
>
> How can I have the "bb" command listed on the following link?
> http://www.crashcourse.ca/wiki/index.php/OE_FILESEXTRAPATHS
>
>
>  [1] -
>  https://github.com/beagleboard/meta-beagleboard/blob/dylan/common-bsp/re=
cipes-kernel/linux/linux-mainline_3.8.bb<https://github.com/beagleboard/met=
a-beagleboard/blob/dylan/common-bsp/recipes-kernel/linux/linux-mainline_3.8=
.bb>
> [2] -
> http://cgit.openembedded.org/meta-handheld/tree/recipes-kernel/linux/linu=
x-yocto_3.10.bbappend
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/
>
>
> 2013/10/15 Andrea Adami <andrea.adami@gmail.com>
>
>> Hi,
>>
>> I guess you're setting a wrong FILESEXTRAPATHS_prepend :=3D
>> "${THISDIR}/files:"
>>
>> See this example, using simple defconfig for some devices and an
>> experimental configuration (WIP ;) fo others using fragments.
>>
>>
>> http://cgit.openembedded.org/meta-handheld/tree/recipes-kernel/linux/lin=
ux-yocto_3.10.bbappend
>>
>> Cheers
>>
>> Andrea
>>
>>
>> On Tue, Oct 15, 2013 at 11:49 PM, Rudolf Streif
>> <rstreif@linuxfoundation.org> wrote:
>> > Diego,
>> >
>> > You are appending a kernel recipe that uses the Linux Yocto tooling. T=
he
>> > defconfig is essentially comprised of many different pieces from the
>> meta
>> > branch of the Yocto kernel repository and optional configuration
>> fragments
>> > that you provide. This tooling will not recognize a defconfig file you
>> > provide but it does recognize configuration fragments to be added to
>> > .config.
>> >
>> > You need to put
>> >
>> > CONFIG_WATCHDOG_NOWAYOUT=3Dy
>> >
>> > into a file that ends with .cfg eg. watchdog.cfg and then modify your
>> > bbappend to
>> >
>> > FILESEXTRAPATHS_prepend :=3D "${THISDIR}/files:"
>> > SRC_URI +=3D " file://0019-mine.patch \
>> >              file://watchdog.cfg \
>> >              "
>> >
>> > Rudi
>> >
>> >
>> >
>> > On Tue, Oct 15, 2013 at 2:07 PM, Diego Sueiro <diego.sueiro@gmail.com>
>> > wrote:
>> >>
>> >> Folks,
>> >>
>> >> I created the following bbapend recipe for linux-mainline_3.8.bb (fro=
m
>> >> meta-beagleboard on dylan branch) for beaglebone.
>> >> meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
>> >>
>> >> FILESEXTRAPATHS_prepend :=3D "${THISDIR}/files:"
>> >> SRC_URI +=3D " file://0019-mine.patch \
>> >>              file://defconfig \
>> >>              "
>> >>
>> >> But the defconfig and .config files on ${S} and ${WORKDIR} used are
>> from
>> >> meta-beagleboad, not from my bbappend.
>> >>
>> >> I tried to follow the instructions to add config fragments on the pag=
e
>> >> below but it did not worked too.
>> >>
>> >>
>> http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#chan=
ging-the-configuration
>> >>
>> >> The strange thing is: My patch is applied but my defconfig, or config
>> >> fragment is not used.
>> >> I just want to add CONFIG_WATCHDOG_NOWAYOUT=3Dy.
>> >>
>> >> I already did a cleasstate but no success.
>> >>
>> >> Any hints?
>> >>
>> >>
>> >> Regards,
>> >>
>> >> --
>> >> *dS
>> >> Diego Sueiro
>> >>
>> >> /*long live rock 'n roll*/
>> >>
>> >> _______________________________________________
>> >> yocto mailing list
>> >> yocto@yoctoproject.org
>> >> https://lists.yoctoproject.org/listinfo/yocto
>> >>
>> >
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > yocto mailing list
>> > yocto@yoctoproject.org
>> > https://lists.yoctoproject.org/listinfo/yocto
>> >
>>
>
>

--089e0118460e8e112d04e8dfbf27
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Folks,<div><br></div><div style>Looking at log.do_unpack i=
t shows:</div><div style><blockquote style=3D"margin:0px 0px 0px 40px;borde=
r:none;padding:0px"><div style>...</div><div style>NOTE: Unpacking=C2=A0&lt=
;...&gt;/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline-3.=
8/beaglebone/defconfig to=C2=A0&lt;...&gt;/build/tmp-angstrom_v2013_06-egli=
bc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.13-r23a/<br>

</div><div>...</div></blockquote></div><blockquote style=3D"margin:0px 0px =
0px 40px;border:none;padding:0px"><div style><div style>NOTE: Unpacking &lt=
;...&gt;/meta-mine/recipes-kernel/linux/linux-mainline-3.8/mine.patch to &l=
t;...&gt;/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux=
-gnueabi/linux-mainline/3.8.13-r23a/</div>

</div><div style><div style>NOTE: Unpacking=C2=A0&lt;...&gt;/meta-beagleboa=
rd/common-bsp/recipes-kernel/linux/linux-mainline-3.8/beaglebone/defconfig =
to=C2=A0&lt;...&gt;/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angs=
trom-linux-gnueabi/linux-mainline/3.8.13-r23a/</div>

</div></blockquote><br><div style>Note that it copies defconfig from meta-b=
eagleboard and in the end, instead copying mine, it is copying from meta-be=
agleboard again.</div><div style><br></div><div style>My layer has the prio=
rity higher than meta-beagleboard.</div>

<div style><br></div><div style><br></div></div><div class=3D"gmail_extra">=
<br clear=3D"all"><div><div dir=3D"ltr"><div>Abra=C3=A7os,</div><div><br></=
div>--<br>*dS<br>Diego Sueiro<br><br>Administrador do Embarcados<br><a href=
=3D"http://www.embarcados.com.br" target=3D"_blank">www.embarcados.com.br</=
a><br>

<br>Engenheiro de Controle e Automa=C3=A7=C3=A3o<br>UNIVERSIDADE FEDERAL DE=
 ITAJUB=C3=80<br><br>/*long live rock &#39;n roll*/</div></div>
<br><br><div class=3D"gmail_quote">2013/10/16 Diego Sueiro <span dir=3D"ltr=
">&lt;<a href=3D"mailto:diego.sueiro@gmail.com" target=3D"_blank">diego.sue=
iro@gmail.com</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div dir=3D"ltr">Guys,<div><br></div><div>As I told before, I already tried=
 the config fragment strategy and it did not worked too.</div><div><br></di=
v><div>Looking at <a href=3D"http://linux-mailine-3.8.bb" target=3D"_blank"=
>linux-mailine-3.8.bb</a> from meta-beagleboard[1] it just inherits kernel =
and not inherits linux-yocto or requires linux-yocto.inc. So I believe that=
 the config fragment will not work. But I can be wrong.</div>


<div><br></div><div>On directory &quot;meta-mine/recipes-kernel/linux/&quot=
; I have this:</div><div><blockquote style=3D"margin:0px 0px 0px 40px;borde=
r:none;padding:0px"><div><div>.</div><div>=E2=94=9C=E2=94=80=E2=94=80 files=
</div>
<div>=E2=94=82 =C2=A0 =E2=94=9C=E2=94=80=E2=94=80 mine.patch</div><div>=E2=
=94=82 =C2=A0 =E2=94=94=E2=94=80=E2=94=80 defconfig</div><div>=E2=94=94=E2=
=94=80=E2=94=80 linux-mainline_3.8.bbappend<br></div></div></blockquote><di=
v><br></div>And my=C2=A0linux-mainline_3.8.bbappend recipe:</div><div><bloc=
kquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px">


<div><div class=3D"im"><div>FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/f=
iles:&quot;</div></div><div>SRC_URI +=3D &quot; file://mine.patch \<br></di=
v><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0file://defconfig \</=
div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;</div></div>

</blockquote>
The mine.patch is applied but defconfig not.</div><div><br></div><div>I&#39=
;ve already tried to use another FILESEXTRAPATHS layout like[2],but no succ=
ess too.</div><div><br></div><div>How can I have the &quot;bb&quot; command=
 listed on the following link?</div>


<div><a href=3D"http://www.crashcourse.ca/wiki/index.php/OE_FILESEXTRAPATHS=
" target=3D"_blank">http://www.crashcourse.ca/wiki/index.php/OE_FILESEXTRAP=
ATHS</a><br></div><div><br></div><div class=3D"gmail_extra"><br clear=3D"al=
l">

<div>
<div dir=3D"ltr"><div>[1] -<a href=3D"https://github.com/beagleboard/meta-b=
eagleboard/blob/dylan/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb=
" target=3D"_blank">=C2=A0https://github.com/beagleboard/meta-beagleboard/b=
lob/dylan/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb</a></div>


<div>[2] -=C2=A0<a href=3D"http://cgit.openembedded.org/meta-handheld/tree/=
recipes-kernel/linux/linux-yocto_3.10.bbappend" target=3D"_blank">http://cg=
it.openembedded.org/meta-handheld/tree/recipes-kernel/linux/linux-yocto_3.1=
0.bbappend</a></div>

<div class=3D"im"><div>
<br></div><div>Regards,</div><div><br></div>--<br>*dS<br>Diego Sueiro<br><b=
r>/*long live rock &#39;n roll*/<br></div></div></div><div><div class=3D"h5=
">
<br><br><div class=3D"gmail_quote">2013/10/15 Andrea Adami <span dir=3D"ltr=
">&lt;<a href=3D"mailto:andrea.adami@gmail.com" target=3D"_blank">andrea.ad=
ami@gmail.com</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,20=
4,204);border-left-style:solid;padding-left:1ex">


Hi,<br>
<br>
I guess you&#39;re setting a wrong FILESEXTRAPATHS_prepend :=3D &quot;${THI=
SDIR}/files:&quot;<br>
<br>
See this example, using simple defconfig for some devices and an<br>
experimental configuration (WIP ;) fo others using fragments.<br>
<br>
<a href=3D"http://cgit.openembedded.org/meta-handheld/tree/recipes-kernel/l=
inux/linux-yocto_3.10.bbappend" target=3D"_blank">http://cgit.openembedded.=
org/meta-handheld/tree/recipes-kernel/linux/linux-yocto_3.10.bbappend</a><b=
r>



<br>
Cheers<br>
<span><font color=3D"#888888"><br>
Andrea<br>
</font></span><div><div><br>
<br>
On Tue, Oct 15, 2013 at 11:49 PM, Rudolf Streif<br>
&lt;<a href=3D"mailto:rstreif@linuxfoundation.org" target=3D"_blank">rstrei=
f@linuxfoundation.org</a>&gt; wrote:<br>
&gt; Diego,<br>
&gt;<br>
&gt; You are appending a kernel recipe that uses the Linux Yocto tooling. T=
he<br>
&gt; defconfig is essentially comprised of many different pieces from the m=
eta<br>
&gt; branch of the Yocto kernel repository and optional configuration fragm=
ents<br>
&gt; that you provide. This tooling will not recognize a defconfig file you=
<br>
&gt; provide but it does recognize configuration fragments to be added to<b=
r>
&gt; .config.<br>
&gt;<br>
&gt; You need to put<br>
&gt;<br>
&gt; CONFIG_WATCHDOG_NOWAYOUT=3Dy<br>
&gt;<br>
&gt; into a file that ends with .cfg eg. watchdog.cfg and then modify your<=
br>
&gt; bbappend to<br>
&gt;<br>
&gt; FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/files:&quot;<br>
&gt; SRC_URI +=3D &quot; file://0019-mine.patch \<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0file://watchdog.cfg \<=
br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;<br>
&gt;<br>
&gt; Rudi<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; On Tue, Oct 15, 2013 at 2:07 PM, Diego Sueiro &lt;<a href=3D"mailto:di=
ego.sueiro@gmail.com" target=3D"_blank">diego.sueiro@gmail.com</a>&gt;<br>
&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Folks,<br>
&gt;&gt;<br>
&gt;&gt; I created the following bbapend recipe for <a href=3D"http://linux=
-mainline_3.8.bb" target=3D"_blank">linux-mainline_3.8.bb</a> (from<br>
&gt;&gt; meta-beagleboard on dylan branch) for beaglebone.<br>
&gt;&gt; meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:<br>
&gt;&gt;<br>
&gt;&gt; FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/files:&quot;<br>
&gt;&gt; SRC_URI +=3D &quot; file://0019-mine.patch \<br>
&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0file://defconfig \=
<br>
&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;<br>
&gt;&gt;<br>
&gt;&gt; But the defconfig and .config files on ${S} and ${WORKDIR} used ar=
e from<br>
&gt;&gt; meta-beagleboad, not from my bbappend.<br>
&gt;&gt;<br>
&gt;&gt; I tried to follow the instructions to add config fragments on the =
page<br>
&gt;&gt; below but it did not worked too.<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"http://www.yoctoproject.org/docs/current/kernel-dev/ker=
nel-dev.html#changing-the-configuration" target=3D"_blank">http://www.yocto=
project.org/docs/current/kernel-dev/kernel-dev.html#changing-the-configurat=
ion</a><br>



&gt;&gt;<br>
&gt;&gt; The strange thing is: My patch is applied but my defconfig, or con=
fig<br>
&gt;&gt; fragment is not used.<br>
&gt;&gt; I just want to add CONFIG_WATCHDOG_NOWAYOUT=3Dy.<br>
&gt;&gt;<br>
&gt;&gt; I already did a cleasstate but no success.<br>
&gt;&gt;<br>
&gt;&gt; Any hints?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Regards,<br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; *dS<br>
&gt;&gt; Diego Sueiro<br>
&gt;&gt;<br>
&gt;&gt; /*long live rock &#39;n roll*/<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; yocto mailing list<br>
&gt;&gt; <a href=3D"mailto:yocto@yoctoproject.org" target=3D"_blank">yocto@=
yoctoproject.org</a><br>
&gt;&gt; <a href=3D"https://lists.yoctoproject.org/listinfo/yocto" target=
=3D"_blank">https://lists.yoctoproject.org/listinfo/yocto</a><br>
&gt;&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; yocto mailing list<br>
&gt; <a href=3D"mailto:yocto@yoctoproject.org" target=3D"_blank">yocto@yoct=
oproject.org</a><br>
&gt; <a href=3D"https://lists.yoctoproject.org/listinfo/yocto" target=3D"_b=
lank">https://lists.yoctoproject.org/listinfo/yocto</a><br>
&gt;<br>
</div></div></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>

--089e0118460e8e112d04e8dfbf27--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bruce.ashfield@gmail.com>
Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com
	[209.85.217.181])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 4866BE016B2
	for <yocto@yoctoproject.org>; Wed, 16 Oct 2013 20:56:10 -0700 (PDT)
Received: by mail-lb0-f181.google.com with SMTP id x18so144407lbi.40
	for <yocto@yoctoproject.org>; Wed, 16 Oct 2013 20:56:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	bh=JA1XniYyr0ceMfUiBHCMbFfnsRvqFjGM94iCCO68aSM=;
	b=bGIEqNM8BPJ5w+lhYZyRUGoqWsnyGsoyvBCXRDGG0F/HHslyCoFQEdaWjDp76cG/Vw
	mFJEaNA5DOA6z3CGFjRot5WB1s8seUq+VVrZ9AowVV3v7CiPKkkbR4MFWuthX2L56Xq/
	SrAAkkAIuTC2jvwadtYT+YRRdiJU3kc4WDyGs9aoLK2PMS5b1lk1uOIfZtTAXIBXuqar
	KwzeqcKItXQXWtgqhZHLlO4UTeOisotcoZYdOo6OIl+5pOso2gaCewc4oaKTy9dTEfGi
	o4dtLDUsLPQxDT+m3xgcTW/3Cp9I7H+QKa8EIXs5uUX5C5jQLd71LOfGIiVfI25Tyvvi
	U/yQ==
MIME-Version: 1.0
X-Received: by 10.152.22.226 with SMTP id h2mr5449697laf.2.1381982169070; Wed,
	16 Oct 2013 20:56:09 -0700 (PDT)
Received: by 10.112.14.200 with HTTP; Wed, 16 Oct 2013 20:56:09 -0700 (PDT)
In-Reply-To: <CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
Date: Wed, 16 Oct 2013 23:56:09 -0400
Message-ID: <CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Diego Sueiro <diego.sueiro@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Rudolf Streif <rstreif@linuxfoundation.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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2013 03:56:11 -0000
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Oct 16, 2013 at 2:19 PM, Diego Sueiro <diego.sueiro@gmail.com> wrot=
e:
> Folks,
>
> Looking at log.do_unpack it shows:
>
> ...
> NOTE: Unpacking
> <...>/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline-3.8=
/beaglebone/defconfig
> to
> <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-g=
nueabi/linux-mainline/3.8.13-r23a/
> ...
>
> NOTE: Unpacking
> <...>/meta-mine/recipes-kernel/linux/linux-mainline-3.8/mine.patch to
> <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-g=
nueabi/linux-mainline/3.8.13-r23a/
> NOTE: Unpacking
> <...>/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline-3.8=
/beaglebone/defconfig
> to
> <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-g=
nueabi/linux-mainline/3.8.13-r23a/
>
>
> Note that it copies defconfig from meta-beagleboard and in the end, inste=
ad
> copying mine, it is copying from meta-beagleboard again.
>
> My layer has the priority higher than meta-beagleboard.

I can't get at my machines to test this myself (technically I'm still
on vacation), but when you
dump the bitbake environment, how many defconfig's show up in the
SRC_URI ? It would be
easy enough in your bbapend to simply call your defconfig something
else (i.e. defconfig-mine)
and override/append to kernel_do_configure() to simply copy yours over
top of the .config,
regardless of what the fetcher is doing with the SRC_URI.

Bruce

>
>
>
> Abra=C3=A7os,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br
>
> Engenheiro de Controle e Automa=C3=A7=C3=A3o
> UNIVERSIDADE FEDERAL DE ITAJUB=C3=80
>
>
> /*long live rock 'n roll*/
>
>
> 2013/10/16 Diego Sueiro <diego.sueiro@gmail.com>
>>
>> Guys,
>>
>> As I told before, I already tried the config fragment strategy and it di=
d
>> not worked too.
>>
>> Looking at linux-mailine-3.8.bb from meta-beagleboard[1] it just inherit=
s
>> kernel and not inherits linux-yocto or requires linux-yocto.inc. So I
>> believe that the config fragment will not work. But I can be wrong.
>>
>> On directory "meta-mine/recipes-kernel/linux/" I have this:
>>
>> .
>> =E2=94=9C=E2=94=80=E2=94=80 files
>> =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 mine.patch
>> =E2=94=82   =E2=94=94=E2=94=80=E2=94=80 defconfig
>> =E2=94=94=E2=94=80=E2=94=80 linux-mainline_3.8.bbappend
>>
>>
>> And my linux-mainline_3.8.bbappend recipe:
>>
>> FILESEXTRAPATHS_prepend :=3D "${THISDIR}/files:"
>> SRC_URI +=3D " file://mine.patch \
>>              file://defconfig \
>>              "
>>
>> The mine.patch is applied but defconfig not.
>>
>> I've already tried to use another FILESEXTRAPATHS layout like[2],but no
>> success too.
>>
>> How can I have the "bb" command listed on the following link?
>> http://www.crashcourse.ca/wiki/index.php/OE_FILESEXTRAPATHS
>>
>>
>> [1] -
>> https://github.com/beagleboard/meta-beagleboard/blob/dylan/common-bsp/re=
cipes-kernel/linux/linux-mainline_3.8.bb
>> [2] -
>> http://cgit.openembedded.org/meta-handheld/tree/recipes-kernel/linux/lin=
ux-yocto_3.10.bbappend
>>
>> Regards,
>>
>> --
>> *dS
>> Diego Sueiro
>>
>> /*long live rock 'n roll*/
>>
>>
>> 2013/10/15 Andrea Adami <andrea.adami@gmail.com>
>>>
>>> Hi,
>>>
>>> I guess you're setting a wrong FILESEXTRAPATHS_prepend :=3D
>>> "${THISDIR}/files:"
>>>
>>> See this example, using simple defconfig for some devices and an
>>> experimental configuration (WIP ;) fo others using fragments.
>>>
>>>
>>> http://cgit.openembedded.org/meta-handheld/tree/recipes-kernel/linux/li=
nux-yocto_3.10.bbappend
>>>
>>> Cheers
>>>
>>> Andrea
>>>
>>>
>>> On Tue, Oct 15, 2013 at 11:49 PM, Rudolf Streif
>>> <rstreif@linuxfoundation.org> wrote:
>>> > Diego,
>>> >
>>> > You are appending a kernel recipe that uses the Linux Yocto tooling.
>>> > The
>>> > defconfig is essentially comprised of many different pieces from the
>>> > meta
>>> > branch of the Yocto kernel repository and optional configuration
>>> > fragments
>>> > that you provide. This tooling will not recognize a defconfig file yo=
u
>>> > provide but it does recognize configuration fragments to be added to
>>> > .config.
>>> >
>>> > You need to put
>>> >
>>> > CONFIG_WATCHDOG_NOWAYOUT=3Dy
>>> >
>>> > into a file that ends with .cfg eg. watchdog.cfg and then modify your
>>> > bbappend to
>>> >
>>> > FILESEXTRAPATHS_prepend :=3D "${THISDIR}/files:"
>>> > SRC_URI +=3D " file://0019-mine.patch \
>>> >              file://watchdog.cfg \
>>> >              "
>>> >
>>> > Rudi
>>> >
>>> >
>>> >
>>> > On Tue, Oct 15, 2013 at 2:07 PM, Diego Sueiro <diego.sueiro@gmail.com=
>
>>> > wrote:
>>> >>
>>> >> Folks,
>>> >>
>>> >> I created the following bbapend recipe for linux-mainline_3.8.bb (fr=
om
>>> >> meta-beagleboard on dylan branch) for beaglebone.
>>> >> meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
>>> >>
>>> >> FILESEXTRAPATHS_prepend :=3D "${THISDIR}/files:"
>>> >> SRC_URI +=3D " file://0019-mine.patch \
>>> >>              file://defconfig \
>>> >>              "
>>> >>
>>> >> But the defconfig and .config files on ${S} and ${WORKDIR} used are
>>> >> from
>>> >> meta-beagleboad, not from my bbappend.
>>> >>
>>> >> I tried to follow the instructions to add config fragments on the pa=
ge
>>> >> below but it did not worked too.
>>> >>
>>> >>
>>> >> http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#=
changing-the-configuration
>>> >>
>>> >> The strange thing is: My patch is applied but my defconfig, or confi=
g
>>> >> fragment is not used.
>>> >> I just want to add CONFIG_WATCHDOG_NOWAYOUT=3Dy.
>>> >>
>>> >> I already did a cleasstate but no success.
>>> >>
>>> >> Any hints?
>>> >>
>>> >>
>>> >> Regards,
>>> >>
>>> >> --
>>> >> *dS
>>> >> Diego Sueiro
>>> >>
>>> >> /*long live rock 'n roll*/
>>> >>
>>> >> _______________________________________________
>>> >> yocto mailing list
>>> >> yocto@yoctoproject.org
>>> >> https://lists.yoctoproject.org/listinfo/yocto
>>> >>
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > yocto mailing list
>>> > yocto@yoctoproject.org
>>> > https://lists.yoctoproject.org/listinfo/yocto
>>> >
>>
>>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



--=20
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"


From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <diego.sueiro@gmail.com>
Received: from mail-ob0-f170.google.com (mail-ob0-f170.google.com
	[209.85.214.170])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 0CED4E016C1
	for <yocto@yoctoproject.org>; Thu, 17 Oct 2013 03:39:32 -0700 (PDT)
Received: by mail-ob0-f170.google.com with SMTP id gq1so1707967obb.1
	for <yocto@yoctoproject.org>; Thu, 17 Oct 2013 03:39:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=dOL7w/41382o5xHd8ocjjFnOrCrItI68QiO4L7+/69c=;
	b=GGddMZkkKoNL9dBJ2PExHcgK+d2R7aYreix+8IEXwHWqQ2xmSlaBP5Jp5j90UDNKKa
	u1gTDJ6Mo2kxrLQPBmFpPnb2ft/K4hv62sqYdAhbArWDoGUyTuetAUvAHZybvV4KYIY8
	HPrFDfRnhFdrqE9nxsjjxALEisba8LVciPI/glXm56ecWIJ748g3GtmP7eOJ2GL86PWq
	osF/xkgqJHk3cvkAb2y1BPs2lvXCAHmw+ydV4rtyBirGwY/AbpC5zqrxY+67KXgjwrB3
	Z/sCMj4dcGu8DsUkI2C/poHz6SfxjXDjds3vWYdcSJr5S88xxtFpj2QVeR0z+iM02crN
	BG4A==
X-Received: by 10.182.176.38 with SMTP id cf6mr12589123obc.11.1382006371397;
	Thu, 17 Oct 2013 03:39:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.120.65 with HTTP; Thu, 17 Oct 2013 03:39:10 -0700 (PDT)
In-Reply-To: <CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
From: Diego Sueiro <diego.sueiro@gmail.com>
Date: Thu, 17 Oct 2013 07:39:10 -0300
Message-ID: <CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Rudolf Streif <rstreif@linuxfoundation.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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2013 10:39:35 -0000
Content-Type: multipart/alternative; boundary=e89a8ff1cf72d8376304e8ed6eb0

--e89a8ff1cf72d8376304e8ed6eb0
Content-Type: text/plain; charset=ISO-8859-1

2013/10/17 Bruce Ashfield <bruce.ashfield@gmail.com>

> On Wed, Oct 16, 2013 at 2:19 PM, Diego Sueiro <diego.sueiro@gmail.com>
> wrote:
> > Folks,
> >
> > Looking at log.do_unpack it shows:
> >
> > ...
> > NOTE: Unpacking
> >
> <...>/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline-3.8/beaglebone/defconfig
> > to
> >
> <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.13-r23a/
> > ...
> >
> > NOTE: Unpacking
> > <...>/meta-mine/recipes-kernel/linux/linux-mainline-3.8/mine.patch to
> >
> <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.13-r23a/
> > NOTE: Unpacking
> >
> <...>/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline-3.8/beaglebone/defconfig
> > to
> >
> <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.13-r23a/
> >
> >
> > Note that it copies defconfig from meta-beagleboard and in the end,
> instead
> > copying mine, it is copying from meta-beagleboard again.
> >
> > My layer has the priority higher than meta-beagleboard.
>
> I can't get at my machines to test this myself (technically I'm still
> on vacation), but when you
> dump the bitbake environment, how many defconfig's show up in the
> SRC_URI ? It would be
> easy enough in your bbapend to simply call your defconfig something
> else (i.e. defconfig-mine)
> and override/append to kernel_do_configure() to simply copy yours over
> top of the .config,
> regardless of what the fetcher is doing with the SRC_URI.
>
> Bruce
>
>
Bruce,

Putting the following in my recipe did the trick:

do_configure_prepend() {
            cp ${WORKDIR}/defconfig-mine ${WORKDIR}/defconfig
}


Now the .config is the same as my custom defconfig.

But, this is a workaround, right?
I expected to get this working "out-of-box".
Why config fragments did not worked too?



--
*dS
Diego Sueiro

/*long live rock 'n roll*/

--e89a8ff1cf72d8376304e8ed6eb0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br>
<br><br><div class=3D"gmail_quote">2013/10/17 Bruce Ashfield <span dir=3D"l=
tr">&lt;<a href=3D"mailto:bruce.ashfield@gmail.com" target=3D"_blank">bruce=
.ashfield@gmail.com</a>&gt;</span><br><blockquote class=3D"gmail_quote" sty=
le=3D"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 class=3D"im">On Wed, Oct 16, 2013 at 2:19 PM, Diego Sueiro &lt;<a href=
=3D"mailto:diego.sueiro@gmail.com">diego.sueiro@gmail.com</a>&gt; wrote:<br=
>
&gt; Folks,<br>
&gt;<br>
</div><div class=3D"im">&gt; Looking at log.do_unpack it shows:<br>
&gt;<br>
&gt; ...<br>
&gt; NOTE: Unpacking<br>
&gt; &lt;...&gt;/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mai=
nline-3.8/beaglebone/defconfig<br>
&gt; to<br>
&gt; &lt;...&gt;/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstro=
m-linux-gnueabi/linux-mainline/3.8.13-r23a/<br>
&gt; ...<br>
&gt;<br>
&gt; NOTE: Unpacking<br>
&gt; &lt;...&gt;/meta-mine/recipes-kernel/linux/linux-mainline-3.8/mine.pat=
ch to<br>
&gt; &lt;...&gt;/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstro=
m-linux-gnueabi/linux-mainline/3.8.13-r23a/<br>
&gt; NOTE: Unpacking<br>
&gt; &lt;...&gt;/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mai=
nline-3.8/beaglebone/defconfig<br>
&gt; to<br>
&gt; &lt;...&gt;/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstro=
m-linux-gnueabi/linux-mainline/3.8.13-r23a/<br>
&gt;<br>
&gt;<br>
&gt; Note that it copies defconfig from meta-beagleboard and in the end, in=
stead<br>
&gt; copying mine, it is copying from meta-beagleboard again.<br>
&gt;<br>
&gt; My layer has the priority higher than meta-beagleboard.<br>
<br>
</div>I can&#39;t get at my machines to test this myself (technically I&#39=
;m still<br>
on vacation), but when you<br>
dump the bitbake environment, how many defconfig&#39;s show up in the<br>
SRC_URI ? It would be<br>
easy enough in your bbapend to simply call your defconfig something<br>
else (i.e. defconfig-mine)<br>
and override/append to kernel_do_configure() to simply copy yours over<br>
top of the .config,<br>
regardless of what the fetcher is doing with the SRC_URI.<br>
<br>
Bruce<br>
<div class=3D""><div class=3D"h5"><br></div></div></blockquote><div><br></d=
iv><div>Bruce,</div><div><br></div><div style>Putting the following in my r=
ecipe did the trick:</div><div style><div><br></div></div></div></div><bloc=
kquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px">

<div class=3D"gmail_extra" style><div class=3D"gmail_quote" style><div styl=
e><div style>do_configure_prepend() {</div></div></div></div><div class=3D"=
gmail_extra" style><div class=3D"gmail_quote" style><div style><div style>=
=A0 =A0 =A0 =A0 =A0 =A0 cp ${WORKDIR}/defconfig-mine ${WORKDIR}/defconfig</=
div>

</div></div></div><div class=3D"gmail_extra" style><div class=3D"gmail_quot=
e" style><div style><div style>}</div></div></div></div></blockquote><div c=
lass=3D"gmail_extra"><div class=3D"gmail_quote"><div style><div><br></div><=
div style>

Now the .config is the same as my custom defconfig.</div><div style><br></d=
iv><div style>But, this is a workaround, right?</div><div style>I expected =
to get this working &quot;out-of-box&quot;.</div><div style>Why config frag=
ments did not worked too?</div>

<div style><br></div><div><br></div></div><div><br class=3D"">--<br>*dS<br>=
Diego Sueiro<br><br>/*long live rock &#39;n roll*/<br></div></div></div></d=
iv>

--e89a8ff1cf72d8376304e8ed6eb0--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Bruce.Ashfield@windriver.com>
Received: from mail.windriver.com (mail.windriver.com [147.11.1.11])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 17179E016C4
	for <yocto@yoctoproject.org>; Thu, 17 Oct 2013 05:50:31 -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 r9HCoQYi004902
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
	Thu, 17 Oct 2013 05:50:26 -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;
	Thu, 17 Oct 2013 05:50:25 -0700
Message-ID: <525FDD08.90400@windriver.com>
Date: Thu, 17 Oct 2013 08:50:16 -0400
From: Bruce Ashfield <bruce.ashfield@windriver.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Diego Sueiro <diego.sueiro@gmail.com>, Bruce Ashfield
	<bruce.ashfield@gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
In-Reply-To: <CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Rudolf Streif <rstreif@linuxfoundation.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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2013 12:50:32 -0000
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

On 13-10-17 06:39 AM, Diego Sueiro wrote:
>
>
>
> 2013/10/17 Bruce Ashfield <bruce.ashfield@gmail.com
> <mailto:bruce.ashfield@gmail.com>>
>
>     On Wed, Oct 16, 2013 at 2:19 PM, Diego Sueiro
>     <diego.sueiro@gmail.com <mailto:diego.sueiro@gmail.com>> wrote:
>      > Folks,
>      >
>      > Looking at log.do_unpack it shows:
>      >
>      > ...
>      > NOTE: Unpacking
>      >
>     <...>/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline-3.8/beaglebone/defconfig
>      > to
>      >
>     <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.13-r23a/
>      > ...
>      >
>      > NOTE: Unpacking
>      > <...>/meta-mine/recipes-kernel/linux/linux-mainline-3.8/mine.patch to
>      >
>     <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.13-r23a/
>      > NOTE: Unpacking
>      >
>     <...>/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline-3.8/beaglebone/defconfig
>      > to
>      >
>     <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.13-r23a/
>      >
>      >
>      > Note that it copies defconfig from meta-beagleboard and in the
>     end, instead
>      > copying mine, it is copying from meta-beagleboard again.
>      >
>      > My layer has the priority higher than meta-beagleboard.
>
>     I can't get at my machines to test this myself (technically I'm still
>     on vacation), but when you
>     dump the bitbake environment, how many defconfig's show up in the
>     SRC_URI ? It would be
>     easy enough in your bbapend to simply call your defconfig something
>     else (i.e. defconfig-mine)
>     and override/append to kernel_do_configure() to simply copy yours over
>     top of the .config,
>     regardless of what the fetcher is doing with the SRC_URI.
>
>     Bruce
>
>
> Bruce,
>
> Putting the following in my recipe did the trick:
>
>     do_configure_prepend() {
>                  cp ${WORKDIR}/defconfig-mine ${WORKDIR}/defconfig
>     }
>
>
> Now the .config is the same as my custom defconfig.
>
> But, this is a workaround, right?

I could be. Until we root cause the issue, I can't say for sure.

> I expected to get this working "out-of-box".

Did you do a  "bitbake -e <your kernel recipe>" ? and then look at
the SRC_URI ? That will tell us if for some reason the beagle layer's
defconfig is on there twice.

> Why config fragments did not worked too?

recipes must inherit linux-yocto to get that support, since it is
optional and not something we force on all kernel recipes. So if you
want fragment support, creating your own kernel recipe, based on the
one in the layers you are using, which inherits linux-yocto is one
route to take.

Bruce

>
>
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <diego.sueiro@gmail.com>
Received: from mail-ie0-f175.google.com (mail-ie0-f175.google.com
	[209.85.223.175])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 5B0CFE016C4
	for <yocto@yoctoproject.org>; Thu, 17 Oct 2013 06:16:06 -0700 (PDT)
Received: by mail-ie0-f175.google.com with SMTP id aq17so3888204iec.34
	for <yocto@yoctoproject.org>; Thu, 17 Oct 2013 06:16:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=wEfnaYPVPTjb1dJY+70Acbi6KlrE6k88Ewd/Z2e7fdU=;
	b=rnQLd6TEe6apUVhWFd/q5A4xIo821hrUG44rZBIs9JPVt+R6Lo+VFHo1ZT7+mGS0oF
	UW1k1OShHDOi2TLe3aHA+R7XQjVrqAyklwl/hYuWwvFQaL0MHmOsVWidMMXqWd7MAa/H
	HtkUHyW0jnaddcLgfYXxkU1mmAB0pmBzPCn2k40nYY5nE0JP1sFQGnZPfDWkvkLxj5+z
	ue1qKhdzPznkmNsYVzSy204Ttg+TvCWvAEAeHaNfv1bGk+gM+aJdjeBDVrwPb0z2pw6G
	dMVLum1eKHMOXVElSNKzyUlzmyNRYZcfyu0izH+lfkAmpzZAYYp5YwCdD1d5LagdSqAH
	9YLA==
X-Received: by 10.42.18.136 with SMTP id x8mr5345448ica.11.1382015765149; Thu,
	17 Oct 2013 06:16:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.26.233 with HTTP; Thu, 17 Oct 2013 06:15:45 -0700 (PDT)
In-Reply-To: <525FDD08.90400@windriver.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
From: Diego Sueiro <diego.sueiro@gmail.com>
Date: Thu, 17 Oct 2013 10:15:45 -0300
Message-ID: <CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Rudolf Streif <rstreif@linuxfoundation.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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2013 13:16:07 -0000
Content-Type: multipart/alternative; boundary=20cf303f6910c1c58d04e8ef9e67

--20cf303f6910c1c58d04e8ef9e67
Content-Type: text/plain; charset=ISO-8859-1

2013/10/17 Bruce Ashfield <bruce.ashfield@windriver.com>

>
>
>  I expected to get this working "out-of-box".
>>
>
> Did you do a  "bitbake -e <your kernel recipe>" ? and then look at
> the SRC_URI ? That will tell us if for some reason the beagle layer's
> defconfig is on there twice.


I'll do it after my current build gets finished.


>
>
>  Why config fragments did not worked too?
>>
>
> recipes must inherit linux-yocto to get that support, since it is
> optional and not something we force on all kernel recipes. So if you
> want fragment support, creating your own kernel recipe, based on the
> one in the layers you are using, which inherits linux-yocto is one
> route to take.

Can I do it on bbappend, or do I need to copy the entirely
linux-mainline_3.8.bb from meta-bleagleboard to my layer and add "inherit
linux-yocto"?
Do I need to "inherit linux-yocto", "require
recipes-kernel/linux/linux-yocto.inc" or "inherit kernel-yocto"?
My concern is: if doing this to just have the config fragment feature, I'll
possibly mess up the kernel build.


Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/

--20cf303f6910c1c58d04e8ef9e67
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
2013/10/17 Bruce Ashfield <span dir=3D"ltr">&lt;<a href=3D"mailto:bruce.ash=
field@windriver.com" target=3D"_blank">bruce.ashfield@windriver.com</a>&gt;=
</span><br>


<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
I expected to get this working &quot;out-of-box&quot;.<br>
</blockquote>
<br></div>
Did you do a =A0&quot;bitbake -e &lt;your kernel recipe&gt;&quot; ? and the=
n look at<br>
the SRC_URI ? That will tell us if for some reason the beagle layer&#39;s<b=
r>
defconfig is on there twice.</blockquote><div>=A0</div><div>I&#39;ll do it =
after my current build gets finished.</div><div>=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">


<div><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
Why config fragments did not worked too?<br>
</blockquote>
<br></div>
recipes must inherit linux-yocto to get that support, since it is<br>
optional and not something we force on all kernel recipes. So if you<br>
want fragment support, creating your own kernel recipe, based on the<br>
one in the layers you are using, which inherits linux-yocto is one<br>
route to take.</blockquote></div>Can I do it on bbappend, or do I need to c=
opy the entirely <a href=3D"http://linux-mainline_3.8.bb">linux-mainline_3.=
8.bb</a> from meta-bleagleboard to my layer and add &quot;inherit linux-yoc=
to&quot;?<br>


Do I need to &quot;inherit linux-yocto&quot;, &quot;require recipes-kernel/=
linux/linux-yocto.inc&quot; or &quot;inherit kernel-yocto&quot;?</div><div =
class=3D"gmail_extra">My concern is: if doing this to just have the config =
fragment feature, I&#39;ll possibly mess up the kernel build.</div>


<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br clear=
=3D"all"><div><div dir=3D"ltr"><div>Regards,</div><div><br></div>--<br>*dS<=
br>Diego Sueiro<br><br>/*long live rock &#39;n roll*/</div></div>
</div></div>

--20cf303f6910c1c58d04e8ef9e67--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Bruce.Ashfield@windriver.com>
Received: from mail.windriver.com (mail.windriver.com [147.11.1.11])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 42562E016C5
	for <yocto@yoctoproject.org>; Thu, 17 Oct 2013 06:19:19 -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 r9HDJF4I013150
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
	Thu, 17 Oct 2013 06:19:15 -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;
	Thu, 17 Oct 2013 06:19:15 -0700
Message-ID: <525FE3C9.3070003@windriver.com>
Date: Thu, 17 Oct 2013 09:19:05 -0400
From: Bruce Ashfield <bruce.ashfield@windriver.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Diego Sueiro <diego.sueiro@gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
In-Reply-To: <CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Rudolf Streif <rstreif@linuxfoundation.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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2013 13:19:22 -0000
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

On 13-10-17 09:15 AM, Diego Sueiro wrote:
>
> 2013/10/17 Bruce Ashfield <bruce.ashfield@windriver.com
> <mailto:bruce.ashfield@windriver.com>>
>
>
>
>         I expected to get this working "out-of-box".
>
>
>     Did you do a  "bitbake -e <your kernel recipe>" ? and then look at
>     the SRC_URI ? That will tell us if for some reason the beagle layer's
>     defconfig is on there twice.
>
> I'll do it after my current build gets finished.
>
>
>
>         Why config fragments did not worked too?
>
>
>     recipes must inherit linux-yocto to get that support, since it is
>     optional and not something we force on all kernel recipes. So if you
>     want fragment support, creating your own kernel recipe, based on the
>     one in the layers you are using, which inherits linux-yocto is one
>     route to take.
>
> Can I do it on bbappend, or do I need to copy the entirely
> linux-mainline_3.8.bb <http://linux-mainline_3.8.bb> from
> meta-bleagleboard to my layer and add "inherit linux-yocto"?
> Do I need to "inherit linux-yocto", "require
> recipes-kernel/linux/linux-yocto.inc" or "inherit kernel-yocto"?

Look at oe-core/meta-skeleton for the custom kernel recipe example.
It has the inherit/include combinations that you need to follow.

> My concern is: if doing this to just have the config fragment feature,
> I'll possibly mess up the kernel build.

It shouldn't. It only adds to existing phases, and doesn't make
any changes. I've tested it in many combinations and it should
work fine.

If something breaks, I'd like to know, so we can fix it.

Bruce

>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/



From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <andrea.adami@gmail.com>
Received: from mail-la0-f49.google.com (mail-la0-f49.google.com
	[209.85.215.49])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 7365FE016C4
	for <yocto@yoctoproject.org>; Thu, 17 Oct 2013 06:51:36 -0700 (PDT)
Received: by mail-la0-f49.google.com with SMTP id ev20so1841866lab.22
	for <yocto@yoctoproject.org>; Thu, 17 Oct 2013 06:51:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=E+DflYtuQ3clPiVfDVQpfl7k3IFeB2dmIShPX6OD438=;
	b=jc+U4sjUewuJfijkcclieYG6ye5JdEJsRaIjoumKWdvOUuEI1Og5ayaAWpsur88Ejc
	3d0SxkrgG9C9TAmhVNatWhIk8hfW9vgyJbHHfrwJVknXrxZ8AxIafBXvLiL6E/HieKya
	70qnYyLDUWdXaWvmSdxkH1GZvI19QEAGkLOWcnKKwRktcGk/FzYhSD05yOJ8j7ez41Eg
	mvz4Uo2m8kNCfxBT3FWty7FmJShvUS4xCEfvbpvLSxVKJk2LAwlGsfcs7Dx8jH4hYuUk
	zT5UlaicSWjGSuEaeriRzb+BWPDAzSBO0P2ncICVy+w43VpZ6qnbS2Jz8gTBjcqES/+L
	OYKA==
MIME-Version: 1.0
X-Received: by 10.112.182.7 with SMTP id ea7mr64792lbc.63.1382017895202; Thu,
	17 Oct 2013 06:51:35 -0700 (PDT)
Received: by 10.112.52.74 with HTTP; Thu, 17 Oct 2013 06:51:35 -0700 (PDT)
In-Reply-To: <525FE3C9.3070003@windriver.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
Date: Thu, 17 Oct 2013 15:51:35 +0200
Message-ID: <CAAQYJAtzSheOwBecK+SqgnRFQd8Uhq4RZHhEi855fVurirjOZQ@mail.gmail.com>
From: Andrea Adami <andrea.adami@gmail.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Rudolf Streif <rstreif@linuxfoundation.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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2013 13:51:37 -0000
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Oct 17, 2013 at 3:19 PM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> On 13-10-17 09:15 AM, Diego Sueiro wrote:
>>
>>
>> 2013/10/17 Bruce Ashfield <bruce.ashfield@windriver.com
>> <mailto:bruce.ashfield@windriver.com>>
>>
>>
>>
>>
>>         I expected to get this working "out-of-box".
>>
>>
>>     Did you do a  "bitbake -e <your kernel recipe>" ? and then look at
>>     the SRC_URI ? That will tell us if for some reason the beagle layer's
>>     defconfig is on there twice.
>>
>> I'll do it after my current build gets finished.
>>
>>
>>
>>         Why config fragments did not worked too?
>>
>>
>>     recipes must inherit linux-yocto to get that support, since it is
>>     optional and not something we force on all kernel recipes. So if you
>>     want fragment support, creating your own kernel recipe, based on the
>>     one in the layers you are using, which inherits linux-yocto is one
>>     route to take.
>>
>> Can I do it on bbappend, or do I need to copy the entirely
>> linux-mainline_3.8.bb <http://linux-mainline_3.8.bb> from
>>
>> meta-bleagleboard to my layer and add "inherit linux-yocto"?
>> Do I need to "inherit linux-yocto", "require
>> recipes-kernel/linux/linux-yocto.inc" or "inherit kernel-yocto"?
>
>
> Look at oe-core/meta-skeleton for the custom kernel recipe example.
> It has the inherit/include combinations that you need to follow.
>
>
>> My concern is: if doing this to just have the config fragment feature,
>> I'll possibly mess up the kernel build.
>
>
> It shouldn't. It only adds to existing phases, and doesn't make
> any changes. I've tested it in many combinations and it should
> work fine.
>
> If something breaks, I'd like to know, so we can fix it.
>
> Bruce
>
>
>>
>>
>> Regards,
>>
>> --
>> *dS
>> Diego Sueiro
>>
>> /*long live rock 'n roll*/
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

As a final note, the defconfig is overwritten by the
do_configure_prepend() code in linux.inc.
This is how kernel recipes did work before linux-yocto.

Cheers

Andrea


From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <diego.sueiro@gmail.com>
Received: from mail-ie0-f174.google.com (mail-ie0-f174.google.com
	[209.85.223.174])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 3A611E01653
	for <yocto@yoctoproject.org>; Thu, 17 Oct 2013 08:47:32 -0700 (PDT)
Received: by mail-ie0-f174.google.com with SMTP id qd12so4228525ieb.33
	for <yocto@yoctoproject.org>; Thu, 17 Oct 2013 08:47:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=AumWClcWoyJTCg7OnurGEBt3zEiGlTxTq2vTVLP8H8o=;
	b=H7ZmC4wl0/sxeuMsyv39wMNsUooIR2t71JeSFZ4yknqQPk8j7K/ErSf1ixKHUBSfFd
	mW9tDB/xopJsKmaMTqxTlTCoLLk9/u1HCU5u/Qz5AMwNmZwt7GoKEHKO1LkduygOOtnk
	a5MI+TnT/7813cJOKM/vceslRZ2hcJchA7OU63cm+re/6xsEi2/nuOEGNrteJ6H/HjXA
	VCD1v1RRyR59EO9dG+ZCkYF2KIFDI+EM/V4Cug97HuT4x2ZPTP8DRP6pLUMXM3XF5/ga
	YnJWbiwFvXrvRqS2fEb3gsyIEjzxzLoX4odEaN06+8FGdy3k/daakMgnyT8GVjak8pSG
	6a4g==
X-Received: by 10.43.77.212 with SMTP id zj20mr5856999icb.5.1382024851265;
	Thu, 17 Oct 2013 08:47:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.26.233 with HTTP; Thu, 17 Oct 2013 08:47:10 -0700 (PDT)
In-Reply-To: <525FE3C9.3070003@windriver.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
From: Diego Sueiro <diego.sueiro@gmail.com>
Date: Thu, 17 Oct 2013 12:47:10 -0300
Message-ID: <CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Rudolf Streif <rstreif@linuxfoundation.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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2013 15:47:37 -0000
Content-Type: multipart/alternative; boundary=047d7b45041e54a3f504e8f1bce0

--047d7b45041e54a3f504e8f1bce0
Content-Type: text/plain; charset=ISO-8859-1

2013/10/17 Bruce Ashfield <bruce.ashfield@windriver.com>

> Look at oe-core/meta-skeleton for the custom kernel recipe example.
> It has the inherit/include combinations that you need to follow.
>
>
>  My concern is: if doing this to just have the config fragment feature,
>> I'll possibly mess up the kernel build.
>>
>
> It shouldn't. It only adds to existing phases, and doesn't make
> any changes. I've tested it in many combinations and it should
> work fine.
>
> If something breaks, I'd like to know, so we can fix it.
>

Bruce,

I didn't change linux-mainline_3.8.bb.
My linux-mainline_3.8.bbappend is:

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.8:"
inherit kernel
require recipes-kernel/linux/linux-yocto.inc
COMPATIBLE_MACHINE_beaglebone = "(beaglebone)"
SRC_URI += " file://mine.patch \
             file://config-addons.cfg \
             "

My config-addons.cfg:

CONFIG_WATCHDOG_NOWAYOUT=y
CONFIG_NTFS_FS=y
CONFIG_NTFS_RW=y

After a cleansstate the build got stucked on do_patch task.
Here is the content of log.do_patch:

DEBUG: Executing shell function do_patch
WARNING: no meta data branch found ...
Switched to branch 'linux-3.8.y'


Running with bitbake -v I got the following:

...
+ configme --reconfig --output
<...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.13-r23a/linux-beaglebone-standard-build
standard beaglebone
[INFO] Configuring target/machine combo: "standard/beaglebone"

[INFO] Configuring target/machine combo: "standard/beaglebone"
[INFO] collecting configs in ./meta/meta-series

[INFO] collecting configs in ./meta/meta-series
cat: meta/cfg/standard/beaglebone/config_frag.txt: No such file or directory

cat: meta/cfg/standard/beaglebone/config_frag.txt: No such file or directory
cat: meta/cfg/standard/beaglebone/config_frag.txt: No such file or directory

cat: meta/cfg/standard/beaglebone/config_frag.txt: No such file or directory
mv: target `3.8.13' is not a directory

mv: target `3.8.13' is not a directory
creation of pre-processed config data failed
config of "standard/beaglebone" failed

creation of pre-processed config data failed
config of "standard/beaglebone" failed
ERROR: Function failed: do_kernel_configme (see
<...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.13-r23a/temp/log.do_kernel_configme15450.
for further information)
ERROR: Task 7
(<...>/setup-scripts/sources/meta-beagleboard/common-bsp/recipes-kernel/linux/
linux-mainline_3.8.bb, do_kernel_configme) failed with exit code '1'





Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/

--047d7b45041e54a3f504e8f1bce0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
2013/10/17 Bruce Ashfield <span dir=3D"ltr">&lt;<a href=3D"mailto:bruce.ash=
field@windriver.com" target=3D"_blank">bruce.ashfield@windriver.com</a>&gt;=
</span><br>


<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div style=3D"overflow:hidden">Look at oe-core/meta-skelet=
on for the custom kernel recipe example.<br>



It has the inherit/include combinations that you need to follow.<div><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
My concern is: if doing this to just have the config fragment feature,<br>
I&#39;ll possibly mess up the kernel build.<br>
</blockquote>
<br></div>
It shouldn&#39;t. It only adds to existing phases, and doesn&#39;t make<br>
any changes. I&#39;ve tested it in many combinations and it should<br>
work fine.<br>
<br>
If something breaks, I&#39;d like to know, so we can fix it.</div></blockqu=
ote></div><br>Bruce,</div><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra">I didn&#39;t change <a href=3D"http://linux-mainline_3.8.b=
b">linux-mainline_3.8.bb</a>.=A0</div>


<div class=3D"gmail_extra">My=A0linux-mainline_3.8.bbappend is:</div><div c=
lass=3D"gmail_extra"><blockquote style=3D"margin:0px 0px 0px 40px;border:no=
ne;padding:0px"><div class=3D"gmail_extra"><div class=3D"gmail_extra">
FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/${PN}-3.8:&quot;</div><div cl=
ass=3D"gmail_extra">inherit kernel<br></div><div class=3D"gmail_extra">requ=
ire recipes-kernel/linux/linux-yocto.inc</div><div class=3D"gmail_extra">CO=
MPATIBLE_MACHINE_beaglebone =3D &quot;(beaglebone)&quot;<br>


</div><div class=3D"gmail_extra">SRC_URI +=3D &quot; file://mine.patch \<br=
></div><div class=3D"gmail_extra">=A0 =A0 =A0 =A0 =A0 =A0 =A0file://config-=
addons.cfg \</div><div class=3D"gmail_extra">=A0 =A0 =A0 =A0 =A0 =A0 =A0&qu=
ot;</div></div></blockquote>My config-addons.cfg:<br>


</div><div class=3D"gmail_extra"><blockquote style=3D"margin:0px 0px 0px 40=
px;border:none;padding:0px"><div class=3D"gmail_extra" style><div class=3D"=
gmail_extra">CONFIG_WATCHDOG_NOWAYOUT=3Dy</div><div class=3D"gmail_extra">C=
ONFIG_NTFS_FS=3Dy</div>

<div class=3D"gmail_extra">CONFIG_NTFS_RW=3Dy</div><div><br></div></div></b=
lockquote></div><div class=3D"gmail_extra">After a cleansstate the build go=
t stucked on do_patch task.</div><div class=3D"gmail_extra">Here is the con=
tent of log.do_patch:</div>

<div class=3D"gmail_extra"><blockquote style=3D"margin:0px 0px 0px 40px;bor=
der:none;padding:0px">
<div class=3D"gmail_extra"><div class=3D"gmail_extra">DEBUG: Executing shel=
l function do_patch</div><div class=3D"gmail_extra">WARNING: no meta data b=
ranch found ...</div><div class=3D"gmail_extra">Switched to branch &#39;lin=
ux-3.8.y&#39;</div>


</div></blockquote></div><div class=3D"gmail_extra"><br></div><div class=3D=
"gmail_extra">Running with bitbake -v I got the following:</div><div class=
=3D"gmail_extra"><blockquote style=3D"margin:0px 0px 0px 40px;border:none;p=
adding:0px">


<div class=3D"gmail_extra"><div class=3D"gmail_extra">...</div><div class=
=3D"gmail_extra">+ configme --reconfig --output &lt;...&gt;/build/tmp-angst=
rom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3=
.8.13-r23a/linux-beaglebone-standard-build standard beaglebone</div>


<div class=3D"gmail_extra">[INFO] Configuring target/machine combo: &quot;s=
tandard/beaglebone&quot;</div><div class=3D"gmail_extra"><br></div><div cla=
ss=3D"gmail_extra">[INFO] Configuring target/machine combo: &quot;standard/=
beaglebone&quot;</div>


<div class=3D"gmail_extra">[INFO] collecting configs in ./meta/meta-series<=
/div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">[INFO]=
 collecting configs in ./meta/meta-series</div><div class=3D"gmail_extra">c=
at: meta/cfg/standard/beaglebone/config_frag.txt: No such file or directory=
</div>


<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">cat: meta/c=
fg/standard/beaglebone/config_frag.txt: No such file or directory</div><div=
 class=3D"gmail_extra">cat: meta/cfg/standard/beaglebone/config_frag.txt: N=
o such file or directory</div>


<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">cat: meta/c=
fg/standard/beaglebone/config_frag.txt: No such file or directory</div><div=
 class=3D"gmail_extra">mv: target `3.8.13&#39; is not a directory</div><div=
 class=3D"gmail_extra">


<br></div><div class=3D"gmail_extra">mv: target `3.8.13&#39; is not a direc=
tory</div><div class=3D"gmail_extra">creation of pre-processed config data =
failed</div><div class=3D"gmail_extra">config of &quot;standard/beaglebone&=
quot; failed</div>


<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">creation of=
 pre-processed config data failed</div><div class=3D"gmail_extra">config of=
 &quot;standard/beaglebone&quot; failed</div><div class=3D"gmail_extra">ERR=
OR: Function failed: do_kernel_configme (see &lt;...&gt;/build/tmp-angstrom=
_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.=
13-r23a/temp/log.do_kernel_configme15450. for further information)</div>


<div class=3D"gmail_extra">ERROR: Task 7 (&lt;...&gt;/setup-scripts/sources=
/meta-beagleboard/common-bsp/recipes-kernel/linux/<a href=3D"http://linux-m=
ainline_3.8.bb">linux-mainline_3.8.bb</a>, do_kernel_configme) failed with =
exit code &#39;1&#39;<br>


</div></div></blockquote></div><div class=3D"gmail_extra"><br></div><div cl=
ass=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br><br clear=3D"a=
ll"><div><div dir=3D"ltr"><div>Regards,</div><div><br></div>--<br>*dS<br>
Diego Sueiro<br><br>/*long live rock &#39;n roll*/<br></div></div>
</div></div>

--047d7b45041e54a3f504e8f1bce0--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Bruce.Ashfield@windriver.com>
Received: from mail.windriver.com (mail.windriver.com [147.11.1.11])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 81041E016D7
	for <yocto@yoctoproject.org>; Thu, 17 Oct 2013 21:48:45 -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 r9I4mdFr005169
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
	Thu, 17 Oct 2013 21:48:40 -0700 (PDT)
Received: from bruce-ashfields-macbook.local (128.224.23.237) by
	ALA-HCA.corp.ad.wrs.com (147.11.189.40) with Microsoft SMTP Server id
	14.2.347.0; Thu, 17 Oct 2013 21:48:39 -0700
Message-ID: <5260BDA6.4020807@windriver.com>
Date: Fri, 18 Oct 2013 00:48:38 -0400
From: Bruce Ashfield <bruce.ashfield@windriver.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
	rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Diego Sueiro <diego.sueiro@gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
In-Reply-To: <CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Rudolf Streif <rstreif@linuxfoundation.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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Oct 2013 04:48:46 -0000
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

On 13-10-17 11:47 AM, Diego Sueiro wrote:
>
> 2013/10/17 Bruce Ashfield <bruce.ashfield@windriver.com
> <mailto:bruce.ashfield@windriver.com>>
>
>     Look at oe-core/meta-skeleton for the custom kernel recipe example.
>     It has the inherit/include combinations that you need to follow.
>
>
>         My concern is: if doing this to just have the config fragment
>         feature,
>         I'll possibly mess up the kernel build.
>
>
>     It shouldn't. It only adds to existing phases, and doesn't make
>     any changes. I've tested it in many combinations and it should
>     work fine.
>
>     If something breaks, I'd like to know, so we can fix it.
>
>
> Bruce,
>
> I didn't change linux-mainline_3.8.bb <http://linux-mainline_3.8.bb>.
> My linux-mainline_3.8.bbappend is:
>
>     FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.8:"
>     inherit kernel
>     require recipes-kernel/linux/linux-yocto.inc
>     COMPATIBLE_MACHINE_beaglebone = "(beaglebone)"
>     SRC_URI += " file://mine.patch \
>                   file://config-addons.cfg \
>                   "
>
> My config-addons.cfg:
>
>     CONFIG_WATCHDOG_NOWAYOUT=y
>     CONFIG_NTFS_FS=y
>     CONFIG_NTFS_RW=y
>
> After a cleansstate the build got stucked on do_patch task.
> Here is the content of log.do_patch:
>
>     DEBUG: Executing shell function do_patch
>     WARNING: no meta data branch found ...
>     Switched to branch 'linux-3.8.y'

I fell behind today .. i had 2300 unread email to start this morning :)
Is there a way that I can get a copy of your recipes and layers ? If
I can do a build myself, I can easily debug and fix this .. otherwise, we'll
go back and forth many times debugging.

Cheers,

Bruce

>
>
> Running with bitbake -v I got the following:
>
>     ...
>     + configme --reconfig --output
>     <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.13-r23a/linux-beaglebone-standard-build
>     standard beaglebone
>     [INFO] Configuring target/machine combo: "standard/beaglebone"
>
>     [INFO] Configuring target/machine combo: "standard/beaglebone"
>     [INFO] collecting configs in ./meta/meta-series
>
>     [INFO] collecting configs in ./meta/meta-series
>     cat: meta/cfg/standard/beaglebone/config_frag.txt: No such file or
>     directory
>
>     cat: meta/cfg/standard/beaglebone/config_frag.txt: No such file or
>     directory
>     cat: meta/cfg/standard/beaglebone/config_frag.txt: No such file or
>     directory
>
>     cat: meta/cfg/standard/beaglebone/config_frag.txt: No such file or
>     directory
>     mv: target `3.8.13' is not a directory
>
>     mv: target `3.8.13' is not a directory
>     creation of pre-processed config data failed
>     config of "standard/beaglebone" failed
>
>     creation of pre-processed config data failed
>     config of "standard/beaglebone" failed
>     ERROR: Function failed: do_kernel_configme (see
>     <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.13-r23a/temp/log.do_kernel_configme15450.
>     for further information)
>     ERROR: Task 7
>     (<...>/setup-scripts/sources/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb
>     <http://linux-mainline_3.8.bb>, do_kernel_configme) failed with exit
>     code '1'
>
>
>
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/



From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <diego.sueiro@gmail.com>
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com
	[209.85.223.172])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 0B944E016DD
	for <yocto@yoctoproject.org>; Fri, 18 Oct 2013 02:17:59 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id tp5so6213218ieb.17
	for <yocto@yoctoproject.org>; Fri, 18 Oct 2013 02:17:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=5N6D6eBXofOu5ZNviW6Xg6vq+KIbMbAzRHbeuJCdUkk=;
	b=HN+ttOI3JWHCY0Qv/vos4UpvkNg7TJlZYUThCJPTXOf/xW/j8KRbxZA2ATRKnNiJOC
	cwuFrCNxyfJfOZ6AjurvGdB5UNkcBoiEEEiDBmRH24E0eBf6CUOgkAFs8rfRk+8Hfb88
	CGdp6QkUmCcRpTOfCu5v13B2I17JiBJJDXoAKQpZv6qFSqXleppsSbS8uOiscXUiUVG4
	7AZH6qcUdy4vme7Y0DIDBHbjN1x4XF1SD/Py7xxvI4N80c8NFD0nDMvQX3//at1L1PKM
	ccwDzXt+DaD8+lygXmfz9ropSI7nWxG+SatYTGyYIJr+gghIseU252G/1V9TzTVzePA5
	eGAw==
X-Received: by 10.43.178.135 with SMTP id ow7mr1063571icc.43.1382087878882;
	Fri, 18 Oct 2013 02:17:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.26.233 with HTTP; Fri, 18 Oct 2013 02:17:38 -0700 (PDT)
In-Reply-To: <5260BDA6.4020807@windriver.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
From: Diego Sueiro <diego.sueiro@gmail.com>
Date: Fri, 18 Oct 2013 06:17:38 -0300
Message-ID: <CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Rudolf Streif <rstreif@linuxfoundation.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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Oct 2013 09:18:03 -0000
Content-Type: multipart/alternative; boundary=001a11c30bec11c07804e900697c

--001a11c30bec11c07804e900697c
Content-Type: text/plain; charset=ISO-8859-1

2013/10/18 Bruce Ashfield <bruce.ashfield@windriver.com>

> I fell behind today .. i had 2300 unread email to start this morning :)
> Is there a way that I can get a copy of your recipes and layers ? If
> I can do a build myself, I can easily debug and fix this .. otherwise,
> we'll
> go back and forth many times debugging.
>
> Cheers,
>
> Bruce
>

I'm using the environment provided by Angstrom from it's github setup
scripts.
If you want to exactly reproduce it you need to:

git clone https://github.com/Angstrom-distribution/setup-scripts.git
cd setup-scripts
git checkout angstrom-v2013.06-yocto1.4
MACHINE=beaglebone ./oebb.sh config beaglebone

Here is the setup and files for meta-mine:

bblayers.conf:

BBLAYERS = \"

...
${TOPDIR}/sources/meta-mine \
"

meta-mine/conf/layer.conf:

# We have a conf and classes directory, append to BBPATH
BBPATH .= ":${LAYERDIR}"
# We have a recipes directory, add to BBFILES
BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
BBFILE_COLLECTIONS += "mine-layer"
BBFILE_PATTERN_mine-layer := "^${LAYERDIR}/"
BBFILE_PRIORITY_mine-layer = "10"
LAYERDEPENDS_mine-layer = "angstrom-layer"

meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:

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 "

meta-mine/recipes-kernel/linux/linux-mainline-3.8/config-addons.cfg:

CONFIG_WATCHDOG_NOWAYOUT=y
CONFIG_NTFS_FS=y
CONFIG_NTFS_RW=y



But I think that instead of using the whole Angstrom you can just use poky
and meta-beagleboard/common-bsp on dylan branch.


Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/

--001a11c30bec11c07804e900697c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
2013/10/18 Bruce Ashfield <span dir=3D"ltr">&lt;<a href=3D"mailto:bruce.ash=
field@windriver.com" target=3D"_blank">bruce.ashfield@windriver.com</a>&gt;=
</span><br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div id=3D":10a" style=3D"overflow:hidden">I fell behind t=
oday .. i had 2300 unread email to start this morning :)<br>


Is there a way that I can get a copy of your recipes and layers ? If<br>
I can do a build myself, I can easily debug and fix this .. otherwise, we&#=
39;ll<br>
go back and forth many times debugging.<br>
<br>
Cheers,<br>
<br>
Bruce</div></blockquote></div><br>I&#39;m using the environment provided by=
 Angstrom from it&#39;s github setup scripts.</div><div class=3D"gmail_extr=
a">If you want to exactly reproduce it you need to:</div><div class=3D"gmai=
l_extra">

<blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><div =
class=3D"gmail_extra" style><div class=3D"gmail_extra">git clone <a href=3D=
"https://github.com/Angstrom-distribution/setup-scripts.git">https://github=
.com/Angstrom-distribution/setup-scripts.git</a></div>

<div class=3D"gmail_extra">cd setup-scripts</div><div class=3D"gmail_extra"=
>git checkout angstrom-v2013.06-yocto1.4</div><div class=3D"gmail_extra">MA=
CHINE=3Dbeaglebone ./oebb.sh config beaglebone</div><div><br></div></div></=
blockquote>

Here is the setup and files for meta-mine:</div><div class=3D"gmail_extra" =
style><br></div>bblayers.conf:<br><blockquote style=3D"margin:0px 0px 0px 4=
0px;border:none;padding:0px"><div class=3D"gmail_extra" style>BBLAYERS =3D =
\&quot;<br>

</div></blockquote><blockquote style=3D"margin:0px 0px 0px 40px;border:none=
;padding:0px"><div class=3D"gmail_extra"><blockquote style=3D"margin:0px 0p=
x 0px 40px;border:none;padding:0px"><div class=3D"gmail_extra" style>...</d=
iv>
<div class=3D"gmail_extra" style>
${TOPDIR}/sources/meta-mine \<br></div><div class=3D"gmail_extra" style>&qu=
ot;</div></blockquote></div></blockquote><div class=3D"gmail_extra">meta-mi=
ne/conf/layer.conf:</div><div class=3D"gmail_extra"><blockquote style=3D"ma=
rgin:0px 0px 0px 40px;border:none;padding:0px">

<div class=3D"gmail_extra" style><div class=3D"gmail_extra"># We have a con=
f and classes directory, append to BBPATH</div><div class=3D"gmail_extra">B=
BPATH .=3D &quot;:${LAYERDIR}&quot;</div><div class=3D"gmail_extra"># We ha=
ve a recipes directory, add to BBFILES<br>

</div><div class=3D"gmail_extra">BBFILES +=3D &quot;${LAYERDIR}/recipes*/*/=
*.bb ${LAYERDIR}/recipes*/*/*.bbappend&quot;</div><div class=3D"gmail_extra=
">BBFILE_COLLECTIONS +=3D &quot;mine-layer&quot;<br></div><div class=3D"gma=
il_extra">

BBFILE_PATTERN_mine-layer :=3D &quot;^${LAYERDIR}/&quot;</div><div class=3D=
"gmail_extra">BBFILE_PRIORITY_mine-layer =3D &quot;10&quot;</div><div class=
=3D"gmail_extra">LAYERDEPENDS_mine-layer =3D &quot;angstrom-layer&quot;<br>=
</div>

<div><br></div></div></blockquote>meta-mine/recipes-kernel/linux/linux-main=
line_3.8.bbappend:</div><div class=3D"gmail_extra"><blockquote style=3D"mar=
gin:0px 0px 0px 40px;border:none;padding:0px"><div class=3D"gmail_extra" st=
yle>

<div class=3D"gmail_extra">FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/${=
PN}-3.8:&quot;</div><div class=3D"gmail_extra"><div class=3D"gmail_extra">i=
nherit kernel</div><div class=3D"gmail_extra">require recipes-kernel/linux/=
linux-yocto.inc</div>

<div class=3D"gmail_extra">COMPATIBLE_MACHINE_beaglebone =3D &quot;(beagleb=
one)&quot;<br></div></div><div class=3D"gmail_extra">SRC_URI +=3D &quot; fi=
le://config-addons.cfg=A0&quot;</div><div class=3D"gmail_extra"><br></div><=
/div></blockquote>

<div class=3D"gmail_extra">meta-mine/recipes-kernel/linux/linux-mainline-3.=
8/config-addons.cfg:<br></div></div><blockquote style=3D"margin:0px 0px 0px=
 40px;border:none;padding:0px"><div class=3D"gmail_extra"><div class=3D"gma=
il_extra" style>

<div class=3D"gmail_extra">CONFIG_WATCHDOG_NOWAYOUT=3Dy</div><div class=3D"=
gmail_extra">CONFIG_NTFS_FS=3Dy</div><div class=3D"gmail_extra">CONFIG_NTFS=
_RW=3Dy</div></div></div></blockquote><div class=3D"gmail_extra"><div class=
=3D"gmail_extra">

<br></div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra" s=
tyle>But I think that instead of using the whole Angstrom you can just use =
poky and meta-beagleboard/common-bsp on dylan branch.</div><div class=3D"gm=
ail_extra">

<br></div><br clear=3D"all"><div><div dir=3D"ltr"><div>Regards,</div><div><=
br></div>--<br>*dS<br>Diego Sueiro<br><br>/*long live rock &#39;n roll*/<br=
></div></div>
</div></div>

--001a11c30bec11c07804e900697c--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Bruce.Ashfield@windriver.com>
Received: from mail.windriver.com (mail.windriver.com [147.11.1.11])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id D0C43E0169A
	for <yocto@yoctoproject.org>; Fri, 18 Oct 2013 13:17:31 -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 r9IKHRKG009747
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
	Fri, 18 Oct 2013 13:17:27 -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;
	Fri, 18 Oct 2013 13:17:26 -0700
Message-ID: <5261974C.7010202@windriver.com>
Date: Fri, 18 Oct 2013 16:17:16 -0400
From: Bruce Ashfield <bruce.ashfield@windriver.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Diego Sueiro <diego.sueiro@gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
In-Reply-To: <CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Rudolf Streif <rstreif@linuxfoundation.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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Oct 2013 20:17:32 -0000
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

On 13-10-18 05:17 AM, Diego Sueiro wrote:
>
> 2013/10/18 Bruce Ashfield <bruce.ashfield@windriver.com
> <mailto:bruce.ashfield@windriver.com>>
>
>     I fell behind today .. i had 2300 unread email to start this morning :)
>     Is there a way that I can get a copy of your recipes and layers ? If
>     I can do a build myself, I can easily debug and fix this ..
>     otherwise, we'll
>     go back and forth many times debugging.
>
>     Cheers,
>
>     Bruce
>
>
> I'm using the environment provided by Angstrom from it's github setup
> scripts.
> If you want to exactly reproduce it you need to:
>
>     git clone https://github.com/Angstrom-distribution/setup-scripts.git
>     cd setup-scripts
>     git checkout angstrom-v2013.06-yocto1.4
>     MACHINE=beaglebone ./oebb.sh config beaglebone
>
> Here is the setup and files for meta-mine:
>
> bblayers.conf:
>
>     BBLAYERS = \"
>
>         ...
>         ${TOPDIR}/sources/meta-mine \
>         "
>
> meta-mine/conf/layer.conf:
>
>     # We have a conf and classes directory, append to BBPATH
>     BBPATH .= ":${LAYERDIR}"
>     # We have a recipes directory, add to BBFILES
>     BBFILES += "${LAYERDIR}/recipes*/*/*.bb
>     ${LAYERDIR}/recipes*/*/*.bbappend"
>     BBFILE_COLLECTIONS += "mine-layer"
>     BBFILE_PATTERN_mine-layer := "^${LAYERDIR}/"
>     BBFILE_PRIORITY_mine-layer = "10"
>     LAYERDEPENDS_mine-layer = "angstrom-layer"
>
> meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
>
>     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 "
>
> meta-mine/recipes-kernel/linux/linux-mainline-3.8/config-addons.cfg:
>
>     CONFIG_WATCHDOG_NOWAYOUT=y
>     CONFIG_NTFS_FS=y
>     CONFIG_NTFS_RW=y
>
>
>
> But I think that instead of using the whole Angstrom you can just use
> poky and meta-beagleboard/common-bsp on dylan branch.

Great. I'll launch some test builds and see what breaks (or works) :)

Bruce

>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/



From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mikelewis@alphalem.com>
Received: from oproxy7-pub.mail.unifiedlayer.com
	(oproxy7-pub.mail.unifiedlayer.com [67.222.55.9])
	by yocto-www.yoctoproject.org (Postfix) with SMTP id AD865E0173E
	for <yocto@yoctoproject.org>; Tue, 22 Oct 2013 09:23:03 -0700 (PDT)
Received: (qmail 26598 invoked by uid 0); 22 Oct 2013 16:23:02 -0000
Received: from unknown (HELO box891.bluehost.com) (69.195.124.91)
	by oproxy7.mail.unifiedlayer.com with SMTP; 22 Oct 2013 16:23:02 -0000
Received: from [24.130.51.221] (port=50591 helo=[10.0.0.10])
	by box891.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256)
	(Exim 4.80) (envelope-from <mikelewis@alphalem.com>)
	id 1VYejV-0006vn-V0; Tue, 22 Oct 2013 10:23:02 -0600
Message-ID: <5266A665.8030303@alphalem.com>
Date: Tue, 22 Oct 2013 09:23:01 -0700
From: Mike Lewis <mikelewis@alphalem.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/20130827 Icedove/17.0.8
MIME-Version: 1.0
To: bruce.ashfield@windriver.com
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com>
In-Reply-To: <5261974C.7010202@windriver.com>
X-Identified-User: {2749:box891.bluehost.com:alphalem:alphalem.com}
	{sentby:smtp auth 24.130.51.221 authed with
	mikelewis+alphalem.com}
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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Oct 2013 16:23:03 -0000
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Bruce,

I'm trying to accomplish the nearly the same thing (i.e. adding config 
fragment) and I'm having the same issue at the do_patch step. Were you 
able to reproduce this on your end?

Thanks,
Mike

On 10/18/2013 01:17 PM, Bruce Ashfield wrote:
> On 13-10-18 05:17 AM, Diego Sueiro wrote:
>>
>> 2013/10/18 Bruce Ashfield <bruce.ashfield@windriver.com
>> <mailto:bruce.ashfield@windriver.com>>
>>
>>     I fell behind today .. i had 2300 unread email to start this 
>> morning :)
>>     Is there a way that I can get a copy of your recipes and layers ? If
>>     I can do a build myself, I can easily debug and fix this ..
>>     otherwise, we'll
>>     go back and forth many times debugging.
>>
>>     Cheers,
>>
>>     Bruce
>>
>>
>> I'm using the environment provided by Angstrom from it's github setup
>> scripts.
>> If you want to exactly reproduce it you need to:
>>
>>     git clone https://github.com/Angstrom-distribution/setup-scripts.git
>>     cd setup-scripts
>>     git checkout angstrom-v2013.06-yocto1.4
>>     MACHINE=beaglebone ./oebb.sh config beaglebone
>>
>> Here is the setup and files for meta-mine:
>>
>> bblayers.conf:
>>
>>     BBLAYERS = \"
>>
>>         ...
>>         ${TOPDIR}/sources/meta-mine \
>>         "
>>
>> meta-mine/conf/layer.conf:
>>
>>     # We have a conf and classes directory, append to BBPATH
>>     BBPATH .= ":${LAYERDIR}"
>>     # We have a recipes directory, add to BBFILES
>>     BBFILES += "${LAYERDIR}/recipes*/*/*.bb
>>     ${LAYERDIR}/recipes*/*/*.bbappend"
>>     BBFILE_COLLECTIONS += "mine-layer"
>>     BBFILE_PATTERN_mine-layer := "^${LAYERDIR}/"
>>     BBFILE_PRIORITY_mine-layer = "10"
>>     LAYERDEPENDS_mine-layer = "angstrom-layer"
>>
>> meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
>>
>>     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 "
>>
>> meta-mine/recipes-kernel/linux/linux-mainline-3.8/config-addons.cfg:
>>
>>     CONFIG_WATCHDOG_NOWAYOUT=y
>>     CONFIG_NTFS_FS=y
>>     CONFIG_NTFS_RW=y
>>
>>
>>
>> But I think that instead of using the whole Angstrom you can just use
>> poky and meta-beagleboard/common-bsp on dylan branch.
>
> Great. I'll launch some test builds and see what breaks (or works) :)
>
> Bruce
>
>>
>>
>> Regards,
>>
>> -- 
>> *dS
>> Diego Sueiro
>>
>> /*long live rock 'n roll*/
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Bruce.Ashfield@windriver.com>
Received: from mail.windriver.com (mail.windriver.com [147.11.1.11])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 2CF17E01742
	for <yocto@yoctoproject.org>; Tue, 22 Oct 2013 15:10:09 -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 r9MMA6HQ012636
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
	Tue, 22 Oct 2013 15:10:06 -0700 (PDT)
Received: from [128.224.20.172] (128.224.20.172) by ALA-HCA.corp.ad.wrs.com
	(147.11.189.50) with Microsoft SMTP Server id 14.2.347.0;
	Tue, 22 Oct 2013 15:10:05 -0700
Message-ID: <5266F7BB.3070709@windriver.com>
Date: Tue, 22 Oct 2013 18:10:03 -0400
From: Bruce Ashfield <bruce.ashfield@windriver.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Mike Lewis <mikelewis@alphalem.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
In-Reply-To: <5266A665.8030303@alphalem.com>
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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Oct 2013 22:10:12 -0000
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

On 13-10-22 12:23 PM, Mike Lewis wrote:
> Hi Bruce,
>
> I'm trying to accomplish the nearly the same thing (i.e. adding config
> fragment) and I'm having the same issue at the do_patch step. Were you
> able to reproduce this on your end?

I'm still working on it. I'm enroute to ELC-e in Scotland, so I had to
cut my builds short and while in transit .. I haven't gotten back to it.

That being said, this is my #1 isssue at the moment, so I'll be back to
it shortly once I'm done getting screened by various security checkpoints :)

Bruce

>
> Thanks,
> Mike
>
> On 10/18/2013 01:17 PM, Bruce Ashfield wrote:
>> On 13-10-18 05:17 AM, Diego Sueiro wrote:
>>>
>>> 2013/10/18 Bruce Ashfield <bruce.ashfield@windriver.com
>>> <mailto:bruce.ashfield@windriver.com>>
>>>
>>>     I fell behind today .. i had 2300 unread email to start this
>>> morning :)
>>>     Is there a way that I can get a copy of your recipes and layers ? If
>>>     I can do a build myself, I can easily debug and fix this ..
>>>     otherwise, we'll
>>>     go back and forth many times debugging.
>>>
>>>     Cheers,
>>>
>>>     Bruce
>>>
>>>
>>> I'm using the environment provided by Angstrom from it's github setup
>>> scripts.
>>> If you want to exactly reproduce it you need to:
>>>
>>>     git clone https://github.com/Angstrom-distribution/setup-scripts.git
>>>     cd setup-scripts
>>>     git checkout angstrom-v2013.06-yocto1.4
>>>     MACHINE=beaglebone ./oebb.sh config beaglebone
>>>
>>> Here is the setup and files for meta-mine:
>>>
>>> bblayers.conf:
>>>
>>>     BBLAYERS = \"
>>>
>>>         ...
>>>         ${TOPDIR}/sources/meta-mine \
>>>         "
>>>
>>> meta-mine/conf/layer.conf:
>>>
>>>     # We have a conf and classes directory, append to BBPATH
>>>     BBPATH .= ":${LAYERDIR}"
>>>     # We have a recipes directory, add to BBFILES
>>>     BBFILES += "${LAYERDIR}/recipes*/*/*.bb
>>>     ${LAYERDIR}/recipes*/*/*.bbappend"
>>>     BBFILE_COLLECTIONS += "mine-layer"
>>>     BBFILE_PATTERN_mine-layer := "^${LAYERDIR}/"
>>>     BBFILE_PRIORITY_mine-layer = "10"
>>>     LAYERDEPENDS_mine-layer = "angstrom-layer"
>>>
>>> meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
>>>
>>>     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 "
>>>
>>> meta-mine/recipes-kernel/linux/linux-mainline-3.8/config-addons.cfg:
>>>
>>>     CONFIG_WATCHDOG_NOWAYOUT=y
>>>     CONFIG_NTFS_FS=y
>>>     CONFIG_NTFS_RW=y
>>>
>>>
>>>
>>> But I think that instead of using the whole Angstrom you can just use
>>> poky and meta-beagleboard/common-bsp on dylan branch.
>>
>> Great. I'll launch some test builds and see what breaks (or works) :)
>>
>> Bruce
>>
>>>
>>>
>>> Regards,
>>>
>>> --
>>> *dS
>>> Diego Sueiro
>>>
>>> /*long live rock 'n roll*/
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>



From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Bruce.Ashfield@windriver.com>
Received: from mail.windriver.com (mail.windriver.com [147.11.1.11])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 91E87E01759
	for <yocto@yoctoproject.org>; Wed, 23 Oct 2013 17:17:45 -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 r9O0Hfsg013865
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
	Wed, 23 Oct 2013 17:17:43 -0700 (PDT)
Received: from [128.224.20.199] (128.224.20.199) by ALA-HCA.corp.ad.wrs.com
	(147.11.189.50) with Microsoft SMTP Server id 14.2.347.0;
	Wed, 23 Oct 2013 17:17:40 -0700
Message-ID: <52686723.4080305@windriver.com>
Date: Wed, 23 Oct 2013 20:17:39 -0400
From: Bruce Ashfield <bruce.ashfield@windriver.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Mike Lewis <mikelewis@alphalem.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
In-Reply-To: <5266A665.8030303@alphalem.com>
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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Oct 2013 00:17:46 -0000
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

On 13-10-22 12:23 PM, Mike Lewis wrote:
> Hi Bruce,
>
> I'm trying to accomplish the nearly the same thing (i.e. adding config
> fragment) and I'm having the same issue at the do_patch step. Were you
> able to reproduce this on your end?

Mike,

Is you config/layer somewhere than I can have a look at it ? I was trying
some builds here, and my tests are working. But I'd like to try it
with your config as well.

Bruce

>
> Thanks,
> Mike
>
> On 10/18/2013 01:17 PM, Bruce Ashfield wrote:
>> On 13-10-18 05:17 AM, Diego Sueiro wrote:
>>>
>>> 2013/10/18 Bruce Ashfield <bruce.ashfield@windriver.com
>>> <mailto:bruce.ashfield@windriver.com>>
>>>
>>>     I fell behind today .. i had 2300 unread email to start this
>>> morning :)
>>>     Is there a way that I can get a copy of your recipes and layers ? If
>>>     I can do a build myself, I can easily debug and fix this ..
>>>     otherwise, we'll
>>>     go back and forth many times debugging.
>>>
>>>     Cheers,
>>>
>>>     Bruce
>>>
>>>
>>> I'm using the environment provided by Angstrom from it's github setup
>>> scripts.
>>> If you want to exactly reproduce it you need to:
>>>
>>>     git clone https://github.com/Angstrom-distribution/setup-scripts.git
>>>     cd setup-scripts
>>>     git checkout angstrom-v2013.06-yocto1.4
>>>     MACHINE=beaglebone ./oebb.sh config beaglebone
>>>
>>> Here is the setup and files for meta-mine:
>>>
>>> bblayers.conf:
>>>
>>>     BBLAYERS = \"
>>>
>>>         ...
>>>         ${TOPDIR}/sources/meta-mine \
>>>         "
>>>
>>> meta-mine/conf/layer.conf:
>>>
>>>     # We have a conf and classes directory, append to BBPATH
>>>     BBPATH .= ":${LAYERDIR}"
>>>     # We have a recipes directory, add to BBFILES
>>>     BBFILES += "${LAYERDIR}/recipes*/*/*.bb
>>>     ${LAYERDIR}/recipes*/*/*.bbappend"
>>>     BBFILE_COLLECTIONS += "mine-layer"
>>>     BBFILE_PATTERN_mine-layer := "^${LAYERDIR}/"
>>>     BBFILE_PRIORITY_mine-layer = "10"
>>>     LAYERDEPENDS_mine-layer = "angstrom-layer"
>>>
>>> meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
>>>
>>>     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 "
>>>
>>> meta-mine/recipes-kernel/linux/linux-mainline-3.8/config-addons.cfg:
>>>
>>>     CONFIG_WATCHDOG_NOWAYOUT=y
>>>     CONFIG_NTFS_FS=y
>>>     CONFIG_NTFS_RW=y
>>>
>>>
>>>
>>> But I think that instead of using the whole Angstrom you can just use
>>> poky and meta-beagleboard/common-bsp on dylan branch.
>>
>> Great. I'll launch some test builds and see what breaks (or works) :)
>>
>> Bruce
>>
>>>
>>>
>>> Regards,
>>>
>>> --
>>> *dS
>>> Diego Sueiro
>>>
>>> /*long live rock 'n roll*/
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>



From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <diego.sueiro@gmail.com>
Received: from mail-ie0-f173.google.com (mail-ie0-f173.google.com
	[209.85.223.173])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id CD99FE0176E
	for <yocto@yoctoproject.org>; Fri, 25 Oct 2013 04:44:01 -0700 (PDT)
Received: by mail-ie0-f173.google.com with SMTP id u16so6013623iet.4
	for <yocto@yoctoproject.org>; Fri, 25 Oct 2013 04:44:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=+Dhqn2RAlG48pBmB+hs4TgDZHz+FrN4l4R0nFKhWHao=;
	b=PB3U1B4kx1Gp5X4+ue+myfqUg6L9a6rY/0CYeR0BiGIjBIN6YOGSmxqqRPjRL0MiQn
	G7voSap9iyoPD2KhRRPJibK81T8ybkmmrAMb4Ptyzwxy27nUW7+KB6gFoD9hLaSJbJXc
	Dkug9mwJcuJg8/1A8+6kSJq9Uh1b4kU2C6v1w2hB3jv2SwxLGac/FUt1QkoOW//mO2t8
	w1WrXSfK1jcKWDriReMz2fAPd/VntQIgFmr/wrYg7XIEBB+Duta3fD0R88XnS4RpF5Sm
	0luk4umglgtwGQ+7AgxS5f8xi+tlLk2mhgRIMP/RyhmzWfof9KlxpKPtlE4Ge/moEQ/T
	ZXLw==
X-Received: by 10.42.149.130 with SMTP id w2mr560014icv.64.1382701440708; Fri,
	25 Oct 2013 04:44:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.26.233 with HTTP; Fri, 25 Oct 2013 04:43:40 -0700 (PDT)
In-Reply-To: <52686723.4080305@windriver.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
	<52686723.4080305@windriver.com>
From: Diego Sueiro <diego.sueiro@gmail.com>
Date: Fri, 25 Oct 2013 09:43:40 -0200
Message-ID: <CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Oct 2013 11:44:02 -0000
Content-Type: multipart/alternative; boundary=90e6ba1efbf034523104e98f445c

--90e6ba1efbf034523104e98f445c
Content-Type: text/plain; charset=ISO-8859-1

Bruce,

Regarding the defconfig not used, I've found this thread on Angstrom devel
ML:
http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg06721.html

I've replaced "FILESEXTRAPATHS_prepend" with "FILESPATH_prepend" and
removed the custom "do_configure_prepend" function and bitbake is now using
my defconfig.
So, it seems that there is an issue with FILESEXTRAPATHS variable.

Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/


2013/10/23 Bruce Ashfield <bruce.ashfield@windriver.com>

> On 13-10-22 12:23 PM, Mike Lewis wrote:
>
>> Hi Bruce,
>>
>> I'm trying to accomplish the nearly the same thing (i.e. adding config
>> fragment) and I'm having the same issue at the do_patch step. Were you
>> able to reproduce this on your end?
>>
>
> Mike,
>
> Is you config/layer somewhere than I can have a look at it ? I was trying
> some builds here, and my tests are working. But I'd like to try it
> with your config as well.
>
> Bruce
>
>
>
>> Thanks,
>> Mike
>>
>> On 10/18/2013 01:17 PM, Bruce Ashfield wrote:
>>
>>> On 13-10-18 05:17 AM, Diego Sueiro wrote:
>>>
>>>>
>>>> 2013/10/18 Bruce Ashfield <bruce.ashfield@windriver.com
>>>> <mailto:bruce.ashfield@**windriver.com <bruce.ashfield@windriver.com>>>
>>>>
>>>>     I fell behind today .. i had 2300 unread email to start this
>>>> morning :)
>>>>     Is there a way that I can get a copy of your recipes and layers ? If
>>>>     I can do a build myself, I can easily debug and fix this ..
>>>>     otherwise, we'll
>>>>     go back and forth many times debugging.
>>>>
>>>>     Cheers,
>>>>
>>>>     Bruce
>>>>
>>>>
>>>> I'm using the environment provided by Angstrom from it's github setup
>>>> scripts.
>>>> If you want to exactly reproduce it you need to:
>>>>
>>>>     git clone https://github.com/Angstrom-**
>>>> distribution/setup-scripts.git<https://github.com/Angstrom-distribution/setup-scripts.git>
>>>>     cd setup-scripts
>>>>     git checkout angstrom-v2013.06-yocto1.4
>>>>     MACHINE=beaglebone ./oebb.sh config beaglebone
>>>>
>>>> Here is the setup and files for meta-mine:
>>>>
>>>> bblayers.conf:
>>>>
>>>>     BBLAYERS = \"
>>>>
>>>>         ...
>>>>         ${TOPDIR}/sources/meta-mine \
>>>>         "
>>>>
>>>> meta-mine/conf/layer.conf:
>>>>
>>>>     # We have a conf and classes directory, append to BBPATH
>>>>     BBPATH .= ":${LAYERDIR}"
>>>>     # We have a recipes directory, add to BBFILES
>>>>     BBFILES += "${LAYERDIR}/recipes*/*/*.bb
>>>>     ${LAYERDIR}/recipes*/*/*.**bbappend"
>>>>     BBFILE_COLLECTIONS += "mine-layer"
>>>>     BBFILE_PATTERN_mine-layer := "^${LAYERDIR}/"
>>>>     BBFILE_PRIORITY_mine-layer = "10"
>>>>     LAYERDEPENDS_mine-layer = "angstrom-layer"
>>>>
>>>> meta-mine/recipes-kernel/**linux/linux-mainline_3.8.**bbappend:
>>>>
>>>>     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 "
>>>>
>>>> meta-mine/recipes-kernel/**linux/linux-mainline-3.8/**
>>>> config-addons.cfg:
>>>>
>>>>     CONFIG_WATCHDOG_NOWAYOUT=y
>>>>     CONFIG_NTFS_FS=y
>>>>     CONFIG_NTFS_RW=y
>>>>
>>>>
>>>>
>>>> But I think that instead of using the whole Angstrom you can just use
>>>> poky and meta-beagleboard/common-bsp on dylan branch.
>>>>
>>>
>>> Great. I'll launch some test builds and see what breaks (or works) :)
>>>
>>> Bruce
>>>
>>>
>>>>
>>>> Regards,
>>>>
>>>> --
>>>> *dS
>>>> Diego Sueiro
>>>>
>>>> /*long live rock 'n roll*/
>>>>
>>>
>>> ______________________________**_________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.**org/listinfo/yocto<https://lists.yoctoproject.org/listinfo/yocto>
>>>
>>
>>
> ______________________________**_________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.**org/listinfo/yocto<https://lists.yoctoproject.org/listinfo/yocto>
>

--90e6ba1efbf034523104e98f445c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Bruce,<div><br></div><div style>Regarding the defconfig no=
t used, I&#39;ve found this thread on Angstrom devel ML:</div><div style><a=
 href=3D"http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/ms=
g06721.html">http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.or=
g/msg06721.html</a><br>

</div><div style><br></div><div style>I&#39;ve replaced &quot;FILESEXTRAPAT=
HS_prepend&quot; with &quot;FILESPATH_prepend&quot; and removed the custom =
&quot;do_configure_prepend&quot; function and bitbake is now using my defco=
nfig.</div>

<div style>So, it seems that there is an issue with FILESEXTRAPATHS variabl=
e.</div><div class=3D"gmail_extra"><br clear=3D"all"><div><div dir=3D"ltr">=
<div>Regards,</div><div><br></div>--<br>*dS<br>Diego Sueiro<br><br>/*long l=
ive rock &#39;n roll*/</div>

</div>
<br><br><div class=3D"gmail_quote">2013/10/23 Bruce Ashfield <span dir=3D"l=
tr">&lt;<a href=3D"mailto:bruce.ashfield@windriver.com" target=3D"_blank">b=
ruce.ashfield@windriver.com</a>&gt;</span><br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-co=
lor:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

<div class=3D"im">On <a href=3D"tel:13-10-22%2012" value=3D"+13102212" targ=
et=3D"_blank">13-10-22 12</a>:23 PM, Mike Lewis wrote:<br>
</div><div class=3D"im"><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);b=
order-left-style:solid;padding-left:1ex">
Hi Bruce,<br>
<br>
I&#39;m trying to accomplish the nearly the same thing (i.e. adding config<=
br>
fragment) and I&#39;m having the same issue at the do_patch step. Were you<=
br>
able to reproduce this on your end?<br>
</blockquote>
<br></div>
Mike,<br>
<br>
Is you config/layer somewhere than I can have a look at it ? I was trying<b=
r>
some builds here, and my tests are working. But I&#39;d like to try it<br>
with your config as well.<span class=3D""><font color=3D"#888888"><br>
<br>
Bruce</font></span><div class=3D""><div class=3D"h5"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
<br>
Thanks,<br>
Mike<br>
<br>
On 10/18/2013 01:17 PM, Bruce Ashfield wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
On <a href=3D"tel:13-10-18%2005" value=3D"+13101805" target=3D"_blank">13-1=
0-18 05</a>:17 AM, Diego Sueiro wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
<br>
2013/10/18 Bruce Ashfield &lt;<a href=3D"mailto:bruce.ashfield@windriver.co=
m" target=3D"_blank">bruce.ashfield@windriver.com</a><br>
&lt;mailto:<a href=3D"mailto:bruce.ashfield@windriver.com" target=3D"_blank=
">bruce.ashfield@<u></u>windriver.com</a>&gt;&gt;<br>
<br>
=A0 =A0 I fell behind today .. i had 2300 unread email to start this<br>
morning :)<br>
=A0 =A0 Is there a way that I can get a copy of your recipes and layers ? I=
f<br>
=A0 =A0 I can do a build myself, I can easily debug and fix this ..<br>
=A0 =A0 otherwise, we&#39;ll<br>
=A0 =A0 go back and forth many times debugging.<br>
<br>
=A0 =A0 Cheers,<br>
<br>
=A0 =A0 Bruce<br>
<br>
<br>
I&#39;m using the environment provided by Angstrom from it&#39;s github set=
up<br>
scripts.<br>
If you want to exactly reproduce it you need to:<br>
<br>
=A0 =A0 git clone <a href=3D"https://github.com/Angstrom-distribution/setup=
-scripts.git" target=3D"_blank">https://github.com/Angstrom-<u></u>distribu=
tion/setup-scripts.git</a><br>
=A0 =A0 cd setup-scripts<br>
=A0 =A0 git checkout angstrom-v2013.06-yocto1.4<br>
=A0 =A0 MACHINE=3Dbeaglebone ./oebb.sh config beaglebone<br>
<br>
Here is the setup and files for meta-mine:<br>
<br>
bblayers.conf:<br>
<br>
=A0 =A0 BBLAYERS =3D \&quot;<br>
<br>
=A0 =A0 =A0 =A0 ...<br>
=A0 =A0 =A0 =A0 ${TOPDIR}/sources/meta-mine \<br>
=A0 =A0 =A0 =A0 &quot;<br>
<br>
meta-mine/conf/layer.conf:<br>
<br>
=A0 =A0 # We have a conf and classes directory, append to BBPATH<br>
=A0 =A0 BBPATH .=3D &quot;:${LAYERDIR}&quot;<br>
=A0 =A0 # We have a recipes directory, add to BBFILES<br>
=A0 =A0 BBFILES +=3D &quot;${LAYERDIR}/recipes*/*/*.bb<br>
=A0 =A0 ${LAYERDIR}/recipes*/*/*.<u></u>bbappend&quot;<br>
=A0 =A0 BBFILE_COLLECTIONS +=3D &quot;mine-layer&quot;<br>
=A0 =A0 BBFILE_PATTERN_mine-layer :=3D &quot;^${LAYERDIR}/&quot;<br>
=A0 =A0 BBFILE_PRIORITY_mine-layer =3D &quot;10&quot;<br>
=A0 =A0 LAYERDEPENDS_mine-layer =3D &quot;angstrom-layer&quot;<br>
<br>
meta-mine/recipes-kernel/<u></u>linux/linux-mainline_3.8.<u></u>bbappend:<b=
r>
<br>
=A0 =A0 FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/${PN}-3.8:&quot;<br>
=A0 =A0 inherit kernel<br>
=A0 =A0 require recipes-kernel/linux/linux-<u></u>yocto.inc<br>
=A0 =A0 COMPATIBLE_MACHINE_beaglebone =3D &quot;(beaglebone)&quot;<br>
=A0 =A0 SRC_URI +=3D &quot; file://config-addons.cfg &quot;<br>
<br>
meta-mine/recipes-kernel/<u></u>linux/linux-mainline-3.8/<u></u>config-addo=
ns.cfg:<br>
<br>
=A0 =A0 CONFIG_WATCHDOG_NOWAYOUT=3Dy<br>
=A0 =A0 CONFIG_NTFS_FS=3Dy<br>
=A0 =A0 CONFIG_NTFS_RW=3Dy<br>
<br>
<br>
<br>
But I think that instead of using the whole Angstrom you can just use<br>
poky and meta-beagleboard/common-bsp on dylan branch.<br>
</blockquote>
<br>
Great. I&#39;ll launch some test builds and see what breaks (or works) :)<b=
r>
<br>
Bruce<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
<br>
<br>
Regards,<br>
<br>
--<br>
*dS<br>
Diego Sueiro<br>
<br>
/*long live rock &#39;n roll*/<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
yocto mailing list<br>
<a href=3D"mailto:yocto@yoctoproject.org" target=3D"_blank">yocto@yoctoproj=
ect.org</a><br>
<a href=3D"https://lists.yoctoproject.org/listinfo/yocto" target=3D"_blank"=
>https://lists.yoctoproject.<u></u>org/listinfo/yocto</a><br>
</blockquote>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
yocto mailing list<br>
<a href=3D"mailto:yocto@yoctoproject.org" target=3D"_blank">yocto@yoctoproj=
ect.org</a><br>
<a href=3D"https://lists.yoctoproject.org/listinfo/yocto" target=3D"_blank"=
>https://lists.yoctoproject.<u></u>org/listinfo/yocto</a><br>
</div></div></blockquote></div><br></div></div>

--90e6ba1efbf034523104e98f445c--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bruce.ashfield@gmail.com>
Received: from mail-la0-f48.google.com (mail-la0-f48.google.com
	[209.85.215.48])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id A966FE01773
	for <yocto@yoctoproject.org>; Fri, 25 Oct 2013 11:44:30 -0700 (PDT)
Received: by mail-la0-f48.google.com with SMTP id ev20so3342691lab.21
	for <yocto@yoctoproject.org>; Fri, 25 Oct 2013 11:44:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=7BMyYHoZHg3k+gnTQWK7NMF7mZd5sVbV5yCjxF7wz9E=;
	b=Eoz9346W45bc2mSxMjIrf3C3f6fGXXmjpi2tRTfQ6bDebO9g8HPO2OFec1EgmdFfft
	BHi465U/KrRBHukLB3trHYNOzX3w/W5dAvn3dhYjqu/M/cHIb5DKqZ1kDeV4/YFx+I9t
	OkS3YJAEaJYLhGpghr2ysgKeW9xCiZbQHdYzXxt6hpF5j6bveu16Vcda5wqwY97OoNNS
	zC3JxGKMY6lpJAGVAC17f7VCYlFutMwgUGaQvcZmzlH9lF2SRikRowVustqmfqSiA02X
	b+f1XEWPuBVdORR0+yXqnAxGZTm2oAwZqgrxvdZjD6G38bKGZ1D/lCbzYjqPJhxj6lxB
	7WuQ==
MIME-Version: 1.0
X-Received: by 10.152.23.5 with SMTP id i5mr5997020laf.8.1382726668086; Fri,
	25 Oct 2013 11:44:28 -0700 (PDT)
Received: by 10.112.14.200 with HTTP; Fri, 25 Oct 2013 11:44:28 -0700 (PDT)
In-Reply-To: <CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CA+gsK-o6n24Aqp2dtpOwnmrCBjWE=HDSJvfqyYy2pvJYrHqXmQ@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
	<52686723.4080305@windriver.com>
	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
Date: Fri, 25 Oct 2013 14:44:28 -0400
Message-ID: <CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Diego Sueiro <diego.sueiro@gmail.com>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Oct 2013 18:44:31 -0000
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Oct 25, 2013 at 7:43 AM, Diego Sueiro <diego.sueiro@gmail.com> wrote:
> Bruce,
>
> Regarding the defconfig not used, I've found this thread on Angstrom devel
> ML:
> http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg06721.html
>
> I've replaced "FILESEXTRAPATHS_prepend" with "FILESPATH_prepend" and removed
> the custom "do_configure_prepend" function and bitbake is now using my
> defconfig.
> So, it seems that there is an issue with FILESEXTRAPATHS variable.
>

Aha. That does make sense.

Mike: does that same change fix your issues ?

Bruce

> Regards,
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/
>
>
> 2013/10/23 Bruce Ashfield <bruce.ashfield@windriver.com>
>>
>> On 13-10-22 12:23 PM, Mike Lewis wrote:
>>>
>>> Hi Bruce,
>>>
>>> I'm trying to accomplish the nearly the same thing (i.e. adding config
>>> fragment) and I'm having the same issue at the do_patch step. Were you
>>> able to reproduce this on your end?
>>
>>
>> Mike,
>>
>> Is you config/layer somewhere than I can have a look at it ? I was trying
>> some builds here, and my tests are working. But I'd like to try it
>> with your config as well.
>>
>> Bruce
>>
>>
>>>
>>> Thanks,
>>> Mike
>>>
>>> On 10/18/2013 01:17 PM, Bruce Ashfield wrote:
>>>>
>>>> On 13-10-18 05:17 AM, Diego Sueiro wrote:
>>>>>
>>>>>
>>>>> 2013/10/18 Bruce Ashfield <bruce.ashfield@windriver.com
>>>>> <mailto:bruce.ashfield@windriver.com>>
>>>>>
>>>>>     I fell behind today .. i had 2300 unread email to start this
>>>>> morning :)
>>>>>     Is there a way that I can get a copy of your recipes and layers ?
>>>>> If
>>>>>     I can do a build myself, I can easily debug and fix this ..
>>>>>     otherwise, we'll
>>>>>     go back and forth many times debugging.
>>>>>
>>>>>     Cheers,
>>>>>
>>>>>     Bruce
>>>>>
>>>>>
>>>>> I'm using the environment provided by Angstrom from it's github setup
>>>>> scripts.
>>>>> If you want to exactly reproduce it you need to:
>>>>>
>>>>>     git clone
>>>>> https://github.com/Angstrom-distribution/setup-scripts.git
>>>>>     cd setup-scripts
>>>>>     git checkout angstrom-v2013.06-yocto1.4
>>>>>     MACHINE=beaglebone ./oebb.sh config beaglebone
>>>>>
>>>>> Here is the setup and files for meta-mine:
>>>>>
>>>>> bblayers.conf:
>>>>>
>>>>>     BBLAYERS = \"
>>>>>
>>>>>         ...
>>>>>         ${TOPDIR}/sources/meta-mine \
>>>>>         "
>>>>>
>>>>> meta-mine/conf/layer.conf:
>>>>>
>>>>>     # We have a conf and classes directory, append to BBPATH
>>>>>     BBPATH .= ":${LAYERDIR}"
>>>>>     # We have a recipes directory, add to BBFILES
>>>>>     BBFILES += "${LAYERDIR}/recipes*/*/*.bb
>>>>>     ${LAYERDIR}/recipes*/*/*.bbappend"
>>>>>     BBFILE_COLLECTIONS += "mine-layer"
>>>>>     BBFILE_PATTERN_mine-layer := "^${LAYERDIR}/"
>>>>>     BBFILE_PRIORITY_mine-layer = "10"
>>>>>     LAYERDEPENDS_mine-layer = "angstrom-layer"
>>>>>
>>>>> meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
>>>>>
>>>>>     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 "
>>>>>
>>>>> meta-mine/recipes-kernel/linux/linux-mainline-3.8/config-addons.cfg:
>>>>>
>>>>>     CONFIG_WATCHDOG_NOWAYOUT=y
>>>>>     CONFIG_NTFS_FS=y
>>>>>     CONFIG_NTFS_RW=y
>>>>>
>>>>>
>>>>>
>>>>> But I think that instead of using the whole Angstrom you can just use
>>>>> poky and meta-beagleboard/common-bsp on dylan branch.
>>>>
>>>>
>>>> Great. I'll launch some test builds and see what breaks (or works) :)
>>>>
>>>> Bruce
>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> --
>>>>> *dS
>>>>> Diego Sueiro
>>>>>
>>>>> /*long live rock 'n roll*/
>>>>
>>>>
>>>> _______________________________________________
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>>
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"


From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mikelewis@alphalem.com>
Received: from oproxy4-pub.mail.unifiedlayer.com
	(oproxy4-pub.mail.unifiedlayer.com [74.220.216.66])
	by yocto-www.yoctoproject.org (Postfix) with SMTP id 74450E01776
	for <yocto@yoctoproject.org>; Fri, 25 Oct 2013 18:19:57 -0700 (PDT)
Received: (qmail 32291 invoked by uid 0); 26 Oct 2013 01:19:56 -0000
Received: from unknown (HELO box891.bluehost.com) (69.195.124.91)
	by oproxy4.mail.unifiedlayer.com with SMTP; 26 Oct 2013 01:19:56 -0000
Received: from [24.130.51.221] (port=36830 helo=[10.0.0.10])
	by box891.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256)
	(Exim 4.80) (envelope-from <mikelewis@alphalem.com>)
	id 1VZsXk-0005qw-Pp; Fri, 25 Oct 2013 19:19:56 -0600
Message-ID: <526B18BC.5050302@alphalem.com>
Date: Fri, 25 Oct 2013 18:19:56 -0700
From: Mike Lewis <mikelewis@alphalem.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/20130827 Icedove/17.0.8
MIME-Version: 1.0
To: Bruce Ashfield <bruce.ashfield@gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
	<52686723.4080305@windriver.com>
	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>
In-Reply-To: <CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>
X-Identified-User: {2749:box891.bluehost.com:alphalem:alphalem.com}
	{sentby:smtp auth 24.130.51.221 authed with
	mikelewis+alphalem.com}
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Oct 2013 01:19:58 -0000
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Bruce: yep, fixed my issue. Sorry for the bother!

Diego: thanks for the solution!

- Mike

On 10/25/2013 11:44 AM, Bruce Ashfield wrote:
> On Fri, Oct 25, 2013 at 7:43 AM, Diego Sueiro <diego.sueiro@gmail.com> wrote:
>> Bruce,
>>
>> Regarding the defconfig not used, I've found this thread on Angstrom devel
>> ML:
>> http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg06721.html
>>
>> I've replaced "FILESEXTRAPATHS_prepend" with "FILESPATH_prepend" and removed
>> the custom "do_configure_prepend" function and bitbake is now using my
>> defconfig.
>> So, it seems that there is an issue with FILESEXTRAPATHS variable.
>>
> Aha. That does make sense.
>
> Mike: does that same change fix your issues ?
>
> Bruce
>
>> Regards,
>>
>> --
>> *dS
>> Diego Sueiro
>>
>> /*long live rock 'n roll*/
>>
>>
>> 2013/10/23 Bruce Ashfield <bruce.ashfield@windriver.com>
>>> On 13-10-22 12:23 PM, Mike Lewis wrote:
>>>> Hi Bruce,
>>>>
>>>> I'm trying to accomplish the nearly the same thing (i.e. adding config
>>>> fragment) and I'm having the same issue at the do_patch step. Were you
>>>> able to reproduce this on your end?
>>>
>>> Mike,
>>>
>>> Is you config/layer somewhere than I can have a look at it ? I was trying
>>> some builds here, and my tests are working. But I'd like to try it
>>> with your config as well.
>>>
>>> Bruce
>>>
>>>
>>>> Thanks,
>>>> Mike
>>>>
>>>> On 10/18/2013 01:17 PM, Bruce Ashfield wrote:
>>>>> On 13-10-18 05:17 AM, Diego Sueiro wrote:
>>>>>>
>>>>>> 2013/10/18 Bruce Ashfield <bruce.ashfield@windriver.com
>>>>>> <mailto:bruce.ashfield@windriver.com>>
>>>>>>
>>>>>>      I fell behind today .. i had 2300 unread email to start this
>>>>>> morning :)
>>>>>>      Is there a way that I can get a copy of your recipes and layers ?
>>>>>> If
>>>>>>      I can do a build myself, I can easily debug and fix this ..
>>>>>>      otherwise, we'll
>>>>>>      go back and forth many times debugging.
>>>>>>
>>>>>>      Cheers,
>>>>>>
>>>>>>      Bruce
>>>>>>
>>>>>>
>>>>>> I'm using the environment provided by Angstrom from it's github setup
>>>>>> scripts.
>>>>>> If you want to exactly reproduce it you need to:
>>>>>>
>>>>>>      git clone
>>>>>> https://github.com/Angstrom-distribution/setup-scripts.git
>>>>>>      cd setup-scripts
>>>>>>      git checkout angstrom-v2013.06-yocto1.4
>>>>>>      MACHINE=beaglebone ./oebb.sh config beaglebone
>>>>>>
>>>>>> Here is the setup and files for meta-mine:
>>>>>>
>>>>>> bblayers.conf:
>>>>>>
>>>>>>      BBLAYERS = \"
>>>>>>
>>>>>>          ...
>>>>>>          ${TOPDIR}/sources/meta-mine \
>>>>>>          "
>>>>>>
>>>>>> meta-mine/conf/layer.conf:
>>>>>>
>>>>>>      # We have a conf and classes directory, append to BBPATH
>>>>>>      BBPATH .= ":${LAYERDIR}"
>>>>>>      # We have a recipes directory, add to BBFILES
>>>>>>      BBFILES += "${LAYERDIR}/recipes*/*/*.bb
>>>>>>      ${LAYERDIR}/recipes*/*/*.bbappend"
>>>>>>      BBFILE_COLLECTIONS += "mine-layer"
>>>>>>      BBFILE_PATTERN_mine-layer := "^${LAYERDIR}/"
>>>>>>      BBFILE_PRIORITY_mine-layer = "10"
>>>>>>      LAYERDEPENDS_mine-layer = "angstrom-layer"
>>>>>>
>>>>>> meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
>>>>>>
>>>>>>      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 "
>>>>>>
>>>>>> meta-mine/recipes-kernel/linux/linux-mainline-3.8/config-addons.cfg:
>>>>>>
>>>>>>      CONFIG_WATCHDOG_NOWAYOUT=y
>>>>>>      CONFIG_NTFS_FS=y
>>>>>>      CONFIG_NTFS_RW=y
>>>>>>
>>>>>>
>>>>>>
>>>>>> But I think that instead of using the whole Angstrom you can just use
>>>>>> poky and meta-beagleboard/common-bsp on dylan branch.
>>>>>
>>>>> Great. I'll launch some test builds and see what breaks (or works) :)
>>>>>
>>>>> Bruce
>>>>>
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> --
>>>>>> *dS
>>>>>> Diego Sueiro
>>>>>>
>>>>>> /*long live rock 'n roll*/
>>>>>
>>>>> _______________________________________________
>>>>> yocto mailing list
>>>>> yocto@yoctoproject.org
>>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
>



From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <diego.sueiro@gmail.com>
Received: from mail-ie0-f175.google.com (mail-ie0-f175.google.com
	[209.85.223.175])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 4F265E01777
	for <yocto@yoctoproject.org>; Sat, 26 Oct 2013 03:57:52 -0700 (PDT)
Received: by mail-ie0-f175.google.com with SMTP id aq17so7938752iec.6
	for <yocto@yoctoproject.org>; Sat, 26 Oct 2013 03:57:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=EBiUWQr7YJaSD/kj88Ht38bqubDbJfh4+yNqBuZKJU4=;
	b=JDdfPsCJwedvzDvMZqA3uOeFYhyDtjAFoGf3Wses2JSBEjhaMzenMoMwRmZY7hozUl
	3C3CxTPxCSfQius+NAK0eilSyYfGok4aggFFBF6yNomarzkCGU3rm27OmTuMIB/yZzGI
	sTnxExLCzU3WagAbdvMh8fQGGaMxm1rU4P5DAHjZi7s4cA2gn/B1Rpyu/6P//OfstRZM
	QO/Tdc7eSbwtcCIf+xHbhj6e5TusNBzJTxXhp1BH6SyV9d0hnteMhNSKmfNLvL+t8DnR
	jNvVxAHTofQgC49X0pqPD0UDPdXVIFNjOFqmUkocUAj7OCDlfiju+XGhciFwfAL4e6zc
	/RdQ==
X-Received: by 10.50.22.101 with SMTP id c5mr1787674igf.17.1382785071442; Sat,
	26 Oct 2013 03:57:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.26.233 with HTTP; Sat, 26 Oct 2013 03:57:31 -0700 (PDT)
In-Reply-To: <526B18BC.5050302@alphalem.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CAAQYJAu+wU0ODvVoTrRBFhVOUVh+CdMg3mimfgGkj-pwJh3A1g@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
	<52686723.4080305@windriver.com>
	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>
	<526B18BC.5050302@alphalem.com>
From: Diego Sueiro <diego.sueiro@gmail.com>
Date: Sat, 26 Oct 2013 08:57:31 -0200
Message-ID: <CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gmail.com>
To: Mike Lewis <mikelewis@alphalem.com>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Oct 2013 10:57:53 -0000
Content-Type: multipart/alternative; boundary=047d7b10c9cbfc0f9904e9a2bc3a

--047d7b10c9cbfc0f9904e9a2bc3a
Content-Type: text/plain; charset=ISO-8859-1

Bruce,

We have two scenarios here:

   1. bbapend with full defconfig replacement
   2. bbapend with config fragments

The first scenario just worked when using FILESPATH_prepend. For me it does
not make sense, since on YP manual says that FILESEXTRAPATHS_prepend must
be use [1].

The second scenario did not worked even changing to FILESPATH_prepend.


[1] -
http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-FILESEXTRAPATHS



Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/


2013/10/25 Mike Lewis <mikelewis@alphalem.com>

> Bruce: yep, fixed my issue. Sorry for the bother!
>
> Diego: thanks for the solution!
>
> - Mike
>
>
> On 10/25/2013 11:44 AM, Bruce Ashfield wrote:
>
>> On Fri, Oct 25, 2013 at 7:43 AM, Diego Sueiro <diego.sueiro@gmail.com>
>> wrote:
>>
>>> Bruce,
>>>
>>> Regarding the defconfig not used, I've found this thread on Angstrom
>>> devel
>>> ML:
>>> http://www.mail-archive.com/**angstrom-distro-devel@**
>>> linuxtogo.org/msg06721.html<http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg06721.html>
>>>
>>> I've replaced "FILESEXTRAPATHS_prepend" with "FILESPATH_prepend" and
>>> removed
>>> the custom "do_configure_prepend" function and bitbake is now using my
>>> defconfig.
>>> So, it seems that there is an issue with FILESEXTRAPATHS variable.
>>>
>>>  Aha. That does make sense.
>>
>> Mike: does that same change fix your issues ?
>>
>> Bruce
>>
>>  Regards,
>>>
>>> --
>>> *dS
>>> Diego Sueiro
>>>
>>> /*long live rock 'n roll*/
>>>
>>>
>>> 2013/10/23 Bruce Ashfield <bruce.ashfield@windriver.com>
>>>
>>>> On 13-10-22 12:23 PM, Mike Lewis wrote:
>>>>
>>>>> Hi Bruce,
>>>>>
>>>>> I'm trying to accomplish the nearly the same thing (i.e. adding config
>>>>> fragment) and I'm having the same issue at the do_patch step. Were you
>>>>> able to reproduce this on your end?
>>>>>
>>>>
>>>> Mike,
>>>>
>>>> Is you config/layer somewhere than I can have a look at it ? I was
>>>> trying
>>>> some builds here, and my tests are working. But I'd like to try it
>>>> with your config as well.
>>>>
>>>> Bruce
>>>>
>>>>
>>>>  Thanks,
>>>>> Mike
>>>>>
>>>>> On 10/18/2013 01:17 PM, Bruce Ashfield wrote:
>>>>>
>>>>>> On 13-10-18 05:17 AM, Diego Sueiro wrote:
>>>>>>
>>>>>>>
>>>>>>> 2013/10/18 Bruce Ashfield <bruce.ashfield@windriver.com
>>>>>>> <mailto:bruce.ashfield@**windriver.com<bruce.ashfield@windriver.com>
>>>>>>> >>
>>>>>>>
>>>>>>>      I fell behind today .. i had 2300 unread email to start this
>>>>>>> morning :)
>>>>>>>      Is there a way that I can get a copy of your recipes and layers
>>>>>>> ?
>>>>>>> If
>>>>>>>      I can do a build myself, I can easily debug and fix this ..
>>>>>>>      otherwise, we'll
>>>>>>>      go back and forth many times debugging.
>>>>>>>
>>>>>>>      Cheers,
>>>>>>>
>>>>>>>      Bruce
>>>>>>>
>>>>>>>
>>>>>>> I'm using the environment provided by Angstrom from it's github setup
>>>>>>> scripts.
>>>>>>> If you want to exactly reproduce it you need to:
>>>>>>>
>>>>>>>      git clone
>>>>>>> https://github.com/Angstrom-**distribution/setup-scripts.git<https://github.com/Angstrom-distribution/setup-scripts.git>
>>>>>>>      cd setup-scripts
>>>>>>>      git checkout angstrom-v2013.06-yocto1.4
>>>>>>>      MACHINE=beaglebone ./oebb.sh config beaglebone
>>>>>>>
>>>>>>> Here is the setup and files for meta-mine:
>>>>>>>
>>>>>>> bblayers.conf:
>>>>>>>
>>>>>>>      BBLAYERS = \"
>>>>>>>
>>>>>>>          ...
>>>>>>>          ${TOPDIR}/sources/meta-mine \
>>>>>>>          "
>>>>>>>
>>>>>>> meta-mine/conf/layer.conf:
>>>>>>>
>>>>>>>      # We have a conf and classes directory, append to BBPATH
>>>>>>>      BBPATH .= ":${LAYERDIR}"
>>>>>>>      # We have a recipes directory, add to BBFILES
>>>>>>>      BBFILES += "${LAYERDIR}/recipes*/*/*.bb
>>>>>>>      ${LAYERDIR}/recipes*/*/*.**bbappend"
>>>>>>>      BBFILE_COLLECTIONS += "mine-layer"
>>>>>>>      BBFILE_PATTERN_mine-layer := "^${LAYERDIR}/"
>>>>>>>      BBFILE_PRIORITY_mine-layer = "10"
>>>>>>>      LAYERDEPENDS_mine-layer = "angstrom-layer"
>>>>>>>
>>>>>>> meta-mine/recipes-kernel/**linux/linux-mainline_3.8.**bbappend:
>>>>>>>
>>>>>>>      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 "
>>>>>>>
>>>>>>> meta-mine/recipes-kernel/**linux/linux-mainline-3.8/**
>>>>>>> config-addons.cfg:
>>>>>>>
>>>>>>>      CONFIG_WATCHDOG_NOWAYOUT=y
>>>>>>>      CONFIG_NTFS_FS=y
>>>>>>>      CONFIG_NTFS_RW=y
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> But I think that instead of using the whole Angstrom you can just use
>>>>>>> poky and meta-beagleboard/common-bsp on dylan branch.
>>>>>>>
>>>>>>
>>>>>> Great. I'll launch some test builds and see what breaks (or works) :)
>>>>>>
>>>>>> Bruce
>>>>>>
>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> --
>>>>>>> *dS
>>>>>>> Diego Sueiro
>>>>>>>
>>>>>>> /*long live rock 'n roll*/
>>>>>>>
>>>>>>
>>>>>> ______________________________**_________________
>>>>>> yocto mailing list
>>>>>> yocto@yoctoproject.org
>>>>>> https://lists.yoctoproject.**org/listinfo/yocto<https://lists.yoctoproject.org/listinfo/yocto>
>>>>>>
>>>>>
>>>>>  ______________________________**_________________
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://lists.yoctoproject.**org/listinfo/yocto<https://lists.yoctoproject.org/listinfo/yocto>
>>>>
>>>
>>>
>>> ______________________________**_________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.**org/listinfo/yocto<https://lists.yoctoproject.org/listinfo/yocto>
>>>
>>>
>>
>>
>

--047d7b10c9cbfc0f9904e9a2bc3a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Bruce,<div><br></div><div style>We have two scenarios here=
:</div><div style><ol style><li style>bbapend with full defconfig replaceme=
nt</li><li style>bbapend with config fragments</li></ol><div style>The firs=
t scenario just worked when using=A0<span style=3D"font-family:arial,sans-s=
erif;font-size:13px">FILESPATH_prepend. For me it does not make sense, sinc=
e on YP manual says that=A0</span><span style=3D"font-family:arial,sans-ser=
if;font-size:13px">FILESEXTRAPATHS_prepend</span><span style=3D"font-family=
:arial,sans-serif;font-size:13px">=A0must be use [1].</span></div>

<div style><span style=3D"font-family:arial,sans-serif;font-size:13px"><br>=
</span></div><div style><span style=3D"font-family:arial,sans-serif;font-si=
ze:13px">The second scenario did not worked even changing to=A0</span><span=
 style=3D"font-family:arial,sans-serif;font-size:13px">FILESPATH_prepend.</=
span></div>

<div style><span style=3D"font-family:arial,sans-serif;font-size:13px"><br>=
</span></div><div style><br></div><div style><span style=3D"font-family:ari=
al,sans-serif;font-size:13px">[1] -=A0</span><a href=3D"http://www.yoctopro=
ject.org/docs/current/mega-manual/mega-manual.html#var-FILESEXTRAPATHS">htt=
p://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-FILE=
SEXTRAPATHS</a></div>

</div><div style><br></div><div style><br></div><div class=3D"gmail_extra">=
<br clear=3D"all"><div><div dir=3D"ltr"><div>Regards,</div><div><br></div>-=
-<br>*dS<br>Diego Sueiro<br><br>/*long live rock &#39;n roll*/<br></div></d=
iv>


<br><br><div class=3D"gmail_quote">2013/10/25 Mike Lewis <span dir=3D"ltr">=
&lt;<a href=3D"mailto:mikelewis@alphalem.com" target=3D"_blank">mikelewis@a=
lphalem.com</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,=
204);border-left-style:solid;padding-left:1ex">

Bruce: yep, fixed my issue. Sorry for the bother!<br>
<br>
Diego: thanks for the solution!<span class=3D""><font color=3D"#888888"><br=
>
<br>
- Mike</font></span><div class=3D""><div class=3D"h5"><br>
<br>
On 10/25/2013 11:44 AM, Bruce Ashfield wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
On Fri, Oct 25, 2013 at 7:43 AM, Diego Sueiro &lt;<a href=3D"mailto:diego.s=
ueiro@gmail.com" target=3D"_blank">diego.sueiro@gmail.com</a>&gt; wrote:<br=
>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
Bruce,<br>
<br>
Regarding the defconfig not used, I&#39;ve found this thread on Angstrom de=
vel<br>
ML:<br>
<a href=3D"http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/=
msg06721.html" target=3D"_blank">http://www.mail-archive.com/<u></u>angstro=
m-distro-devel@<u></u>linuxtogo.org/msg06721.html</a><br>
<br>
I&#39;ve replaced &quot;FILESEXTRAPATHS_prepend&quot; with &quot;FILESPATH_=
prepend&quot; and removed<br>
the custom &quot;do_configure_prepend&quot; function and bitbake is now usi=
ng my<br>
defconfig.<br>
So, it seems that there is an issue with FILESEXTRAPATHS variable.<br>
<br>
</blockquote>
Aha. That does make sense.<br>
<br>
Mike: does that same change fix your issues ?<br>
<br>
Bruce<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
Regards,<br>
<br>
--<br>
*dS<br>
Diego Sueiro<br>
<br>
/*long live rock &#39;n roll*/<br>
<br>
<br>
2013/10/23 Bruce Ashfield &lt;<a href=3D"mailto:bruce.ashfield@windriver.co=
m" target=3D"_blank">bruce.ashfield@windriver.com</a>&gt;<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
On <a href=3D"tel:13-10-22%2012" value=3D"+13102212" target=3D"_blank">13-1=
0-22 12</a>:23 PM, Mike Lewis wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
Hi Bruce,<br>
<br>
I&#39;m trying to accomplish the nearly the same thing (i.e. adding config<=
br>
fragment) and I&#39;m having the same issue at the do_patch step. Were you<=
br>
able to reproduce this on your end?<br>
</blockquote>
<br>
Mike,<br>
<br>
Is you config/layer somewhere than I can have a look at it ? I was trying<b=
r>
some builds here, and my tests are working. But I&#39;d like to try it<br>
with your config as well.<br>
<br>
Bruce<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
Thanks,<br>
Mike<br>
<br>
On 10/18/2013 01:17 PM, Bruce Ashfield wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
On <a href=3D"tel:13-10-18%2005" value=3D"+13101805" target=3D"_blank">13-1=
0-18 05</a>:17 AM, Diego Sueiro wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
<br>
2013/10/18 Bruce Ashfield &lt;<a href=3D"mailto:bruce.ashfield@windriver.co=
m" target=3D"_blank">bruce.ashfield@windriver.com</a><br>
&lt;mailto:<a href=3D"mailto:bruce.ashfield@windriver.com" target=3D"_blank=
">bruce.ashfield@<u></u>windriver.com</a>&gt;&gt;<br>
<br>
=A0 =A0 =A0I fell behind today .. i had 2300 unread email to start this<br>
morning :)<br>
=A0 =A0 =A0Is there a way that I can get a copy of your recipes and layers =
?<br>
If<br>
=A0 =A0 =A0I can do a build myself, I can easily debug and fix this ..<br>
=A0 =A0 =A0otherwise, we&#39;ll<br>
=A0 =A0 =A0go back and forth many times debugging.<br>
<br>
=A0 =A0 =A0Cheers,<br>
<br>
=A0 =A0 =A0Bruce<br>
<br>
<br>
I&#39;m using the environment provided by Angstrom from it&#39;s github set=
up<br>
scripts.<br>
If you want to exactly reproduce it you need to:<br>
<br>
=A0 =A0 =A0git clone<br>
<a href=3D"https://github.com/Angstrom-distribution/setup-scripts.git" targ=
et=3D"_blank">https://github.com/Angstrom-<u></u>distribution/setup-scripts=
.git</a><br>
=A0 =A0 =A0cd setup-scripts<br>
=A0 =A0 =A0git checkout angstrom-v2013.06-yocto1.4<br>
=A0 =A0 =A0MACHINE=3Dbeaglebone ./oebb.sh config beaglebone<br>
<br>
Here is the setup and files for meta-mine:<br>
<br>
bblayers.conf:<br>
<br>
=A0 =A0 =A0BBLAYERS =3D \&quot;<br>
<br>
=A0 =A0 =A0 =A0 =A0...<br>
=A0 =A0 =A0 =A0 =A0${TOPDIR}/sources/meta-mine \<br>
=A0 =A0 =A0 =A0 =A0&quot;<br>
<br>
meta-mine/conf/layer.conf:<br>
<br>
=A0 =A0 =A0# We have a conf and classes directory, append to BBPATH<br>
=A0 =A0 =A0BBPATH .=3D &quot;:${LAYERDIR}&quot;<br>
=A0 =A0 =A0# We have a recipes directory, add to BBFILES<br>
=A0 =A0 =A0BBFILES +=3D &quot;${LAYERDIR}/recipes*/*/*.bb<br>
=A0 =A0 =A0${LAYERDIR}/recipes*/*/*.<u></u>bbappend&quot;<br>
=A0 =A0 =A0BBFILE_COLLECTIONS +=3D &quot;mine-layer&quot;<br>
=A0 =A0 =A0BBFILE_PATTERN_mine-layer :=3D &quot;^${LAYERDIR}/&quot;<br>
=A0 =A0 =A0BBFILE_PRIORITY_mine-layer =3D &quot;10&quot;<br>
=A0 =A0 =A0LAYERDEPENDS_mine-layer =3D &quot;angstrom-layer&quot;<br>
<br>
meta-mine/recipes-kernel/<u></u>linux/linux-mainline_3.8.<u></u>bbappend:<b=
r>
<br>
=A0 =A0 =A0FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/${PN}-3.8:&quot;<b=
r>
=A0 =A0 =A0inherit kernel<br>
=A0 =A0 =A0require recipes-kernel/linux/linux-<u></u>yocto.inc<br>
=A0 =A0 =A0COMPATIBLE_MACHINE_beaglebone =3D &quot;(beaglebone)&quot;<br>
=A0 =A0 =A0SRC_URI +=3D &quot; file://config-addons.cfg &quot;<br>
<br>
meta-mine/recipes-kernel/<u></u>linux/linux-mainline-3.8/<u></u>config-addo=
ns.cfg:<br>
<br>
=A0 =A0 =A0CONFIG_WATCHDOG_NOWAYOUT=3Dy<br>
=A0 =A0 =A0CONFIG_NTFS_FS=3Dy<br>
=A0 =A0 =A0CONFIG_NTFS_RW=3Dy<br>
<br>
<br>
<br>
But I think that instead of using the whole Angstrom you can just use<br>
poky and meta-beagleboard/common-bsp on dylan branch.<br>
</blockquote>
<br>
Great. I&#39;ll launch some test builds and see what breaks (or works) :)<b=
r>
<br>
Bruce<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
<br>
Regards,<br>
<br>
--<br>
*dS<br>
Diego Sueiro<br>
<br>
/*long live rock &#39;n roll*/<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
yocto mailing list<br>
<a href=3D"mailto:yocto@yoctoproject.org" target=3D"_blank">yocto@yoctoproj=
ect.org</a><br>
<a href=3D"https://lists.yoctoproject.org/listinfo/yocto" target=3D"_blank"=
>https://lists.yoctoproject.<u></u>org/listinfo/yocto</a><br>
</blockquote>
<br>
</blockquote>
______________________________<u></u>_________________<br>
yocto mailing list<br>
<a href=3D"mailto:yocto@yoctoproject.org" target=3D"_blank">yocto@yoctoproj=
ect.org</a><br>
<a href=3D"https://lists.yoctoproject.org/listinfo/yocto" target=3D"_blank"=
>https://lists.yoctoproject.<u></u>org/listinfo/yocto</a><br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
yocto mailing list<br>
<a href=3D"mailto:yocto@yoctoproject.org" target=3D"_blank">yocto@yoctoproj=
ect.org</a><br>
<a href=3D"https://lists.yoctoproject.org/listinfo/yocto" target=3D"_blank"=
>https://lists.yoctoproject.<u></u>org/listinfo/yocto</a><br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br></div></div>

--047d7b10c9cbfc0f9904e9a2bc3a--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Bruce.Ashfield@windriver.com>
Received: from mail.windriver.com (mail.windriver.com [147.11.1.11])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id CE8CAE00460
	for <yocto@yoctoproject.org>; Sat, 26 Oct 2013 07:54:29 -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 r9QEsNt1019049
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
	Sat, 26 Oct 2013 07:54:23 -0700 (PDT)
Received: from bruce-ashfields-macbook.local (128.224.20.239) by
	ALA-HCA.corp.ad.wrs.com (147.11.189.40) with Microsoft SMTP Server id
	14.2.347.0; Sat, 26 Oct 2013 07:54:22 -0700
Message-ID: <526BD79D.20501@windriver.com>
Date: Sat, 26 Oct 2013 10:54:21 -0400
From: Bruce Ashfield <bruce.ashfield@windriver.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
	rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Diego Sueiro <diego.sueiro@gmail.com>, Mike Lewis <mikelewis@alphalem.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>	<525FDD08.90400@windriver.com>	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>	<525FE3C9.3070003@windriver.com>	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>	<5260BDA6.4020807@windriver.com>	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>	<5261974C.7010202@windriver.com>
	<5266A665.8030303@alphalem.com>	<52686723.4080305@windriver.com>	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>	<526B18BC.5050302@alphalem.com>
	<CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gm!
	ail.com>
In-Reply-To: <CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gmail.com>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Oct 2013 14:54:32 -0000
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

On 13-10-26 6:57 AM, Diego Sueiro wrote:
> Bruce,
>
> We have two scenarios here:
>
>  1. bbapend with full defconfig replacement
>  2. bbapend with config fragments
>
> The first scenario just worked when using FILESPATH_prepend. For me it
> does not make sense, since on YP manual says that
> FILESEXTRAPATHS_prepend must be use [1].
>
> The second scenario did not worked even changing to FILESPATH_prepend.
>

No problem. I'm going to continue looking into this, since we do want
consistent behaviour with all the methods.

Leave it with me and I'll take care of it, I just wanted to be sure you
could move forward while I dig into things (now that I'm back in the
office).

Bruce


>
> [1] -
> http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-FILESEXTRAPATHS
>
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/
>
>
> 2013/10/25 Mike Lewis <mikelewis@alphalem.com
> <mailto:mikelewis@alphalem.com>>
>
>     Bruce: yep, fixed my issue. Sorry for the bother!
>
>     Diego: thanks for the solution!
>
>     - Mike
>
>
>     On 10/25/2013 11:44 AM, Bruce Ashfield wrote:
>
>         On Fri, Oct 25, 2013 at 7:43 AM, Diego Sueiro
>         <diego.sueiro@gmail.com <mailto:diego.sueiro@gmail.com>> wrote:
>
>             Bruce,
>
>             Regarding the defconfig not used, I've found this thread on
>             Angstrom devel
>             ML:
>             http://www.mail-archive.com/__angstrom-distro-devel@__linuxtogo.org/msg06721.html
>             <http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg06721.html>
>
>             I've replaced "FILESEXTRAPATHS_prepend" with
>             "FILESPATH_prepend" and removed
>             the custom "do_configure_prepend" function and bitbake is
>             now using my
>             defconfig.
>             So, it seems that there is an issue with FILESEXTRAPATHS
>             variable.
>
>         Aha. That does make sense.
>
>         Mike: does that same change fix your issues ?
>
>         Bruce
>
>             Regards,
>
>             --
>             *dS
>             Diego Sueiro
>
>             /*long live rock 'n roll*/
>
>
>             2013/10/23 Bruce Ashfield <bruce.ashfield@windriver.com
>             <mailto:bruce.ashfield@windriver.com>>
>
>                 On 13-10-22 12 <tel:13-10-22%2012>:23 PM, Mike Lewis wrote:
>
>                     Hi Bruce,
>
>                     I'm trying to accomplish the nearly the same thing
>                     (i.e. adding config
>                     fragment) and I'm having the same issue at the
>                     do_patch step. Were you
>                     able to reproduce this on your end?
>
>
>                 Mike,
>
>                 Is you config/layer somewhere than I can have a look at
>                 it ? I was trying
>                 some builds here, and my tests are working. But I'd like
>                 to try it
>                 with your config as well.
>
>                 Bruce
>
>
>                     Thanks,
>                     Mike
>
>                     On 10/18/2013 01:17 PM, Bruce Ashfield wrote:
>
>                         On 13-10-18 05 <tel:13-10-18%2005>:17 AM, Diego
>                         Sueiro wrote:
>
>
>                             2013/10/18 Bruce Ashfield
>                             <bruce.ashfield@windriver.com
>                             <mailto:bruce.ashfield@windriver.com>
>                             <mailto:bruce.ashfield@__windriver.com
>                             <mailto:bruce.ashfield@windriver.com>>>
>
>                                   I fell behind today .. i had 2300
>                             unread email to start this
>                             morning :)
>                                   Is there a way that I can get a copy
>                             of your recipes and layers ?
>                             If
>                                   I can do a build myself, I can easily
>                             debug and fix this ..
>                                   otherwise, we'll
>                                   go back and forth many times debugging.
>
>                                   Cheers,
>
>                                   Bruce
>
>
>                             I'm using the environment provided by
>                             Angstrom from it's github setup
>                             scripts.
>                             If you want to exactly reproduce it you need to:
>
>                                   git clone
>                             https://github.com/Angstrom-__distribution/setup-scripts.git
>                             <https://github.com/Angstrom-distribution/setup-scripts.git>
>                                   cd setup-scripts
>                                   git checkout angstrom-v2013.06-yocto1.4
>                                   MACHINE=beaglebone ./oebb.sh config
>                             beaglebone
>
>                             Here is the setup and files for meta-mine:
>
>                             bblayers.conf:
>
>                                   BBLAYERS = \"
>
>                                       ...
>                                       ${TOPDIR}/sources/meta-mine \
>                                       "
>
>                             meta-mine/conf/layer.conf:
>
>                                   # We have a conf and classes
>                             directory, append to BBPATH
>                                   BBPATH .= ":${LAYERDIR}"
>                                   # We have a recipes directory, add to
>                             BBFILES
>                                   BBFILES += "${LAYERDIR}/recipes*/*/*.bb
>                                   ${LAYERDIR}/recipes*/*/*.__bbappend"
>                                   BBFILE_COLLECTIONS += "mine-layer"
>                                   BBFILE_PATTERN_mine-layer :=
>                             "^${LAYERDIR}/"
>                                   BBFILE_PRIORITY_mine-layer = "10"
>                                   LAYERDEPENDS_mine-layer = "angstrom-layer"
>
>                             meta-mine/recipes-kernel/__linux/linux-mainline_3.8.__bbappend:
>
>                                   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 "
>
>                             meta-mine/recipes-kernel/__linux/linux-mainline-3.8/__config-addons.cfg:
>
>                                   CONFIG_WATCHDOG_NOWAYOUT=y
>                                   CONFIG_NTFS_FS=y
>                                   CONFIG_NTFS_RW=y
>
>
>
>                             But I think that instead of using the whole
>                             Angstrom you can just use
>                             poky and meta-beagleboard/common-bsp on
>                             dylan branch.
>
>
>                         Great. I'll launch some test builds and see what
>                         breaks (or works) :)
>
>                         Bruce
>
>
>                             Regards,
>
>                             --
>                             *dS
>                             Diego Sueiro
>
>                             /*long live rock 'n roll*/
>
>
>                         _________________________________________________
>                         yocto mailing list
>                         yocto@yoctoproject.org
>                         <mailto:yocto@yoctoproject.org>
>                         https://lists.yoctoproject.__org/listinfo/yocto
>                         <https://lists.yoctoproject.org/listinfo/yocto>
>
>
>                 _________________________________________________
>                 yocto mailing list
>                 yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>                 https://lists.yoctoproject.__org/listinfo/yocto
>                 <https://lists.yoctoproject.org/listinfo/yocto>
>
>
>
>             _________________________________________________
>             yocto mailing list
>             yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>             https://lists.yoctoproject.__org/listinfo/yocto
>             <https://lists.yoctoproject.org/listinfo/yocto>
>
>
>
>
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Bruce.Ashfield@windriver.com>
Received: from mail.windriver.com (mail.windriver.com [147.11.1.11])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 87AF2E01793
	for <yocto@yoctoproject.org>; Mon, 28 Oct 2013 13:58:47 -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 r9SKweJX021344
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
	Mon, 28 Oct 2013 13:58:41 -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;
	Mon, 28 Oct 2013 13:58:40 -0700
Message-ID: <526ECFF3.4060207@windriver.com>
Date: Mon, 28 Oct 2013 16:58:27 -0400
From: Bruce Ashfield <bruce.ashfield@windriver.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Diego Sueiro <diego.sueiro@gmail.com>, Mike Lewis <mikelewis@alphalem.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>	<525FDD08.90400@windriver.com>	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>	<525FE3C9.3070003@windriver.com>	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>	<5260BDA6.4020807@windriver.com>	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>	<5261974C.7010202@windriver.com>
	<5266A665.8030303@alphalem.com>	<52686723.4080305@windriver.com>	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>	<526B18BC.5050302@alphalem.com>
	<CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gm!
	ail.com>
In-Reply-To: <CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gmail.com>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Oct 2013 20:58:48 -0000
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

On 13-10-26 06:57 AM, Diego Sueiro wrote:
> Bruce,
>
> We have two scenarios here:
>
>  1. bbapend with full defconfig replacement
>  2. bbapend with config fragments
>
> The first scenario just worked when using FILESPATH_prepend. For me it
> does not make sense, since on YP manual says that
> FILESEXTRAPATHS_prepend must be use [1].
>
> The second scenario did not worked even changing to FILESPATH_prepend.

I ran tests today, using the layers Mike indicated, since it was
a bit easier for me to set up on top of my existing builds.

I'm using dylan for my yocto checkout (not oe-core standalone, since
this is a yocto list/question),

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.

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.

Mike: what were you initially seeing that was different from my results ?

Cheers,

Bruce

>
>
> [1] -
> http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-FILESEXTRAPATHS
>
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/
>
>
> 2013/10/25 Mike Lewis <mikelewis@alphalem.com
> <mailto:mikelewis@alphalem.com>>
>
>     Bruce: yep, fixed my issue. Sorry for the bother!
>
>     Diego: thanks for the solution!
>
>     - Mike
>
>
>     On 10/25/2013 11:44 AM, Bruce Ashfield wrote:
>
>         On Fri, Oct 25, 2013 at 7:43 AM, Diego Sueiro
>         <diego.sueiro@gmail.com <mailto:diego.sueiro@gmail.com>> wrote:
>
>             Bruce,
>
>             Regarding the defconfig not used, I've found this thread on
>             Angstrom devel
>             ML:
>             http://www.mail-archive.com/__angstrom-distro-devel@__linuxtogo.org/msg06721.html
>             <http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg06721.html>
>
>             I've replaced "FILESEXTRAPATHS_prepend" with
>             "FILESPATH_prepend" and removed
>             the custom "do_configure_prepend" function and bitbake is
>             now using my
>             defconfig.
>             So, it seems that there is an issue with FILESEXTRAPATHS
>             variable.
>
>         Aha. That does make sense.
>
>         Mike: does that same change fix your issues ?
>
>         Bruce
>
>             Regards,
>
>             --
>             *dS
>             Diego Sueiro
>
>             /*long live rock 'n roll*/
>
>
>             2013/10/23 Bruce Ashfield <bruce.ashfield@windriver.com
>             <mailto:bruce.ashfield@windriver.com>>
>
>                 On 13-10-22 12 <tel:13-10-22%2012>:23 PM, Mike Lewis wrote:
>
>                     Hi Bruce,
>
>                     I'm trying to accomplish the nearly the same thing
>                     (i.e. adding config
>                     fragment) and I'm having the same issue at the
>                     do_patch step. Were you
>                     able to reproduce this on your end?
>
>
>                 Mike,
>
>                 Is you config/layer somewhere than I can have a look at
>                 it ? I was trying
>                 some builds here, and my tests are working. But I'd like
>                 to try it
>                 with your config as well.
>
>                 Bruce
>
>
>                     Thanks,
>                     Mike
>
>                     On 10/18/2013 01:17 PM, Bruce Ashfield wrote:
>
>                         On 13-10-18 05 <tel:13-10-18%2005>:17 AM, Diego
>                         Sueiro wrote:
>
>
>                             2013/10/18 Bruce Ashfield
>                             <bruce.ashfield@windriver.com
>                             <mailto:bruce.ashfield@windriver.com>
>                             <mailto:bruce.ashfield@__windriver.com
>                             <mailto:bruce.ashfield@windriver.com>>>
>
>                                   I fell behind today .. i had 2300
>                             unread email to start this
>                             morning :)
>                                   Is there a way that I can get a copy
>                             of your recipes and layers ?
>                             If
>                                   I can do a build myself, I can easily
>                             debug and fix this ..
>                                   otherwise, we'll
>                                   go back and forth many times debugging.
>
>                                   Cheers,
>
>                                   Bruce
>
>
>                             I'm using the environment provided by
>                             Angstrom from it's github setup
>                             scripts.
>                             If you want to exactly reproduce it you need to:
>
>                                   git clone
>                             https://github.com/Angstrom-__distribution/setup-scripts.git
>                             <https://github.com/Angstrom-distribution/setup-scripts.git>
>                                   cd setup-scripts
>                                   git checkout angstrom-v2013.06-yocto1.4
>                                   MACHINE=beaglebone ./oebb.sh config
>                             beaglebone
>
>                             Here is the setup and files for meta-mine:
>
>                             bblayers.conf:
>
>                                   BBLAYERS = \"
>
>                                       ...
>                                       ${TOPDIR}/sources/meta-mine \
>                                       "
>
>                             meta-mine/conf/layer.conf:
>
>                                   # We have a conf and classes
>                             directory, append to BBPATH
>                                   BBPATH .= ":${LAYERDIR}"
>                                   # We have a recipes directory, add to
>                             BBFILES
>                                   BBFILES += "${LAYERDIR}/recipes*/*/*.bb
>                                   ${LAYERDIR}/recipes*/*/*.__bbappend"
>                                   BBFILE_COLLECTIONS += "mine-layer"
>                                   BBFILE_PATTERN_mine-layer :=
>                             "^${LAYERDIR}/"
>                                   BBFILE_PRIORITY_mine-layer = "10"
>                                   LAYERDEPENDS_mine-layer = "angstrom-layer"
>
>                             meta-mine/recipes-kernel/__linux/linux-mainline_3.8.__bbappend:
>
>                                   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 "
>
>                             meta-mine/recipes-kernel/__linux/linux-mainline-3.8/__config-addons.cfg:
>
>                                   CONFIG_WATCHDOG_NOWAYOUT=y
>                                   CONFIG_NTFS_FS=y
>                                   CONFIG_NTFS_RW=y
>
>
>
>                             But I think that instead of using the whole
>                             Angstrom you can just use
>                             poky and meta-beagleboard/common-bsp on
>                             dylan branch.
>
>
>                         Great. I'll launch some test builds and see what
>                         breaks (or works) :)
>
>                         Bruce
>
>
>                             Regards,
>
>                             --
>                             *dS
>                             Diego Sueiro
>
>                             /*long live rock 'n roll*/
>
>
>                         _________________________________________________
>                         yocto mailing list
>                         yocto@yoctoproject.org
>                         <mailto:yocto@yoctoproject.org>
>                         https://lists.yoctoproject.__org/listinfo/yocto
>                         <https://lists.yoctoproject.org/listinfo/yocto>
>
>
>                 _________________________________________________
>                 yocto mailing list
>                 yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>                 https://lists.yoctoproject.__org/listinfo/yocto
>                 <https://lists.yoctoproject.org/listinfo/yocto>
>
>
>
>             _________________________________________________
>             yocto mailing list
>             yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>             https://lists.yoctoproject.__org/listinfo/yocto
>             <https://lists.yoctoproject.org/listinfo/yocto>
>
>
>
>
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mikelewis@alphalem.com>
Received: from oproxy13-pub.mail.unifiedlayer.com
	(oproxy13-pub.mail.unifiedlayer.com [69.89.16.30])
	by yocto-www.yoctoproject.org (Postfix) with SMTP id A3DC4E01796
	for <yocto@yoctoproject.org>; Mon, 28 Oct 2013 14:41:16 -0700 (PDT)
Received: (qmail 28407 invoked by uid 0); 28 Oct 2013 21:41:15 -0000
Received: from unknown (HELO box891.bluehost.com) (69.195.124.91)
	by oproxy13.mail.unifiedlayer.com with SMTP; 28 Oct 2013 21:41:15 -0000
Received: from [24.130.51.221] (port=49595 helo=[10.0.0.10])
	by box891.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256)
	(Exim 4.80) (envelope-from <mikelewis@alphalem.com>)
	id 1VauYl-0005OE-KI; Mon, 28 Oct 2013 15:41:15 -0600
Message-ID: <526ED9FB.3060208@alphalem.com>
Date: Mon, 28 Oct 2013 14:41:15 -0700
From: Mike Lewis <mikelewis@alphalem.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/20130827 Icedove/17.0.8
MIME-Version: 1.0
To: Bruce Ashfield <bruce.ashfield@windriver.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>	<525FDD08.90400@windriver.com>	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>	<525FE3C9.3070003@windriver.com>	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>	<5260BDA6.4020807@windriver.com>	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>	<5261974C.7010202@windriver.com>
	<5266A665.8030303@alphalem.com>	<52686723.4080305@windriver.com>	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>	<526B18BC.5050302@alphalem.com>
	<CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gm!
	ail.com> <526ECFF3.4060207@windriver.com>
In-Reply-To: <526ECFF3.4060207@windriver.com>
X-Identified-User: {2749:box891.bluehost.com:alphalem:alphalem.com}
	{sentby:smtp auth 24.130.51.221 authed with
	mikelewis+alphalem.com}
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Oct 2013 21:41:16 -0000
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Bruce,

Thanks for running the tests. I was seeing neither my full defconfig 
(additions included) nor a .cfg with only my additions making it into 
the final config. Just the default beagleboard defconfig from meta-ti.

I wasn't using yocto at the time I was experiencing the issue, so I'll 
add that back in and try to replicate your success. I thought that 
things would be simpler with fewer layers, but maybe that was the cause 
of the problem.

- Mike

On 10/28/2013 01:58 PM, Bruce Ashfield wrote:
> On 13-10-26 06:57 AM, Diego Sueiro wrote:
>> Bruce,
>>
>> We have two scenarios here:
>>
>>  1. bbapend with full defconfig replacement
>>  2. bbapend with config fragments
>>
>> The first scenario just worked when using FILESPATH_prepend. For me it
>> does not make sense, since on YP manual says that
>> FILESEXTRAPATHS_prepend must be use [1].
>>
>> The second scenario did not worked even changing to FILESPATH_prepend.
>
> I ran tests today, using the layers Mike indicated, since it was
> a bit easier for me to set up on top of my existing builds.
>
> I'm using dylan for my yocto checkout (not oe-core standalone, since
> this is a yocto list/question),
>
> 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.
>
> 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.
>
> Mike: what were you initially seeing that was different from my results ?
>
> Cheers,
>
> Bruce
>
>>
>>
>> [1] -
>> http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-FILESEXTRAPATHS 
>>
>>
>>
>>
>> Regards,
>>
>> -- 
>> *dS
>> Diego Sueiro
>>
>> /*long live rock 'n roll*/
>>
>>
>> 2013/10/25 Mike Lewis <mikelewis@alphalem.com
>> <mailto:mikelewis@alphalem.com>>
>>
>>     Bruce: yep, fixed my issue. Sorry for the bother!
>>
>>     Diego: thanks for the solution!
>>
>>     - Mike
>>
>>
>>     On 10/25/2013 11:44 AM, Bruce Ashfield wrote:
>>
>>         On Fri, Oct 25, 2013 at 7:43 AM, Diego Sueiro
>>         <diego.sueiro@gmail.com <mailto:diego.sueiro@gmail.com>> wrote:
>>
>>             Bruce,
>>
>>             Regarding the defconfig not used, I've found this thread on
>>             Angstrom devel
>>             ML:
>> http://www.mail-archive.com/__angstrom-distro-devel@__linuxtogo.org/msg06721.html
>> <http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg06721.html>
>>
>>             I've replaced "FILESEXTRAPATHS_prepend" with
>>             "FILESPATH_prepend" and removed
>>             the custom "do_configure_prepend" function and bitbake is
>>             now using my
>>             defconfig.
>>             So, it seems that there is an issue with FILESEXTRAPATHS
>>             variable.
>>
>>         Aha. That does make sense.
>>
>>         Mike: does that same change fix your issues ?
>>
>>         Bruce
>>
>>             Regards,
>>
>>             --
>>             *dS
>>             Diego Sueiro
>>
>>             /*long live rock 'n roll*/
>>
>>
>>             2013/10/23 Bruce Ashfield <bruce.ashfield@windriver.com
>>             <mailto:bruce.ashfield@windriver.com>>
>>
>>                 On 13-10-22 12 <tel:13-10-22%2012>:23 PM, Mike Lewis 
>> wrote:
>>
>>                     Hi Bruce,
>>
>>                     I'm trying to accomplish the nearly the same thing
>>                     (i.e. adding config
>>                     fragment) and I'm having the same issue at the
>>                     do_patch step. Were you
>>                     able to reproduce this on your end?
>>
>>
>>                 Mike,
>>
>>                 Is you config/layer somewhere than I can have a look at
>>                 it ? I was trying
>>                 some builds here, and my tests are working. But I'd like
>>                 to try it
>>                 with your config as well.
>>
>>                 Bruce
>>
>>
>>                     Thanks,
>>                     Mike
>>
>>                     On 10/18/2013 01:17 PM, Bruce Ashfield wrote:
>>
>>                         On 13-10-18 05 <tel:13-10-18%2005>:17 AM, Diego
>>                         Sueiro wrote:
>>
>>
>>                             2013/10/18 Bruce Ashfield
>>                             <bruce.ashfield@windriver.com
>> <mailto:bruce.ashfield@windriver.com>
>> <mailto:bruce.ashfield@__windriver.com
>> <mailto:bruce.ashfield@windriver.com>>>
>>
>>                                   I fell behind today .. i had 2300
>>                             unread email to start this
>>                             morning :)
>>                                   Is there a way that I can get a copy
>>                             of your recipes and layers ?
>>                             If
>>                                   I can do a build myself, I can easily
>>                             debug and fix this ..
>>                                   otherwise, we'll
>>                                   go back and forth many times 
>> debugging.
>>
>>                                   Cheers,
>>
>>                                   Bruce
>>
>>
>>                             I'm using the environment provided by
>>                             Angstrom from it's github setup
>>                             scripts.
>>                             If you want to exactly reproduce it you 
>> need to:
>>
>>                                   git clone
>> https://github.com/Angstrom-__distribution/setup-scripts.git
>> <https://github.com/Angstrom-distribution/setup-scripts.git>
>>                                   cd setup-scripts
>>                                   git checkout 
>> angstrom-v2013.06-yocto1.4
>>                                   MACHINE=beaglebone ./oebb.sh config
>>                             beaglebone
>>
>>                             Here is the setup and files for meta-mine:
>>
>>                             bblayers.conf:
>>
>>                                   BBLAYERS = \"
>>
>>                                       ...
>> ${TOPDIR}/sources/meta-mine \
>>                                       "
>>
>>                             meta-mine/conf/layer.conf:
>>
>>                                   # We have a conf and classes
>>                             directory, append to BBPATH
>>                                   BBPATH .= ":${LAYERDIR}"
>>                                   # We have a recipes directory, add to
>>                             BBFILES
>>                                   BBFILES += 
>> "${LAYERDIR}/recipes*/*/*.bb
>> ${LAYERDIR}/recipes*/*/*.__bbappend"
>>                                   BBFILE_COLLECTIONS += "mine-layer"
>>                                   BBFILE_PATTERN_mine-layer :=
>>                             "^${LAYERDIR}/"
>>                                   BBFILE_PRIORITY_mine-layer = "10"
>>                                   LAYERDEPENDS_mine-layer = 
>> "angstrom-layer"
>>
>> meta-mine/recipes-kernel/__linux/linux-mainline_3.8.__bbappend:
>>
>>                                   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 "
>>
>> meta-mine/recipes-kernel/__linux/linux-mainline-3.8/__config-addons.cfg:
>>
>>                                   CONFIG_WATCHDOG_NOWAYOUT=y
>>                                   CONFIG_NTFS_FS=y
>>                                   CONFIG_NTFS_RW=y
>>
>>
>>
>>                             But I think that instead of using the whole
>>                             Angstrom you can just use
>>                             poky and meta-beagleboard/common-bsp on
>>                             dylan branch.
>>
>>
>>                         Great. I'll launch some test builds and see what
>>                         breaks (or works) :)
>>
>>                         Bruce
>>
>>
>>                             Regards,
>>
>>                             --
>>                             *dS
>>                             Diego Sueiro
>>
>>                             /*long live rock 'n roll*/
>>
>>
>> _________________________________________________
>>                         yocto mailing list
>>                         yocto@yoctoproject.org
>>                         <mailto:yocto@yoctoproject.org>
>> https://lists.yoctoproject.__org/listinfo/yocto
>> <https://lists.yoctoproject.org/listinfo/yocto>
>>
>>
>> _________________________________________________
>>                 yocto mailing list
>>                 yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>>                 https://lists.yoctoproject.__org/listinfo/yocto
>> <https://lists.yoctoproject.org/listinfo/yocto>
>>
>>
>>
>>             _________________________________________________
>>             yocto mailing list
>>             yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>>             https://lists.yoctoproject.__org/listinfo/yocto
>> <https://lists.yoctoproject.org/listinfo/yocto>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>



From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <diego.sueiro@gmail.com>
Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com
	[209.85.223.181])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 37FA5E0179E
	for <yocto@yoctoproject.org>; Tue, 29 Oct 2013 03:33:37 -0700 (PDT)
Received: by mail-ie0-f181.google.com with SMTP id ar20so13255661iec.40
	for <yocto@yoctoproject.org>; Tue, 29 Oct 2013 03:33:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=ZYPGw0qwlGE598c8z9j8QbUxZ00q2mKSK4hFqPc/R5A=;
	b=wZPEeIHHTybexJqk4p8IeSdTZzPbS1Cc7pyYlxrBG+LxbbHTvsFkyQ22cDzdaZG31u
	M039d8zo2mKPcKs4ZDC8Vqh9PslFzXr5U8odlIRbwYDXGzYtevqPB9wzYo599nyd5IwS
	fzub5cITkgKxfSiE+TWN6XmAuTLtdqC5cfq6P77Gmii+3V7dYlWVKHMOQkiETiXOXJmV
	IYNLkANhWmcxGfilFi9s6TllugLZOkRhBjD7Hl81OVHkNUMXNjjWeKHfXXDt7lOtPklC
	uTgh1r8bCWSH3/pBCabZPuHLouyjbf11MZ8suemrHO6GhEJGsloX/fxHclB6WoqCjbN5
	oBgw==
X-Received: by 10.50.26.36 with SMTP id i4mr11968239igg.33.1383042817045; Tue,
	29 Oct 2013 03:33:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.26.233 with HTTP; Tue, 29 Oct 2013 03:33:15 -0700 (PDT)
In-Reply-To: <526ECFF3.4060207@windriver.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
	<52686723.4080305@windriver.com>
	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>
	<526B18BC.5050302@alphalem.com>
	<CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gmail.com>
	<526ECFF3.4060207@windriver.com>
From: Diego Sueiro <diego.sueiro@gmail.com>
Date: Tue, 29 Oct 2013 08:33:15 -0200
Message-ID: <CAMCfZKFnYB3DKSejuZ3JT-uwo=rNekOT3bUcFvuAHdnJnqFONg@mail.gmail.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Oct 2013 10:33:40 -0000
Content-Type: multipart/alternative; boundary=047d7bd76fe0d1c6ef04e9debf24

--047d7bd76fe0d1c6ef04e9debf24
Content-Type: text/plain; charset=ISO-8859-1

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:**3dc4505f0e744177ae4ddff1e1ce8b**31b95dfaa6"
> meta-ti           = "master:**c14c386946e1ea341faeea292580e3**7d538d645d"
> meta-alphalem     = "master:**a5c0e8ff51297a4090cd47d669b4fc**9c94696908"
> meta-alphalem-bsp = "master:**56086e4dc618e975c9a46491793041**f0d18e47a2"
>
> 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*/

--047d7bd76fe0d1c6ef04e9debf24
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
2013/10/28 Bruce Ashfield <span dir=3D"ltr">&lt;<a href=3D"mailto:bruce.ash=
field@windriver.com" target=3D"_blank">bruce.ashfield@windriver.com</a>&gt;=
</span><br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"overflow:hidden">I&#39;m using=
 dylan for my yocto checkout (not oe-core standalone, since<br>
this is a yocto list/question),<br></div></blockquote><div>I thought that o=
pemenbedded-core and poky were sharing the same core components, classes an=
d functions.<br></div><div><br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


<div style=3D"overflow:hidden">
<br>
My build shows:<br>
<br>
meta<br>
meta-yocto<br>
meta-yocto-bsp =A0 =A0=3D &quot;dylan:<u></u>3dc4505f0e744177ae4ddff1e1ce8b=
<u></u>31b95dfaa6&quot;<br>
meta-ti =A0 =A0 =A0 =A0 =A0 =3D &quot;master:<u></u>c14c386946e1ea341faeea2=
92580e3<u></u>7d538d645d&quot;<br>
meta-alphalem =A0 =A0 =3D &quot;master:<u></u>a5c0e8ff51297a4090cd47d669b4f=
c<u></u>9c94696908&quot;<br>
meta-alphalem-bsp =3D &quot;master:<u></u>56086e4dc618e975c9a46491793041<u>=
</u>f0d18e47a2&quot;<br>
<br>
Mike indicated that he was using dylan for meta-ti, but that doesn&#39;t<br=
>
make a difference either, since for our purposed. It&#39;s kernel.bbclass<b=
r>
and the yocto kernel processing that matters.<br></div></blockquote><div>I&=
#39;ll build a setup with yocto (dylan), meta-beagleboard (dylan) and meta-=
mine to check if I can reproduce the issues.=A0</div><div><br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">


<div style=3D"overflow:hidden">
<br>
In meta-alphalem-bsp, I have linux-mainline_3.2.bbappend, with the<br>
following content:<br>
<br>
&gt; cat linux-mainline_3.2.bbappend<br>
FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/${PN}-3.2:&quot;<br>
<br>
inherit kernel<br>
require recipes-kernel/linux/linux-<u></u>yocto.inc<br>
<br>
COMPATIBLE_MACHINE =3D &quot;(beagleboard)&quot;<br>
<br>
SRC_URI_append =3D &quot; file://defconfig&quot;<br>
SRC_URI_append =3D &quot; file://my_frag.cfg&quot;<br>
<br>
And I added a fragment which has:<br>
<br>
&gt; cat my_frag.cfg<br>
CONFIG_WATCHDOG_NOWAYOUT=3Dy<br>
CONFIG_NTFS_FS=3Dy<br>
CONFIG_NTFS_RW=3Dy<br>
<br>
When both are applied to the kernel build, we should see CONFIG_NTFS_FS<br>
transition from =3Dm to =3Dy:<br>
<br>
&gt; grep CONFIG_NTFS_FS *<br>
defconfig:CONFIG_NTFS_FS=3Dm<br>
my_frag.cfg:CONFIG_NTFS_FS=3Dy<br>
<br>
After invoking linux-mainline&#39;s configure task, I see the following:<br=
>
<br>
&gt; grep CONFIG_NTFS_FS linux-beagleboard-standard-<u></u>build/.config<br=
>
CONFIG_NTFS_FS=3Dy<br>
<br>
And other elements of the defconfig and fragment are properly applied<br>
to the configuration phase.<br>
<br>
I&#39;m also seeing good results on master, which means that I&#39;m at a<b=
r>
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.</div></blockquote></div>For th=
e full defconfig replacement after doing a do_configure I&#39;ve checked .c=
onfig on ${S} and it did not included my CONFIGS.</div><div class=3D"gmail_=
extra">


For config fragment it got stuck on do_patch task.</div><div class=3D"gmail=
_extra"><br><br><br clear=3D"all"><div><div dir=3D"ltr"><div>Regards,</div>
<div><br></div>--<br>*dS<br>Diego Sueiro<br><br>/*long live rock &#39;n rol=
l*/<br></div></div>
</div></div>

--047d7bd76fe0d1c6ef04e9debf24--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <andrea.adami@gmail.com>
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com
	[209.85.215.44])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id EB127E0179E
	for <yocto@yoctoproject.org>; Tue, 29 Oct 2013 04:00:11 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id ep20so6374600lab.3
	for <yocto@yoctoproject.org>; Tue, 29 Oct 2013 04:00:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=VQmTk+GQ3V/aG1f8j/uLgfzpo059mik8g1+jTqVbTUc=;
	b=rNIuou+YEDknaJ1XYEW1PaRWJKBE81WmI5lddfqe09SGj3I0guuakw3qw5HuituBAj
	xAb9zFwS3XeIo5UAt2G9xFkcMPqWTANt4xlpqXH5EeGwqL61G3ElpByNjK6A4Myih4fk
	cDUbDwmVIx3+iV89+AvR9RX5XIQWJpnz2SkxfRdOAXgXtnA/zieoRInVRokLmUcnHviC
	B5Uxs1dLpOo5GSt0wjK4/BUWQwkOICnx8QJRZFdsJS49c60uoeCwbJhBSMyAJzIBygoe
	8qkY8VZKwAlLrgV624MY3LcuR2VAJJNWT065Hy4zYFgKI7/3wiVofFBaUaT4OkFuDZjd
	JMJA==
MIME-Version: 1.0
X-Received: by 10.152.116.109 with SMTP id jv13mr4936033lab.30.1383044410185; 
	Tue, 29 Oct 2013 04:00:10 -0700 (PDT)
Received: by 10.112.52.74 with HTTP; Tue, 29 Oct 2013 04:00:10 -0700 (PDT)
In-Reply-To: <CAMCfZKFnYB3DKSejuZ3JT-uwo=rNekOT3bUcFvuAHdnJnqFONg@mail.gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
	<52686723.4080305@windriver.com>
	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>
	<526B18BC.5050302@alphalem.com>
	<CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gmail.com>
	<526ECFF3.4060207@windriver.com>
	<CAMCfZKFnYB3DKSejuZ3JT-uwo=rNekOT3bUcFvuAHdnJnqFONg@mail.gmail.com>
Date: Tue, 29 Oct 2013 12:00:10 +0100
Message-ID: <CAAQYJAuCDgpYKA9VPA35pYEq31HRhxN3gM1S6LRrNqcJbTFK0Q@mail.gmail.com>
From: Andrea Adami <andrea.adami@gmail.com>
To: Diego Sueiro <diego.sueiro@gmail.com>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Oct 2013 11:00:17 -0000
Content-Type: text/plain; charset=ISO-8859-1

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


From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <diego.sueiro@gmail.com>
Received: from mail-ie0-f178.google.com (mail-ie0-f178.google.com
	[209.85.223.178])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id B9ABAE01737
	for <yocto@yoctoproject.org>; Tue, 29 Oct 2013 07:56:08 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id x13so14521379ief.9
	for <yocto@yoctoproject.org>; Tue, 29 Oct 2013 07:56:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=QgZe2q3xvzJG3pBegYn55/8KnC8CWLgUaM2VmI51hgA=;
	b=A5pWgh6mLDPjj/d0vTkoJAYi65JLB9EiWsOv98lMz3cJsum88stawmb3V51b5DTosg
	viBYqdY/sP1KlbXLEnWey8Zk5rR58t+27oZdUnb0Li4g836J7rAO1Uhxu5+mwTH8qQbd
	p1Wc6c3PyEQ9wCMlBtOLAre3x3YrOKCKmU6J/ZW2H2KhAaN0cePh0KHT+vNgI6V3UcpA
	NriGPxrvdtapYGfrJZHxRT/qXgpFZNpZA7/rnRRUCix/rbIzrA3+5MAeYaR0rKZgNA6m
	iyhnmSXDWiOaODwxc7tRyCmgQGnoovJpx62zyDFRrsvOp4OvihU0WQYTMCxifzj+mALn
	3lqg==
X-Received: by 10.50.26.36 with SMTP id i4mr12847149igg.33.1383058567924; Tue,
	29 Oct 2013 07:56:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.26.233 with HTTP; Tue, 29 Oct 2013 07:55:47 -0700 (PDT)
In-Reply-To: <CAAQYJAuCDgpYKA9VPA35pYEq31HRhxN3gM1S6LRrNqcJbTFK0Q@mail.gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
	<52686723.4080305@windriver.com>
	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>
	<526B18BC.5050302@alphalem.com>
	<CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gmail.com>
	<526ECFF3.4060207@windriver.com>
	<CAMCfZKFnYB3DKSejuZ3JT-uwo=rNekOT3bUcFvuAHdnJnqFONg@mail.gmail.com>
	<CAAQYJAuCDgpYKA9VPA35pYEq31HRhxN3gM1S6LRrNqcJbTFK0Q@mail.gmail.com>
From: Diego Sueiro <diego.sueiro@gmail.com>
Date: Tue, 29 Oct 2013 12:55:47 -0200
Message-ID: <CAMCfZKFPhz4odA9iMZ5aWzWtT1XR8JX_EHxJQLXyVuy+S7KLqg@mail.gmail.com>
To: Andrea Adami <andrea.adami@gmail.com>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Oct 2013 14:56:11 -0000
Content-Type: multipart/alternative; boundary=047d7bd76fe0a55f2304e9e26aba

--047d7bd76fe0a55f2304e9e26aba
Content-Type: text/plain; charset=ISO-8859-1

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
>

--047d7bd76fe0a55f2304e9e26aba
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra" style=3D"font-family:arial,sans=
-serif;font-size:13px"><div class=3D"im"><div class=3D"gmail_quote">2013/10=
/29 Andrea Adami=A0<span dir=3D"ltr">&lt;<a href=3D"mailto:andrea.adami@gma=
il.com" target=3D"_blank">andrea.adami@gmail.com</a>&gt;</span><br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div style=3D"overflow:hidden">I&#39;ll jump in one more t=
ime...<br>

<br>Have you tried putting defconfig and patch under &lt;machine&gt; subdir=
?<br><br>recipes-kernel/linux/linux-yocto-3.2/&lt;machine&gt;<br>defconfig<=
br>my-own.patch<br><br>I&#39;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>Andrea,</div><div class=3D"gma=
il_extra" style=3D"font-family:arial,sans-serif;font-size:13px"><br></div>
<div class=3D"gmail_extra" style=3D"font-family:arial,sans-serif;font-size:=
13px">
I did it before and not worked.</div><div class=3D"gmail_extra" style=3D"fo=
nt-family:arial,sans-serif;font-size:13px">I&#39;ll do it again just to mak=
e sure.</div><div class=3D"" style=3D"font-family:arial,sans-serif;font-siz=
e:13px">

<div id=3D":3l5" class=3D"" tabindex=3D"0"><img class=3D"" src=3D"https://m=
ail.google.com/mail/u/0/images/cleardot.gif" style=3D"max-width: 100%;"></d=
iv></div><div class=3D"im" style=3D"font-family:arial,sans-serif;font-size:=
13px"><div class=3D"gmail_extra">

<br><br clear=3D"all"><div><div dir=3D"ltr"><div>Regards,</div><div><br></d=
iv>--<br>*dS<br>Diego Sueiro<br><br>/*long live rock &#39;n roll*/</div></d=
iv></div></div><div class=3D"gmail_extra"><div><div dir=3D"ltr"><br></div><=
/div>

<br><div class=3D"gmail_quote">2013/10/29 Andrea Adami <span dir=3D"ltr">&l=
t;<a href=3D"mailto:andrea.adami@gmail.com" target=3D"_blank">andrea.adami@=
gmail.com</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div class=3D"HOEnZb"><div class=3D"h5">On Tue, Oct 29, 2013 at 11:33 AM, D=
iego Sueiro &lt;<a href=3D"mailto:diego.sueiro@gmail.com">diego.sueiro@gmai=
l.com</a>&gt; wrote:<br>
&gt;<br>
&gt; 2013/10/28 Bruce Ashfield &lt;<a href=3D"mailto:bruce.ashfield@windriv=
er.com">bruce.ashfield@windriver.com</a>&gt;<br>
&gt;&gt;<br>
&gt;&gt; I&#39;m using dylan for my yocto checkout (not oe-core standalone,=
 since<br>
&gt;&gt; this is a yocto list/question),<br>
&gt;<br>
&gt; I thought that opemenbedded-core and poky were sharing the same core<b=
r>
&gt; components, classes and functions.<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; My build shows:<br>
&gt;&gt;<br>
&gt;&gt; meta<br>
&gt;&gt; meta-yocto<br>
&gt;&gt; meta-yocto-bsp =A0 =A0=3D &quot;dylan:3dc4505f0e744177ae4ddff1e1ce=
8b31b95dfaa6&quot;<br>
&gt;&gt; meta-ti =A0 =A0 =A0 =A0 =A0 =3D &quot;master:c14c386946e1ea341faee=
a292580e37d538d645d&quot;<br>
&gt;&gt; meta-alphalem =A0 =A0 =3D &quot;master:a5c0e8ff51297a4090cd47d669b=
4fc9c94696908&quot;<br>
&gt;&gt; meta-alphalem-bsp =3D &quot;master:56086e4dc618e975c9a46491793041f=
0d18e47a2&quot;<br>
&gt;&gt;<br>
&gt;&gt; Mike indicated that he was using dylan for meta-ti, but that doesn=
&#39;t<br>
&gt;&gt; make a difference either, since for our purposed. It&#39;s kernel.=
bbclass<br>
&gt;&gt; and the yocto kernel processing that matters.<br>
&gt;<br>
&gt; I&#39;ll build a setup with yocto (dylan), meta-beagleboard (dylan) an=
d<br>
&gt; meta-mine to check if I can reproduce the issues.<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; In meta-alphalem-bsp, I have linux-mainline_3.2.bbappend, with the=
<br>
&gt;&gt; following content:<br>
&gt;&gt;<br>
&gt;&gt; &gt; cat linux-mainline_3.2.bbappend<br>
&gt;&gt; FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/${PN}-3.2:&quot;<br>
&gt;&gt;<br>
&gt;&gt; inherit kernel<br>
&gt;&gt; require recipes-kernel/linux/linux-yocto.inc<br>
&gt;&gt;<br>
&gt;&gt; COMPATIBLE_MACHINE =3D &quot;(beagleboard)&quot;<br>
&gt;&gt;<br>
&gt;&gt; SRC_URI_append =3D &quot; file://defconfig&quot;<br>
&gt;&gt; SRC_URI_append =3D &quot; file://my_frag.cfg&quot;<br>
&gt;&gt;<br>
&gt;&gt; And I added a fragment which has:<br>
&gt;&gt;<br>
&gt;&gt; &gt; cat my_frag.cfg<br>
&gt;&gt; CONFIG_WATCHDOG_NOWAYOUT=3Dy<br>
&gt;&gt; CONFIG_NTFS_FS=3Dy<br>
&gt;&gt; CONFIG_NTFS_RW=3Dy<br>
&gt;&gt;<br>
&gt;&gt; When both are applied to the kernel build, we should see CONFIG_NT=
FS_FS<br>
&gt;&gt; transition from =3Dm to =3Dy:<br>
&gt;&gt;<br>
&gt;&gt; &gt; grep CONFIG_NTFS_FS *<br>
&gt;&gt; defconfig:CONFIG_NTFS_FS=3Dm<br>
&gt;&gt; my_frag.cfg:CONFIG_NTFS_FS=3Dy<br>
&gt;&gt;<br>
&gt;&gt; After invoking linux-mainline&#39;s configure task, I see the foll=
owing:<br>
&gt;&gt;<br>
&gt;&gt; &gt; grep CONFIG_NTFS_FS linux-beagleboard-standard-build/.config<=
br>
&gt;&gt; CONFIG_NTFS_FS=3Dy<br>
&gt;&gt;<br>
&gt;&gt; And other elements of the defconfig and fragment are properly appl=
ied<br>
&gt;&gt; to the configuration phase.<br>
&gt;&gt;<br>
&gt;&gt; I&#39;m also seeing good results on master, which means that I&#39=
;m at a<br>
&gt;&gt; standstill to reproduce any problems.<br>
&gt;&gt;<br>
&gt;&gt; Diego: can you confirm for me what triggers you are seeing that sh=
ows<br>
&gt;&gt; the defconfig and fragment are not used. I assume the config optio=
ns<br>
&gt;&gt; are not present, but I just want to be sure.<br>
&gt;<br>
&gt; For the full defconfig replacement after doing a do_configure I&#39;ve=
 checked<br>
&gt; .config on ${S} and it did not included my CONFIGS.<br>
&gt; For config fragment it got stuck on do_patch task.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Regards,<br>
&gt;<br>
&gt; --<br>
&gt; *dS<br>
&gt; Diego Sueiro<br>
&gt;<br>
&gt; /*long live rock &#39;n roll*/<br>
&gt;<br>
</div></div><div class=3D"im">&gt; ________________________________________=
_______<br>
&gt; yocto mailing list<br>
&gt; <a href=3D"mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a><b=
r>
&gt; <a href=3D"https://lists.yoctoproject.org/listinfo/yocto" target=3D"_b=
lank">https://lists.yoctoproject.org/listinfo/yocto</a><br>
&gt;<br>
<br>
</div>I&#39;ll jump in one more time...<br>
<br>
Have you tried putting defconfig and patch under &lt;machine&gt; subdir?<br=
>
<br>
recipes-kernel/linux/linux-yocto-3.2/&lt;machine&gt;<br>
defconfig<br>
my-own.patch<br>
<br>
I&#39;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 class=3D"HOEnZb"><font color=3D"#888888"><br>
Andrea<br>
</font></span></blockquote></div><br></div></div>

--047d7bd76fe0a55f2304e9e26aba--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <diego.sueiro@gmail.com>
Received: from mail-ie0-f180.google.com (mail-ie0-f180.google.com
	[209.85.223.180])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 5DE74E017A6
	for <yocto@yoctoproject.org>; Tue, 29 Oct 2013 08:31:27 -0700 (PDT)
Received: by mail-ie0-f180.google.com with SMTP id e14so8003iej.39
	for <yocto@yoctoproject.org>; Tue, 29 Oct 2013 08:31:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=jJeriTGe0LpJ6UWXdT10BJgGnThmVmVjBpotQ7mENHY=;
	b=HvRofs9hKIsRsyPfZQa+md+Rh8iH6iPYSCMxOVlQ0N4iSTLv3PgKcvLsXVHWzRXlfd
	az+AFI1EjnswR6q0qE/k2QuzwuG7iCb3Fx40rVgsVwNl55mwfMMqTI8X7WnMk97VFXMk
	AdhtTVCWt8SHMTcCO4dDzQ/rhhv5pyc674LXWVr4oP4GVMu0Op6XBwyYvcMovcjwOGYB
	pHkiMEag7M/jvSO05lw9k4f8WhclTXirjz967GZoKmX90X5SJebvcIz342u2OPm7wbsD
	jeF7AIIuYs/eP0P4Nry05iUwdaRexOodPBZSWAyNLPMxGAu9X9f8KttdOwVozvsmW86z
	lwvA==
X-Received: by 10.50.61.179 with SMTP id q19mr12966960igr.33.1383060686175;
	Tue, 29 Oct 2013 08:31:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.26.233 with HTTP; Tue, 29 Oct 2013 08:31:06 -0700 (PDT)
In-Reply-To: <CAMCfZKFPhz4odA9iMZ5aWzWtT1XR8JX_EHxJQLXyVuy+S7KLqg@mail.gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CAMCfZKF_Rp=uds8tnDPSD9k3GO5dEiHSx9WfYjZ0yPkmh_9YPg@mail.gmail.com>
	<CAMCfZKFh8iJH4655mzFveFYfz8ebLXkGftSa-MR5mEcMEFV8Vw@mail.gmail.com>
	<CADkTA4MgxmiOofDLynbOLR=hV-KQ1ic+Eagjm0yetYOtB6FJzw@mail.gmail.com>
	<CAMCfZKF3aHG4wFMRx2XcdroJJ6ga5v6KHF5DbBTWV7jXOGNX-g@mail.gmail.com>
	<525FDD08.90400@windriver.com>
	<CAMCfZKHz82sPsHXjqxbFDJjFNi7ck+BS=_OtyGmb2FYDAxoe1A@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
	<52686723.4080305@windriver.com>
	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>
	<526B18BC.5050302@alphalem.com>
	<CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gmail.com>
	<526ECFF3.4060207@windriver.com>
	<CAMCfZKFnYB3DKSejuZ3JT-uwo=rNekOT3bUcFvuAHdnJnqFONg@mail.gmail.com>
	<CAAQYJAuCDgpYKA9VPA35pYEq31HRhxN3gM1S6LRrNqcJbTFK0Q@mail.gmail.com>
	<CAMCfZKFPhz4odA9iMZ5aWzWtT1XR8JX_EHxJQLXyVuy+S7KLqg@mail.gmail.com>
From: Diego Sueiro <diego.sueiro@gmail.com>
Date: Tue, 29 Oct 2013 13:31:06 -0200
Message-ID: <CAMCfZKHaRRVcx5YG+7DJ10-4DE_n9titOG7+aB3R+4H8iZjGvw@mail.gmail.com>
To: Andrea Adami <andrea.adami@gmail.com>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Oct 2013 15:31:28 -0000
Content-Type: multipart/alternative; boundary=047d7bdc109ee71c2704e9e2e8d9

--047d7bdc109ee71c2704e9e2e8d9
Content-Type: text/plain; charset=ISO-8859-1

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.

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
>>
>
>

--047d7bdc109ee71c2704e9e2e8d9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Bruce,<div><br></div><div>I&#39;ve created new build setup=
 with this configuration:<br></div><div><blockquote style=3D"margin:0px 0px=
 0px 40px;border:none;padding:0px"><div><div>BB_VERSION =A0 =A0 =A0 =A0=3D =
&quot;1.18.0&quot;</div>


<div>BUILD_SYS =A0 =A0 =A0 =A0 =3D &quot;x86_64-linux&quot;</div><div>NATIV=
ELSBSTRING =A0 =3D &quot;Ubuntu-12.10&quot;</div><div>TARGET_SYS =A0 =A0 =
=A0 =A0=3D &quot;arm-poky-linux-gnueabi&quot;</div><div>MACHINE =A0 =A0 =A0=
 =A0 =A0 =3D &quot;beaglebone&quot;</div>


<div>DISTRO =A0 =A0 =A0 =A0 =A0 =A0=3D &quot;poky&quot;</div><div>DISTRO_VE=
RSION =A0 =A0=3D &quot;1.4.2&quot;</div><div>TUNE_FEATURES =A0 =A0 =3D &quo=
t;armv7a vfp neon&quot;</div><div>TARGET_FPU =A0 =A0 =A0 =A0=3D &quot;vfp-n=
eon&quot;</div><div>meta =A0 =A0 =A0 =A0 =A0 =A0 =A0</div>


<div>meta-yocto =A0 =A0 =A0 =A0</div><div>meta-yocto-bsp =A0 =A0=3D &quot;d=
ylan:4e399f08d596197859214fdb3b06403b87bf8789&quot;</div><div>meta-oe =A0 =
=A0 =A0 =A0 =A0 =3D &quot;dylan:a108b2203a997634f87ac687e81712badaf3c546&qu=
ot;</div><div>common-bsp =A0 =A0 =A0 =A0=3D &quot;dylan:7fdf9c670a10c5031a2=
d5555c15c45e453de8c21&quot;</div>


<div>meta-mine =A0 =A0 =A0 =A0 =3D &quot;dylan:4e399f08d596197859214fdb3b06=
403b87bf8789&quot;</div></div><div><br></div></blockquote></div><div>common=
-bsp comes from meta-beagleboard.</div><div>meta-oe needed to be added beca=
use of=A0machine_kernel_pr.bbclass.<br>



</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">bblay=
ers.conf:</div><div class=3D"gmail_extra"><blockquote style=3D"margin:0px 0=
px 0px 40px;border:none;padding:0px"><div class=3D"gmail_extra">
<div class=3D"gmail_extra">LCONF_VERSION =3D &quot;6&quot;<br></div><div cl=
ass=3D"gmail_extra">BBPATH =3D &quot;${TOPDIR}&quot;<br></div><div class=3D=
"gmail_extra">BBFILES ?=3D &quot;&quot;</div><div class=3D"gmail_extra">BBL=
AYERS ?=3D &quot; \<br>


</div><div class=3D"gmail_extra">
=A0 ${TOPDIR}/meta \</div><div class=3D"gmail_extra">=A0 ${TOPDIR}/meta-yoc=
to \</div><div class=3D"gmail_extra">=A0 ${TOPDIR}/meta-yocto-bsp \</div><d=
iv class=3D"gmail_extra">=A0 ${TOPDIR}/meta-openembedded/meta-oe \</div><di=
v class=3D"gmail_extra">



=A0 ${TOPDIR}/meta-beagleboard/common-bsp \</div><div class=3D"gmail_extra"=
>=A0 ${TOPDIR}/meta-mine \</div><div class=3D"gmail_extra">=A0 &quot;</div>=
<div><br></div></div></blockquote></div><div class=3D"gmail_extra">meta-min=
e:<br></div>


<div class=3D"gmail_extra"><blockquote style=3D"margin:0px 0px 0px 40px;bor=
der:none;padding:0px"><div class=3D"gmail_extra">conf/layer.conf:</div></bl=
ockquote></div><blockquote style=3D"margin:0px 0px 0px 40px;border:none;pad=
ding:0px">



<div class=3D"gmail_extra"><blockquote style=3D"margin:0px 0px 0px 40px;bor=
der:none;padding:0px"><div class=3D"gmail_extra"><div class=3D"gmail_extra"=
>BBPATH .=3D &quot;:${LAYERDIR}&quot;<br></div><div class=3D"gmail_extra">B=
BFILES +=3D &quot;${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbap=
pend&quot;<br>


</div>
<div class=3D"gmail_extra">BBFILE_COLLECTIONS +=3D &quot;my-layer&quot;<br>=
</div><div class=3D"gmail_extra">BBFILE_PATTERN_my-layer :=3D &quot;^${LAYE=
RDIR}/&quot;</div><div class=3D"gmail_extra">BBFILE_PRIORITY_my-layer =3D &=
quot;10&quot;</div>



<div class=3D"gmail_extra"><br></div></div></blockquote></div></blockquote>=
<blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><div =
class=3D"gmail_extra">recipes-kernel/linux/linux-mainline_3.8.bbappend (sce=
nario 1):<br>

</div></blockquote><blockquote style=3D"margin:0px 0px 0px 40px;border:none=
;padding:0px"><blockquote style=3D"margin:0px 0px 0px 40px;border:none;padd=
ing:0px"><div class=3D"gmail_extra" style><div class=3D"gmail_extra">FILESE=
XTRAPATHS_prepend :=3D &quot;${THISDIR}/${PN}-3.8:&quot;</div>

<div class=3D"gmail_extra">COMPATIBLE_MACHINE_beaglebone =3D &quot;(beagleb=
one)&quot;<br></div><div class=3D"gmail_extra">SRC_URI +=3D &quot; file://d=
efconfig \<br></div><div class=3D"gmail_extra">=A0 =A0 =A0 =A0 =A0 =A0 =A0&=
quot;</div></div></blockquote>

</blockquote><blockquote style=3D"margin:0px 0px 0px 40px;border:none;paddi=
ng:0px">recipes-kernel/linux/linux-mainline-3.8/defconfig (scenario 1):<br>=
</blockquote><blockquote style=3D"margin:0px 0px 0px 40px;border:none;paddi=
ng:0px">

<blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><a hr=
ef=3D"http://pastebin.com/qd8B3C5K">http://pastebin.com/qd8B3C5K</a><br></b=
lockquote></blockquote><blockquote style=3D"margin:0px 0px 0px 40px;border:=
none;padding:0px">

<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">recipes-ker=
nel/linux/linux-mainline_3.8.bbappend (scenario 2):<br></div></blockquote><=
blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><block=
quote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px">

<div class=3D"gmail_extra"><div class=3D"gmail_extra">FILESEXTRAPATHS_prepe=
nd :=3D &quot;${THISDIR}/${PN}-3.8:&quot;</div>

<div class=3D"gmail_extra">inherit kernel<br></div><div class=3D"gmail_extr=
a">require recipes-kernel/linux/linux-yocto.inc</div><div class=3D"gmail_ex=
tra">COMPATIBLE_MACHINE_beaglebone =3D &quot;(beaglebone)&quot;<br></div>
<div class=3D"gmail_extra">SRC_URI +=3D &quot; file://config-addons.cfg \<b=
r></div><div class=3D"gmail_extra">=A0 =A0 =A0 =A0 =A0 =A0 =A0&quot;</div><=
/div></blockquote></blockquote><blockquote style=3D"margin:0px 0px 0px 40px=
;border:none;padding:0px">



recipes-kernel/linux/linux-mainline-3.8/config-addons.cfg (scenario 2):</bl=
ockquote><blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0=
px"><blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px">


<blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px">
</blockquote></blockquote></blockquote><blockquote style=3D"margin:0px 0px =
0px 40px;border:none;padding:0px"><blockquote style=3D"margin:0px 0px 0px 4=
0px;border:none;padding:0px">CONFIG_WATCHDOG_NOWAYOUT=3Dy<br><blockquote st=
yle=3D"margin:0px 0px 0px 40px;border:none;padding:0px">



</blockquote>CONFIG_NTFS_FS=3Dy<br>CONFIG_NTFS_RW=3Dy</blockquote></blockqu=
ote><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br></d=
iv><div class=3D"gmail_extra">Results:</div><div class=3D"gmail_extra"><div=
><ul style>

<li style>Scenario 1: Full defconfig=A0replacement</li></ul></div></div><bl=
ockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><div cla=
ss=3D"gmail_extra"><div style>${WORKDIR}/defconfig comes from meta-beaglebo=
ard instead of meta-mine<br>

</div></div></blockquote><blockquote style=3D"margin:0px 0px 0px 40px;borde=
r:none;padding:0px"><div class=3D"gmail_extra"><div style>${S}/.config=A0co=
mes from meta-beagleboard instead of meta-mine</div></div></blockquote><div=
 class=3D"gmail_extra">

<ul style><li style>Scenario 2: Config fragments</li></ul></div><blockquote=
 style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><div class=3D"gm=
ail_extra">&quot;bitbake linux-mainline&quot; got stuck on do_patch</div></=
blockquote>

<blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px">
<div class=3D"gmail_extra">log.do_patch:</div></blockquote><blockquote styl=
e=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><blockquote style=3D"=
margin:0px 0px 0px 40px;border:none;padding:0px"><div class=3D"gmail_extra"=
>
DEBUG: Executing shell function do_patch<br></div></blockquote></blockquote=
><blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><blo=
ckquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><div clas=
s=3D"gmail_extra">

<div class=3D"gmail_extra" style>WARNING: no meta data branch found ...</di=
v></div></blockquote></blockquote><blockquote style=3D"margin:0px 0px 0px 4=
0px;border:none;padding:0px"><blockquote style=3D"margin:0px 0px 0px 40px;b=
order:none;padding:0px">

<div class=3D"gmail_extra"><div class=3D"gmail_extra" style>Switched to bra=
nch &#39;linux-3.8.y&#39;</div></div></blockquote></blockquote><blockquote =
style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"><blockquote style=
=3D"margin:0px 0px 0px 40px;border:none;padding:0px">

<div class=3D"gmail_extra"><div class=3D"gmail_extra" style>[INFO] validati=
ng against known patches =A0(beaglebone-standard-meta)</div></div></blockqu=
ote></blockquote><div class=3D"gmail_extra"><div>
<br></div></div><div class=3D"gmail_extra"><br clear=3D"all"><div><div dir=
=3D"ltr"><div>Regards,</div><div><br></div>--<br>*dS<br>
Diego Sueiro<br><br>/*long live rock &#39;n roll*/<br></div></div>
<br><br><div class=3D"gmail_quote">2013/10/29 Diego Sueiro <span dir=3D"ltr=
">&lt;<a href=3D"mailto:diego.sueiro@gmail.com" target=3D"_blank">diego.sue=
iro@gmail.com</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,20=
4,204);border-left-style:solid;padding-left:1ex">



<div dir=3D"ltr"><div class=3D"gmail_extra" style=3D"font-family:arial,sans=
-serif;font-size:13px"><div><div><div class=3D"gmail_quote">2013/10/29 Andr=
ea Adami=A0<span dir=3D"ltr">&lt;<a href=3D"mailto:andrea.adami@gmail.com" =
target=3D"_blank">andrea.adami@gmail.com</a>&gt;</span><br>




<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div style=3D"overflow:hidden">I&#39;ll jump in one more t=
ime...<br>




<br>Have you tried putting defconfig and patch under &lt;machine&gt; subdir=
?<br><br>recipes-kernel/linux/linux-yocto-3.2/&lt;machine&gt;<br>defconfig<=
br>my-own.patch<br><br>I&#39;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 c=
lass=3D"gmail_extra" style=3D"font-family:arial,sans-serif;font-size:13px">



<br></div><div class=3D"gmail_extra" style=3D"font-family:arial,sans-serif;=
font-size:13px">
I did it before and not worked.</div><div class=3D"gmail_extra" style=3D"fo=
nt-family:arial,sans-serif;font-size:13px">I&#39;ll do it again just to mak=
e sure.</div></div><div style=3D"font-family:arial,sans-serif;font-size:13p=
x">




<div><img src=3D"https://mail.google.com/mail/u/0/images/cleardot.gif" styl=
e=3D"max-width: 100%;"></div></div><div><div style=3D"font-family:arial,san=
s-serif;font-size:13px"><div class=3D"gmail_extra">
<br><br clear=3D"all"><div><div dir=3D"ltr"><div>Regards,</div><div><br></d=
iv>--<br>*dS<br>Diego Sueiro<br><br>/*long live rock &#39;n roll*/</div></d=
iv></div></div></div><div><div><div class=3D"gmail_extra"><div><div dir=3D"=
ltr">



<br></div></div>
<br><div class=3D"gmail_quote">2013/10/29 Andrea Adami <span dir=3D"ltr">&l=
t;<a href=3D"mailto:andrea.adami@gmail.com" target=3D"_blank">andrea.adami@=
gmail.com</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,20=
4);border-left-style:solid;padding-left:1ex">




<div><div>On Tue, Oct 29, 2013 at 11:33 AM, Diego Sueiro &lt;<a href=3D"mai=
lto:diego.sueiro@gmail.com" target=3D"_blank">diego.sueiro@gmail.com</a>&gt=
; wrote:<br>
&gt;<br>
&gt; 2013/10/28 Bruce Ashfield &lt;<a href=3D"mailto:bruce.ashfield@windriv=
er.com" target=3D"_blank">bruce.ashfield@windriver.com</a>&gt;<br>
&gt;&gt;<br>
&gt;&gt; I&#39;m using dylan for my yocto checkout (not oe-core standalone,=
 since<br>
&gt;&gt; this is a yocto list/question),<br>
&gt;<br>
&gt; I thought that opemenbedded-core and poky were sharing the same core<b=
r>
&gt; components, classes and functions.<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; My build shows:<br>
&gt;&gt;<br>
&gt;&gt; meta<br>
&gt;&gt; meta-yocto<br>
&gt;&gt; meta-yocto-bsp =A0 =A0=3D &quot;dylan:3dc4505f0e744177ae4ddff1e1ce=
8b31b95dfaa6&quot;<br>
&gt;&gt; meta-ti =A0 =A0 =A0 =A0 =A0 =3D &quot;master:c14c386946e1ea341faee=
a292580e37d538d645d&quot;<br>
&gt;&gt; meta-alphalem =A0 =A0 =3D &quot;master:a5c0e8ff51297a4090cd47d669b=
4fc9c94696908&quot;<br>
&gt;&gt; meta-alphalem-bsp =3D &quot;master:56086e4dc618e975c9a46491793041f=
0d18e47a2&quot;<br>
&gt;&gt;<br>
&gt;&gt; Mike indicated that he was using dylan for meta-ti, but that doesn=
&#39;t<br>
&gt;&gt; make a difference either, since for our purposed. It&#39;s kernel.=
bbclass<br>
&gt;&gt; and the yocto kernel processing that matters.<br>
&gt;<br>
&gt; I&#39;ll build a setup with yocto (dylan), meta-beagleboard (dylan) an=
d<br>
&gt; meta-mine to check if I can reproduce the issues.<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; In meta-alphalem-bsp, I have linux-mainline_3.2.bbappend, with the=
<br>
&gt;&gt; following content:<br>
&gt;&gt;<br>
&gt;&gt; &gt; cat linux-mainline_3.2.bbappend<br>
&gt;&gt; FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/${PN}-3.2:&quot;<br>
&gt;&gt;<br>
&gt;&gt; inherit kernel<br>
&gt;&gt; require recipes-kernel/linux/linux-yocto.inc<br>
&gt;&gt;<br>
&gt;&gt; COMPATIBLE_MACHINE =3D &quot;(beagleboard)&quot;<br>
&gt;&gt;<br>
&gt;&gt; SRC_URI_append =3D &quot; file://defconfig&quot;<br>
&gt;&gt; SRC_URI_append =3D &quot; file://my_frag.cfg&quot;<br>
&gt;&gt;<br>
&gt;&gt; And I added a fragment which has:<br>
&gt;&gt;<br>
&gt;&gt; &gt; cat my_frag.cfg<br>
&gt;&gt; CONFIG_WATCHDOG_NOWAYOUT=3Dy<br>
&gt;&gt; CONFIG_NTFS_FS=3Dy<br>
&gt;&gt; CONFIG_NTFS_RW=3Dy<br>
&gt;&gt;<br>
&gt;&gt; When both are applied to the kernel build, we should see CONFIG_NT=
FS_FS<br>
&gt;&gt; transition from =3Dm to =3Dy:<br>
&gt;&gt;<br>
&gt;&gt; &gt; grep CONFIG_NTFS_FS *<br>
&gt;&gt; defconfig:CONFIG_NTFS_FS=3Dm<br>
&gt;&gt; my_frag.cfg:CONFIG_NTFS_FS=3Dy<br>
&gt;&gt;<br>
&gt;&gt; After invoking linux-mainline&#39;s configure task, I see the foll=
owing:<br>
&gt;&gt;<br>
&gt;&gt; &gt; grep CONFIG_NTFS_FS linux-beagleboard-standard-build/.config<=
br>
&gt;&gt; CONFIG_NTFS_FS=3Dy<br>
&gt;&gt;<br>
&gt;&gt; And other elements of the defconfig and fragment are properly appl=
ied<br>
&gt;&gt; to the configuration phase.<br>
&gt;&gt;<br>
&gt;&gt; I&#39;m also seeing good results on master, which means that I&#39=
;m at a<br>
&gt;&gt; standstill to reproduce any problems.<br>
&gt;&gt;<br>
&gt;&gt; Diego: can you confirm for me what triggers you are seeing that sh=
ows<br>
&gt;&gt; the defconfig and fragment are not used. I assume the config optio=
ns<br>
&gt;&gt; are not present, but I just want to be sure.<br>
&gt;<br>
&gt; For the full defconfig replacement after doing a do_configure I&#39;ve=
 checked<br>
&gt; .config on ${S} and it did not included my CONFIGS.<br>
&gt; For config fragment it got stuck on do_patch task.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Regards,<br>
&gt;<br>
&gt; --<br>
&gt; *dS<br>
&gt; Diego Sueiro<br>
&gt;<br>
&gt; /*long live rock &#39;n roll*/<br>
&gt;<br>
</div></div><div>&gt; _______________________________________________<br>
&gt; yocto mailing list<br>
&gt; <a href=3D"mailto:yocto@yoctoproject.org" target=3D"_blank">yocto@yoct=
oproject.org</a><br>
&gt; <a href=3D"https://lists.yoctoproject.org/listinfo/yocto" target=3D"_b=
lank">https://lists.yoctoproject.org/listinfo/yocto</a><br>
&gt;<br>
<br>
</div>I&#39;ll jump in one more time...<br>
<br>
Have you tried putting defconfig and patch under &lt;machine&gt; subdir?<br=
>
<br>
recipes-kernel/linux/linux-yocto-3.2/&lt;machine&gt;<br>
defconfig<br>
my-own.patch<br>
<br>
I&#39;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=3D"#888888"><br>
Andrea<br>
</font></span></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div></div>

--047d7bdc109ee71c2704e9e2e8d9--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jukka.rissanen@linux.intel.com>
Received: from mga11.intel.com (mga11.intel.com [192.55.52.93])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 58427E0179A
	for <yocto@yoctoproject.org>; Wed, 30 Oct 2013 00:57:37 -0700 (PDT)
Received: from fmsmga002.fm.intel.com ([10.253.24.26])
	by fmsmga102.fm.intel.com with ESMTP; 30 Oct 2013 00:57:26 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.93,599,1378882800"; d="scan'208";a="425010345"
Received: from sorvi.fi.intel.com (HELO [10.237.72.152]) ([10.237.72.152])
	by fmsmga002.fm.intel.com with ESMTP; 30 Oct 2013 00:57:22 -0700
Message-ID: <5270BBDF.8040905@linux.intel.com>
Date: Wed, 30 Oct 2013 09:57:19 +0200
From: Jukka Rissanen <jukka.rissanen@linux.intel.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version: 1.0
To: Diego Sueiro <diego.sueiro@gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
In-Reply-To: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Oct 2013 07:57:41 -0000
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Diego,

On 16.10.2013 00:07, Diego Sueiro wrote:
> Folks,
>
> I created the following bbapend recipe for linux-mainline_3.8.bb
> <http://linux-mainline_3.8.bb> (from meta-beagleboard on dylan branch)
> for beaglebone.
> meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
>
>     FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>     SRC_URI += " file://0019-mine.patch \
>                   file://defconfig \
>                   "
>
> But the defconfig and .config files on ${S} and ${WORKDIR} used are from
> meta-beagleboad, not from my bbappend.

I did this like this in 
http://git.yoctoproject.org/cgit/cgit.cgi/meta-eca/tree/meta-eca-bsp/recipes-kernel/linux/linux-mainline_3.8.bbappend


FILESEXTRAPATHS_append := ":${THISDIR}/${PN}"

# netfilter stuff is missing from beaglebone kernel
SRC_URI_append_beaglebone += "file://netfilter.cfg"

do_configure_append_beaglebone () {
	for i in ${S}/../*.cfg; do
		echo "Adding ${i} to ${S}/.config"
		cat ${i} >> ${S}/.config
	done

	yes '' | oe_runmake oldconfig
}


Seems to work just fine for me.


-- 
Cheers,
Jukka


From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bruce.ashfield@gmail.com>
Received: from mail-lb0-f170.google.com (mail-lb0-f170.google.com
	[209.85.217.170])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id D026BE017AF
	for <yocto@yoctoproject.org>; Wed, 30 Oct 2013 05:27:19 -0700 (PDT)
Received: by mail-lb0-f170.google.com with SMTP id u14so1154339lbd.29
	for <yocto@yoctoproject.org>; Wed, 30 Oct 2013 05:27:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=55FgURuYsYtvbVHqt0b7yWE5x4HrPAfLiz38U+aK4No=;
	b=0JEsiRviNzL7J4rFrtUBsiJlepsitzOkDVa2ARMBLyth7oKPS2Y/CLkSSj4G9Mokr+
	F4u5iYDe808PwjGDK5Mc2kh2cpq/S71oavJcKwxAIS9bwY68XSFd9k59/qWMnpoY0SKL
	TCBh2c7kIhel753kv6KoSBVq1w7p5T/uqoX1eYn3ljyc4v3dtyZ8cclh0WLcKZaJwvMK
	NCgou2pJhyKnEu2qeGKkfy8Zts7cNAQqX4R7VI6mKkZn7mqK29AoG8UgqGhBVfSNeXzP
	dX0MnDbR/+TuLH08PsuO9eLGC40qkNm1+33uje9hlD9z3AsEbRd/dk+3QThexJRfivv9
	kyxQ==
MIME-Version: 1.0
X-Received: by 10.112.130.6 with SMTP id oa6mr23398lbb.62.1383136038486; Wed,
	30 Oct 2013 05:27:18 -0700 (PDT)
Received: by 10.112.14.200 with HTTP; Wed, 30 Oct 2013 05:27:18 -0700 (PDT)
In-Reply-To: <5270BBDF.8040905@linux.intel.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<5270BBDF.8040905@linux.intel.com>
Date: Wed, 30 Oct 2013 08:27:18 -0400
Message-ID: <CADkTA4OtaOs-D_hOXL7UrjDaeaSW_sWANdLWSMW+2CjRd=5ubw@mail.gmail.com>
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Oct 2013 12:27:23 -0000
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Oct 30, 2013 at 3:57 AM, Jukka Rissanen
<jukka.rissanen@linux.intel.com> wrote:
> Hi Diego,
>
>
> On 16.10.2013 00:07, Diego Sueiro wrote:
>>
>> Folks,
>>
>> I created the following bbapend recipe for linux-mainline_3.8.bb
>> <http://linux-mainline_3.8.bb> (from meta-beagleboard on dylan branch)
>>
>> for beaglebone.
>> meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
>>
>>     FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>>     SRC_URI += " file://0019-mine.patch \
>>                   file://defconfig \
>>                   "
>>
>> But the defconfig and .config files on ${S} and ${WORKDIR} used are from
>> meta-beagleboad, not from my bbappend.
>
>
> I did this like this in
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-eca/tree/meta-eca-bsp/recipes-kernel/linux/linux-mainline_3.8.bbappend
>
>
> FILESEXTRAPATHS_append := ":${THISDIR}/${PN}"
>
> # netfilter stuff is missing from beaglebone kernel
> SRC_URI_append_beaglebone += "file://netfilter.cfg"
>
> do_configure_append_beaglebone () {
>         for i in ${S}/../*.cfg; do
>                 echo "Adding ${i} to ${S}/.config"
>                 cat ${i} >> ${S}/.config
>         done
>
>         yes '' | oe_runmake oldconfig
> }
>
>
> Seems to work just fine for me.
>

But that's *really* not the point.

Having configuration fragments applied and managed is more than a brute force
concatenation of the contents, letting lkc do what it wants to them,
without reporting
and control is what

There's something in place, that already does this and more, which has
the ability
to scale to more complex cases.

What I'm trying to understand is what exactly is different in Diego's
setup, since
the exact cases reported here work fine for me, Andrea and any number of other
people. Something strange is going on.

We need to be patient and work through this, so if there's a bug in the already
available infrastructure, we can flush it out :)

Bruce

>
> --
> Cheers,
> Jukka
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"


From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Bruce.Ashfield@windriver.com>
Received: from mail.windriver.com (mail.windriver.com [147.11.1.11])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id E292BE017B0
	for <yocto@yoctoproject.org>; 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 <bruce.ashfield@windriver.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Diego Sueiro <diego.sueiro@gmail.com>, Andrea Adami
	<andrea.adami@gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
	<52686723.4080305@windriver.com>
	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>
	<526B18BC.5050302@alphalem.com>
	<CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gmail.com>
	<526ECFF3.4060207@windriver.com>
	<CAMCfZKFnYB3DKSejuZ3JT-uwo=rNekOT3bUcFvuAHdnJnqFONg@mail.gmail.com>
	<CAAQYJAuCDgpYKA9VPA35pYEq31HRhxN3gM1S6LRrNqcJbTFK0Q@mail.gmail.com>
	<CAMCfZKFPhz4odA9iMZ5aWzWtT1XR8JX_EHxJQLXyVuy+S7KLqg@mail.gmail.com>
	<CAMCfZKHaRRVcx5YG+7DJ10-4DE_n9titOG7+aB3R+4H8iZjGvw@mail.gmail.com>
In-Reply-To: <CAMCfZKHaRRVcx5YG+7DJ10-4DE_n9titOG7+aB3R+4H8iZjGvw@mail.gmail.com>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=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 <diego.sueiro@gmail.com 
> <mailto:diego.sueiro@gmail.com>>
>
>     2013/10/29 Andrea Adami <andrea.adami@gmail.com
>     <mailto: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
>     <mailto:andrea.adami@gmail.com>>
>
>         On Tue, Oct 29, 2013 at 11:33 AM, Diego Sueiro
>         <diego.sueiro@gmail.com <mailto:diego.sueiro@gmail.com>> wrote:
>         >
>         > 2013/10/28 Bruce Ashfield <bruce.ashfield@windriver.com
>         <mailto: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 <mailto: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
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<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 &nbsp; &nbsp; &nbsp; &nbsp;= "1.18.0"</div>
              <div>BUILD_SYS &nbsp; &nbsp; &nbsp; &nbsp; = "x86_64-linux"</div>
              <div>NATIVELSBSTRING &nbsp; = "Ubuntu-12.10"</div>
              <div>TARGET_SYS &nbsp; &nbsp; &nbsp; &nbsp;= "arm-poky-linux-gnueabi"</div>
              <div>MACHINE &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; = "beaglebone"</div>
              <div>DISTRO &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;= "poky"</div>
              <div>DISTRO_VERSION &nbsp; &nbsp;= "1.4.2"</div>
              <div>TUNE_FEATURES &nbsp; &nbsp; = "armv7a vfp neon"</div>
              <div>TARGET_FPU &nbsp; &nbsp; &nbsp; &nbsp;= "vfp-neon"</div>
              <div>meta &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</div>
              <div>meta-yocto &nbsp; &nbsp; &nbsp; &nbsp;</div>
              <div>meta-yocto-bsp &nbsp; &nbsp;=
                "dylan:4e399f08d596197859214fdb3b06403b87bf8789"</div>
              <div>meta-oe &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
                "dylan:a108b2203a997634f87ac687e81712badaf3c546"</div>
              <div>common-bsp &nbsp; &nbsp; &nbsp; &nbsp;=
                "dylan:7fdf9c670a10c5031a2d5555c15c45e453de8c21"</div>
              <div>meta-mine &nbsp; &nbsp; &nbsp; &nbsp; =
                "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&nbsp;machine_kernel_pr.bbclass.<br>
        </div>
      </div>
    </blockquote>
    <br>
    FYI: I've created this exactly environment on my builder. I'll
    follow up<br>
    shortly with the results of the two scenarios.<br>
    <br>
    Honestly, I hope it breaks .. that'll make it much easier to debug
    :)<br>
    <br>
    Bruce<br>
    <br>
    <blockquote
cite="mid:CAMCfZKHaRRVcx5YG+7DJ10-4DE_n9titOG7+aB3R+4H8iZjGvw@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
        </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">
                &nbsp; ${TOPDIR}/meta \</div>
              <div class="gmail_extra">&nbsp; ${TOPDIR}/meta-yocto \</div>
              <div class="gmail_extra">&nbsp; ${TOPDIR}/meta-yocto-bsp \</div>
              <div class="gmail_extra">&nbsp;
                ${TOPDIR}/meta-openembedded/meta-oe \</div>
              <div class="gmail_extra">
                &nbsp; ${TOPDIR}/meta-beagleboard/common-bsp \</div>
              <div class="gmail_extra">&nbsp; ${TOPDIR}/meta-mine \</div>
              <div class="gmail_extra">&nbsp; "</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">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"</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">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"</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&nbsp;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&nbsp;comes from meta-beagleboard
              instead of meta-mine</div>
          </div>
        </blockquote>
        <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 &nbsp;(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">&lt;<a moz-do-not-send="true"
                href="mailto:diego.sueiro@gmail.com" target="_blank">diego.sueiro@gmail.com</a>&gt;</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&nbsp;<span
                          dir="ltr">&lt;<a moz-do-not-send="true"
                            href="mailto:andrea.adami@gmail.com"
                            target="_blank">andrea.adami@gmail.com</a>&gt;</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 &lt;machine&gt; subdir?<br>
                            <br>
recipes-kernel/linux/linux-yocto-3.2/&lt;machine&gt;<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">&lt;<a moz-do-not-send="true"
                            href="mailto:andrea.adami@gmail.com"
                            target="_blank">andrea.adami@gmail.com</a>&gt;</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 &lt;<a moz-do-not-send="true"
                                href="mailto:diego.sueiro@gmail.com"
                                target="_blank">diego.sueiro@gmail.com</a>&gt;
                              wrote:<br>
                              &gt;<br>
                              &gt; 2013/10/28 Bruce Ashfield &lt;<a
                                moz-do-not-send="true"
                                href="mailto:bruce.ashfield@windriver.com"
                                target="_blank">bruce.ashfield@windriver.com</a>&gt;<br>
                              &gt;&gt;<br>
                              &gt;&gt; I'm using dylan for my yocto
                              checkout (not oe-core standalone, since<br>
                              &gt;&gt; this is a yocto list/question),<br>
                              &gt;<br>
                              &gt; I thought that opemenbedded-core and
                              poky were sharing the same core<br>
                              &gt; components, classes and functions.<br>
                              &gt;<br>
                              &gt;&gt;<br>
                              &gt;&gt; My build shows:<br>
                              &gt;&gt;<br>
                              &gt;&gt; meta<br>
                              &gt;&gt; meta-yocto<br>
                              &gt;&gt; meta-yocto-bsp &nbsp; &nbsp;=
                              "dylan:3dc4505f0e744177ae4ddff1e1ce8b31b95dfaa6"<br>
                              &gt;&gt; meta-ti &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
                              "master:c14c386946e1ea341faeea292580e37d538d645d"<br>
                              &gt;&gt; meta-alphalem &nbsp; &nbsp; =
                              "master:a5c0e8ff51297a4090cd47d669b4fc9c94696908"<br>
                              &gt;&gt; meta-alphalem-bsp =
                              "master:56086e4dc618e975c9a46491793041f0d18e47a2"<br>
                              &gt;&gt;<br>
                              &gt;&gt; Mike indicated that he was using
                              dylan for meta-ti, but that doesn't<br>
                              &gt;&gt; make a difference either, since
                              for our purposed. It's kernel.bbclass<br>
                              &gt;&gt; and the yocto kernel processing
                              that matters.<br>
                              &gt;<br>
                              &gt; I'll build a setup with yocto
                              (dylan), meta-beagleboard (dylan) and<br>
                              &gt; meta-mine to check if I can reproduce
                              the issues.<br>
                              &gt;<br>
                              &gt;&gt;<br>
                              &gt;&gt; In meta-alphalem-bsp, I have
                              linux-mainline_3.2.bbappend, with the<br>
                              &gt;&gt; following content:<br>
                              &gt;&gt;<br>
                              &gt;&gt; &gt; cat
                              linux-mainline_3.2.bbappend<br>
                              &gt;&gt; FILESEXTRAPATHS_prepend :=
                              "${THISDIR}/${PN}-3.2:"<br>
                              &gt;&gt;<br>
                              &gt;&gt; inherit kernel<br>
                              &gt;&gt; require
                              recipes-kernel/linux/linux-yocto.inc<br>
                              &gt;&gt;<br>
                              &gt;&gt; COMPATIBLE_MACHINE =
                              "(beagleboard)"<br>
                              &gt;&gt;<br>
                              &gt;&gt; SRC_URI_append = <a class="moz-txt-link-rfc2396E" href="file://defconfig">"
                              file://defconfig"</a><br>
                              &gt;&gt; SRC_URI_append = <a class="moz-txt-link-rfc2396E" href="file://my_frag.cfg">"
                              file://my_frag.cfg"</a><br>
                              &gt;&gt;<br>
                              &gt;&gt; And I added a fragment which has:<br>
                              &gt;&gt;<br>
                              &gt;&gt; &gt; cat my_frag.cfg<br>
                              &gt;&gt; CONFIG_WATCHDOG_NOWAYOUT=y<br>
                              &gt;&gt; CONFIG_NTFS_FS=y<br>
                              &gt;&gt; CONFIG_NTFS_RW=y<br>
                              &gt;&gt;<br>
                              &gt;&gt; When both are applied to the
                              kernel build, we should see CONFIG_NTFS_FS<br>
                              &gt;&gt; transition from =m to =y:<br>
                              &gt;&gt;<br>
                              &gt;&gt; &gt; grep CONFIG_NTFS_FS *<br>
                              &gt;&gt; defconfig:CONFIG_NTFS_FS=m<br>
                              &gt;&gt; my_frag.cfg:CONFIG_NTFS_FS=y<br>
                              &gt;&gt;<br>
                              &gt;&gt; After invoking linux-mainline's
                              configure task, I see the following:<br>
                              &gt;&gt;<br>
                              &gt;&gt; &gt; grep CONFIG_NTFS_FS
                              linux-beagleboard-standard-build/.config<br>
                              &gt;&gt; CONFIG_NTFS_FS=y<br>
                              &gt;&gt;<br>
                              &gt;&gt; And other elements of the
                              defconfig and fragment are properly
                              applied<br>
                              &gt;&gt; to the configuration phase.<br>
                              &gt;&gt;<br>
                              &gt;&gt; I'm also seeing good results on
                              master, which means that I'm at a<br>
                              &gt;&gt; standstill to reproduce any
                              problems.<br>
                              &gt;&gt;<br>
                              &gt;&gt; Diego: can you confirm for me
                              what triggers you are seeing that shows<br>
                              &gt;&gt; the defconfig and fragment are
                              not used. I assume the config options<br>
                              &gt;&gt; are not present, but I just want
                              to be sure.<br>
                              &gt;<br>
                              &gt; For the full defconfig replacement
                              after doing a do_configure I've checked<br>
                              &gt; .config on ${S} and it did not
                              included my CONFIGS.<br>
                              &gt; For config fragment it got stuck on
                              do_patch task.<br>
                              &gt;<br>
                              &gt;<br>
                              &gt;<br>
                              &gt; Regards,<br>
                              &gt;<br>
                              &gt; --<br>
                              &gt; *dS<br>
                              &gt; Diego Sueiro<br>
                              &gt;<br>
                              &gt; /*long live rock 'n roll*/<br>
                              &gt;<br>
                            </div>
                          </div>
                          <div>&gt;
                            _______________________________________________<br>
                            &gt; yocto mailing list<br>
                            &gt; <a moz-do-not-send="true"
                              href="mailto:yocto@yoctoproject.org"
                              target="_blank">yocto@yoctoproject.org</a><br>
                            &gt; <a moz-do-not-send="true"
                              href="https://lists.yoctoproject.org/listinfo/yocto"
                              target="_blank">https://lists.yoctoproject.org/listinfo/yocto</a><br>
                            &gt;<br>
                            <br>
                          </div>
                          I'll jump in one more time...<br>
                          <br>
                          Have you tried putting defconfig and patch
                          under &lt;machine&gt; subdir?<br>
                          <br>
recipes-kernel/linux/linux-yocto-3.2/&lt;machine&gt;<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>

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

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Bruce.Ashfield@windriver.com>
Received: from mail.windriver.com (mail.windriver.com [147.11.1.11])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id AEB91E0173B
	for <yocto@yoctoproject.org>; Wed, 30 Oct 2013 06:54:49 -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 r9UDsmxI023818
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
	Wed, 30 Oct 2013 06:54:48 -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:54:47 -0700
Message-ID: <52710F99.7020701@windriver.com>
Date: Wed, 30 Oct 2013 09:54:33 -0400
From: Bruce Ashfield <bruce.ashfield@windriver.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Diego Sueiro <diego.sueiro@gmail.com>, Andrea Adami
	<andrea.adami@gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
	<52686723.4080305@windriver.com>
	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>
	<526B18BC.5050302@alphalem.com>
	<CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gmail.com>
	<526ECFF3.4060207@windriver.com>
	<CAMCfZKFnYB3DKSejuZ3JT-uwo=rNekOT3bUcFvuAHdnJnqFONg@mail.gmail.com>
	<CAAQYJAuCDgpYKA9VPA35pYEq31HRhxN3gM1S6LRrNqcJbTFK0Q@mail.gmail.com>
	<CAMCfZKFPhz4odA9iMZ5aWzWtT1XR8JX_EHxJQLXyVuy+S7KLqg@mail.gmail.com>
	<CAMCfZKHaRRVcx5YG+7DJ10-4DE_n9titOG7+aB3R+4H8iZjGvw@mail.gmail.com>
In-Reply-To: <CAMCfZKHaRRVcx5YG+7DJ10-4DE_n9titOG7+aB3R+4H8iZjGvw@mail.gmail.com>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Oct 2013 13:54:52 -0000
Content-Type: multipart/alternative;
	boundary="------------000902060905040003010008"

--------------000902060905040003010008
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.
>
> 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
>

I've confirmed this behaviour on dylan when I exactly reproduced
your configuration. The more interesting one is scenario 2, so I'm
trying it out, before looking at #1 in more detail.

Bruce

>   * 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 
> <mailto:diego.sueiro@gmail.com>>
>
>     2013/10/29 Andrea Adami <andrea.adami@gmail.com
>     <mailto: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
>     <mailto:andrea.adami@gmail.com>>
>
>         On Tue, Oct 29, 2013 at 11:33 AM, Diego Sueiro
>         <diego.sueiro@gmail.com <mailto:diego.sueiro@gmail.com>> wrote:
>         >
>         > 2013/10/28 Bruce Ashfield <bruce.ashfield@windriver.com
>         <mailto: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 <mailto: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
>
>
>


--------------000902060905040003010008
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<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 &nbsp; &nbsp; &nbsp; &nbsp;= "1.18.0"</div>
              <div>BUILD_SYS &nbsp; &nbsp; &nbsp; &nbsp; = "x86_64-linux"</div>
              <div>NATIVELSBSTRING &nbsp; = "Ubuntu-12.10"</div>
              <div>TARGET_SYS &nbsp; &nbsp; &nbsp; &nbsp;= "arm-poky-linux-gnueabi"</div>
              <div>MACHINE &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; = "beaglebone"</div>
              <div>DISTRO &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;= "poky"</div>
              <div>DISTRO_VERSION &nbsp; &nbsp;= "1.4.2"</div>
              <div>TUNE_FEATURES &nbsp; &nbsp; = "armv7a vfp neon"</div>
              <div>TARGET_FPU &nbsp; &nbsp; &nbsp; &nbsp;= "vfp-neon"</div>
              <div>meta &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</div>
              <div>meta-yocto &nbsp; &nbsp; &nbsp; &nbsp;</div>
              <div>meta-yocto-bsp &nbsp; &nbsp;=
                "dylan:4e399f08d596197859214fdb3b06403b87bf8789"</div>
              <div>meta-oe &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
                "dylan:a108b2203a997634f87ac687e81712badaf3c546"</div>
              <div>common-bsp &nbsp; &nbsp; &nbsp; &nbsp;=
                "dylan:7fdf9c670a10c5031a2d5555c15c45e453de8c21"</div>
              <div>meta-mine &nbsp; &nbsp; &nbsp; &nbsp; =
                "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&nbsp;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">
                &nbsp; ${TOPDIR}/meta \</div>
              <div class="gmail_extra">&nbsp; ${TOPDIR}/meta-yocto \</div>
              <div class="gmail_extra">&nbsp; ${TOPDIR}/meta-yocto-bsp \</div>
              <div class="gmail_extra">&nbsp;
                ${TOPDIR}/meta-openembedded/meta-oe \</div>
              <div class="gmail_extra">
                &nbsp; ${TOPDIR}/meta-beagleboard/common-bsp \</div>
              <div class="gmail_extra">&nbsp; ${TOPDIR}/meta-mine \</div>
              <div class="gmail_extra">&nbsp; "</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">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"</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">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"</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&nbsp;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&nbsp;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 &nbsp;(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">&lt;<a moz-do-not-send="true"
                href="mailto:diego.sueiro@gmail.com" target="_blank">diego.sueiro@gmail.com</a>&gt;</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&nbsp;<span
                          dir="ltr">&lt;<a moz-do-not-send="true"
                            href="mailto:andrea.adami@gmail.com"
                            target="_blank">andrea.adami@gmail.com</a>&gt;</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 &lt;machine&gt; subdir?<br>
                            <br>
recipes-kernel/linux/linux-yocto-3.2/&lt;machine&gt;<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">&lt;<a moz-do-not-send="true"
                            href="mailto:andrea.adami@gmail.com"
                            target="_blank">andrea.adami@gmail.com</a>&gt;</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 &lt;<a moz-do-not-send="true"
                                href="mailto:diego.sueiro@gmail.com"
                                target="_blank">diego.sueiro@gmail.com</a>&gt;
                              wrote:<br>
                              &gt;<br>
                              &gt; 2013/10/28 Bruce Ashfield &lt;<a
                                moz-do-not-send="true"
                                href="mailto:bruce.ashfield@windriver.com"
                                target="_blank">bruce.ashfield@windriver.com</a>&gt;<br>
                              &gt;&gt;<br>
                              &gt;&gt; I'm using dylan for my yocto
                              checkout (not oe-core standalone, since<br>
                              &gt;&gt; this is a yocto list/question),<br>
                              &gt;<br>
                              &gt; I thought that opemenbedded-core and
                              poky were sharing the same core<br>
                              &gt; components, classes and functions.<br>
                              &gt;<br>
                              &gt;&gt;<br>
                              &gt;&gt; My build shows:<br>
                              &gt;&gt;<br>
                              &gt;&gt; meta<br>
                              &gt;&gt; meta-yocto<br>
                              &gt;&gt; meta-yocto-bsp &nbsp; &nbsp;=
                              "dylan:3dc4505f0e744177ae4ddff1e1ce8b31b95dfaa6"<br>
                              &gt;&gt; meta-ti &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
                              "master:c14c386946e1ea341faeea292580e37d538d645d"<br>
                              &gt;&gt; meta-alphalem &nbsp; &nbsp; =
                              "master:a5c0e8ff51297a4090cd47d669b4fc9c94696908"<br>
                              &gt;&gt; meta-alphalem-bsp =
                              "master:56086e4dc618e975c9a46491793041f0d18e47a2"<br>
                              &gt;&gt;<br>
                              &gt;&gt; Mike indicated that he was using
                              dylan for meta-ti, but that doesn't<br>
                              &gt;&gt; make a difference either, since
                              for our purposed. It's kernel.bbclass<br>
                              &gt;&gt; and the yocto kernel processing
                              that matters.<br>
                              &gt;<br>
                              &gt; I'll build a setup with yocto
                              (dylan), meta-beagleboard (dylan) and<br>
                              &gt; meta-mine to check if I can reproduce
                              the issues.<br>
                              &gt;<br>
                              &gt;&gt;<br>
                              &gt;&gt; In meta-alphalem-bsp, I have
                              linux-mainline_3.2.bbappend, with the<br>
                              &gt;&gt; following content:<br>
                              &gt;&gt;<br>
                              &gt;&gt; &gt; cat
                              linux-mainline_3.2.bbappend<br>
                              &gt;&gt; FILESEXTRAPATHS_prepend :=
                              "${THISDIR}/${PN}-3.2:"<br>
                              &gt;&gt;<br>
                              &gt;&gt; inherit kernel<br>
                              &gt;&gt; require
                              recipes-kernel/linux/linux-yocto.inc<br>
                              &gt;&gt;<br>
                              &gt;&gt; COMPATIBLE_MACHINE =
                              "(beagleboard)"<br>
                              &gt;&gt;<br>
                              &gt;&gt; SRC_URI_append = <a class="moz-txt-link-rfc2396E" href="file://defconfig">"
                              file://defconfig"</a><br>
                              &gt;&gt; SRC_URI_append = <a class="moz-txt-link-rfc2396E" href="file://my_frag.cfg">"
                              file://my_frag.cfg"</a><br>
                              &gt;&gt;<br>
                              &gt;&gt; And I added a fragment which has:<br>
                              &gt;&gt;<br>
                              &gt;&gt; &gt; cat my_frag.cfg<br>
                              &gt;&gt; CONFIG_WATCHDOG_NOWAYOUT=y<br>
                              &gt;&gt; CONFIG_NTFS_FS=y<br>
                              &gt;&gt; CONFIG_NTFS_RW=y<br>
                              &gt;&gt;<br>
                              &gt;&gt; When both are applied to the
                              kernel build, we should see CONFIG_NTFS_FS<br>
                              &gt;&gt; transition from =m to =y:<br>
                              &gt;&gt;<br>
                              &gt;&gt; &gt; grep CONFIG_NTFS_FS *<br>
                              &gt;&gt; defconfig:CONFIG_NTFS_FS=m<br>
                              &gt;&gt; my_frag.cfg:CONFIG_NTFS_FS=y<br>
                              &gt;&gt;<br>
                              &gt;&gt; After invoking linux-mainline's
                              configure task, I see the following:<br>
                              &gt;&gt;<br>
                              &gt;&gt; &gt; grep CONFIG_NTFS_FS
                              linux-beagleboard-standard-build/.config<br>
                              &gt;&gt; CONFIG_NTFS_FS=y<br>
                              &gt;&gt;<br>
                              &gt;&gt; And other elements of the
                              defconfig and fragment are properly
                              applied<br>
                              &gt;&gt; to the configuration phase.<br>
                              &gt;&gt;<br>
                              &gt;&gt; I'm also seeing good results on
                              master, which means that I'm at a<br>
                              &gt;&gt; standstill to reproduce any
                              problems.<br>
                              &gt;&gt;<br>
                              &gt;&gt; Diego: can you confirm for me
                              what triggers you are seeing that shows<br>
                              &gt;&gt; the defconfig and fragment are
                              not used. I assume the config options<br>
                              &gt;&gt; are not present, but I just want
                              to be sure.<br>
                              &gt;<br>
                              &gt; For the full defconfig replacement
                              after doing a do_configure I've checked<br>
                              &gt; .config on ${S} and it did not
                              included my CONFIGS.<br>
                              &gt; For config fragment it got stuck on
                              do_patch task.<br>
                              &gt;<br>
                              &gt;<br>
                              &gt;<br>
                              &gt; Regards,<br>
                              &gt;<br>
                              &gt; --<br>
                              &gt; *dS<br>
                              &gt; Diego Sueiro<br>
                              &gt;<br>
                              &gt; /*long live rock 'n roll*/<br>
                              &gt;<br>
                            </div>
                          </div>
                          <div>&gt;
                            _______________________________________________<br>
                            &gt; yocto mailing list<br>
                            &gt; <a moz-do-not-send="true"
                              href="mailto:yocto@yoctoproject.org"
                              target="_blank">yocto@yoctoproject.org</a><br>
                            &gt; <a moz-do-not-send="true"
                              href="https://lists.yoctoproject.org/listinfo/yocto"
                              target="_blank">https://lists.yoctoproject.org/listinfo/yocto</a><br>
                            &gt;<br>
                            <br>
                          </div>
                          I'll jump in one more time...<br>
                          <br>
                          Have you tried putting defconfig and patch
                          under &lt;machine&gt; subdir?<br>
                          <br>
recipes-kernel/linux/linux-yocto-3.2/&lt;machine&gt;<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>

--------------000902060905040003010008--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <diego.sueiro@gmail.com>
Received: from mail-ie0-f178.google.com (mail-ie0-f178.google.com
	[209.85.223.178])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 7E201E0173C
	for <yocto@yoctoproject.org>; Wed, 30 Oct 2013 07:08:30 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id x13so2334921ief.37
	for <yocto@yoctoproject.org>; Wed, 30 Oct 2013 07:08:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=R1/GEH+OKsmbgiS0hpKKRnC8IZpHoaAaMF8+lNTKKq0=;
	b=Beuc7oxH7tjIuofwQ6dqWKhS5DQNePd7YEXeXbLMG342QwE1G3K0qdYnL0V/FrDnpI
	VqHWYakwO0VIkg2zOgM+VXnvU+v5yPNLM8jnzPwKIZkkLTI7+frD3GfvYSx2WfFvIQLD
	ihlZ2lk1iHKCpr/8W6lC/OZ9e2pptP8Q70N2fl1p97LkG8LYM77uBFJUSeA15WI5x10l
	ftdHNJ4R99QNUSOsWw8d0Wqqq7wBvVlzlSSR7OVy8sgzFZZ5rqEOKPd7VPXdDRzhEbhg
	Qm8a1VGSSw+ISLLqtjkkp5mIlq2mEr9lumn1pbdy/3creuq071nZsTO4i3DfqcuwM6Ux
	Jy4w==
X-Received: by 10.50.43.131 with SMTP id w3mr2520627igl.17.1383142110559; Wed,
	30 Oct 2013 07:08:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.26.233 with HTTP; Wed, 30 Oct 2013 07:08:10 -0700 (PDT)
In-Reply-To: <52710F99.7020701@windriver.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
	<52686723.4080305@windriver.com>
	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>
	<526B18BC.5050302@alphalem.com>
	<CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gmail.com>
	<526ECFF3.4060207@windriver.com>
	<CAMCfZKFnYB3DKSejuZ3JT-uwo=rNekOT3bUcFvuAHdnJnqFONg@mail.gmail.com>
	<CAAQYJAuCDgpYKA9VPA35pYEq31HRhxN3gM1S6LRrNqcJbTFK0Q@mail.gmail.com>
	<CAMCfZKFPhz4odA9iMZ5aWzWtT1XR8JX_EHxJQLXyVuy+S7KLqg@mail.gmail.com>
	<CAMCfZKHaRRVcx5YG+7DJ10-4DE_n9titOG7+aB3R+4H8iZjGvw@mail.gmail.com>
	<52710F99.7020701@windriver.com>
From: Diego Sueiro <diego.sueiro@gmail.com>
Date: Wed, 30 Oct 2013 12:08:10 -0200
Message-ID: <CAMCfZKGkNCo-UCzEW5ZRJBrD-4z3CwgBzL+H8VjeKZdjRPkqTg@mail.gmail.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Oct 2013 14:08:31 -0000
Content-Type: multipart/alternative; boundary=047d7bfea1862c967304e9f5de92

--047d7bfea1862c967304e9f5de92
Content-Type: text/plain; charset=ISO-8859-1

2013/10/30 Bruce Ashfield <bruce.ashfield@windriver.com>

> I've confirmed this behaviour on dylan when I exactly reproduced
> your configuration. The more interesting one is scenario 2, so I'm
> trying it out, before looking at #1 in more detail.
>
Phew, now I'm not feeling crazy.

Looking at linux.inc from meta-beagleboard I can see that there are a lot
of tweaks applied onto kernel config. Maybe it is bricking something.
https://github.com/beagleboard/meta-beagleboard/blob/dylan/common-bsp/recipes-kernel/linux/linux.inc


Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/

--047d7bfea1862c967304e9f5de92
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
2013/10/30 Bruce Ashfield <span dir=3D"ltr">&lt;<a href=3D"mailto:bruce.ash=
field@windriver.com" target=3D"_blank">bruce.ashfield@windriver.com</a>&gt;=
</span><br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div bgcolor=3D"#FFFFFF" text=3D"#000000">I&#39;ve confirm=
ed this behaviour on dylan when I exactly reproduced<br>


    your configuration. The more interesting one is scenario 2, so I&#39;m<=
br>
    trying it out, before looking at #1 in more detail.</div></blockquote><=
/div>Phew, now I&#39;m not feeling crazy.</div><div class=3D"gmail_extra"><=
br></div><div class=3D"gmail_extra" style>Looking at linux.inc from meta-be=
agleboard I can see that there are a lot of tweaks applied onto kernel conf=
ig. Maybe it is bricking something.</div>

<div class=3D"gmail_extra" style><a href=3D"https://github.com/beagleboard/=
meta-beagleboard/blob/dylan/common-bsp/recipes-kernel/linux/linux.inc">http=
s://github.com/beagleboard/meta-beagleboard/blob/dylan/common-bsp/recipes-k=
ernel/linux/linux.inc</a><br>

</div><div class=3D"gmail_extra"><br><br clear=3D"all"><div><div dir=3D"ltr=
"><div>Regards,</div><div><br></div>--<br>*dS<br>Diego Sueiro<br><br>/*long=
 live rock &#39;n roll*/<br></div></div>
</div></div>

--047d7bfea1862c967304e9f5de92--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Bruce.Ashfield@windriver.com>
Received: from mail.windriver.com (mail.windriver.com [147.11.1.11])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 1846EE0173B
	for <yocto@yoctoproject.org>; Wed, 30 Oct 2013 07:26:18 -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 r9UEQF6R028339
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
	Wed, 30 Oct 2013 07:26:16 -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 07:26:15 -0700
Message-ID: <527116F9.4090201@windriver.com>
Date: Wed, 30 Oct 2013 10:26:01 -0400
From: Bruce Ashfield <bruce.ashfield@windriver.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Diego Sueiro <diego.sueiro@gmail.com>, Andrea Adami
	<andrea.adami@gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
	<52686723.4080305@windriver.com>
	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>
	<526B18BC.5050302@alphalem.com>
	<CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gmail.com>
	<526ECFF3.4060207@windriver.com>
	<CAMCfZKFnYB3DKSejuZ3JT-uwo=rNekOT3bUcFvuAHdnJnqFONg@mail.gmail.com>
	<CAAQYJAuCDgpYKA9VPA35pYEq31HRhxN3gM1S6LRrNqcJbTFK0Q@mail.gmail.com>
	<CAMCfZKFPhz4odA9iMZ5aWzWtT1XR8JX_EHxJQLXyVuy+S7KLqg@mail.gmail.com>
	<CAMCfZKHaRRVcx5YG+7DJ10-4DE_n9titOG7+aB3R+4H8iZjGvw@mail.gmail.com>
In-Reply-To: <CAMCfZKHaRRVcx5YG+7DJ10-4DE_n9titOG7+aB3R+4H8iZjGvw@mail.gmail.com>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Oct 2013 14:26:19 -0000
Content-Type: multipart/alternative;
	boundary="------------050101050703010705080605"

--------------050101050703010705080605
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.
>
> 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)
>

.... AND, I can see this now as well. So you are definitely seeing a bug,
give me a few hours and I'll spin a fix, or find out what is configured
wrong and catch it before it causes problems.

Bruce

>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/
>
>
> 2013/10/29 Diego Sueiro <diego.sueiro@gmail.com 
> <mailto:diego.sueiro@gmail.com>>
>
>     2013/10/29 Andrea Adami <andrea.adami@gmail.com
>     <mailto: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
>     <mailto:andrea.adami@gmail.com>>
>
>         On Tue, Oct 29, 2013 at 11:33 AM, Diego Sueiro
>         <diego.sueiro@gmail.com <mailto:diego.sueiro@gmail.com>> wrote:
>         >
>         > 2013/10/28 Bruce Ashfield <bruce.ashfield@windriver.com
>         <mailto: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 <mailto: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
>
>
>


--------------050101050703010705080605
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<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 &nbsp; &nbsp; &nbsp; &nbsp;= "1.18.0"</div>
              <div>BUILD_SYS &nbsp; &nbsp; &nbsp; &nbsp; = "x86_64-linux"</div>
              <div>NATIVELSBSTRING &nbsp; = "Ubuntu-12.10"</div>
              <div>TARGET_SYS &nbsp; &nbsp; &nbsp; &nbsp;= "arm-poky-linux-gnueabi"</div>
              <div>MACHINE &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; = "beaglebone"</div>
              <div>DISTRO &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;= "poky"</div>
              <div>DISTRO_VERSION &nbsp; &nbsp;= "1.4.2"</div>
              <div>TUNE_FEATURES &nbsp; &nbsp; = "armv7a vfp neon"</div>
              <div>TARGET_FPU &nbsp; &nbsp; &nbsp; &nbsp;= "vfp-neon"</div>
              <div>meta &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</div>
              <div>meta-yocto &nbsp; &nbsp; &nbsp; &nbsp;</div>
              <div>meta-yocto-bsp &nbsp; &nbsp;=
                "dylan:4e399f08d596197859214fdb3b06403b87bf8789"</div>
              <div>meta-oe &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
                "dylan:a108b2203a997634f87ac687e81712badaf3c546"</div>
              <div>common-bsp &nbsp; &nbsp; &nbsp; &nbsp;=
                "dylan:7fdf9c670a10c5031a2d5555c15c45e453de8c21"</div>
              <div>meta-mine &nbsp; &nbsp; &nbsp; &nbsp; =
                "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&nbsp;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">
                &nbsp; ${TOPDIR}/meta \</div>
              <div class="gmail_extra">&nbsp; ${TOPDIR}/meta-yocto \</div>
              <div class="gmail_extra">&nbsp; ${TOPDIR}/meta-yocto-bsp \</div>
              <div class="gmail_extra">&nbsp;
                ${TOPDIR}/meta-openembedded/meta-oe \</div>
              <div class="gmail_extra">
                &nbsp; ${TOPDIR}/meta-beagleboard/common-bsp \</div>
              <div class="gmail_extra">&nbsp; ${TOPDIR}/meta-mine \</div>
              <div class="gmail_extra">&nbsp; "</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">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"</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">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"</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&nbsp;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&nbsp;comes from meta-beagleboard
              instead of meta-mine</div>
          </div>
        </blockquote>
        <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 &nbsp;(beaglebone-standard-meta)</div>
            </div>
          </blockquote>
        </blockquote>
      </div>
    </blockquote>
    <br>
    .... AND, I can see this now as well. So you are definitely seeing a
    bug,<br>
    give me a few hours and I'll spin a fix, or find out what is
    configured<br>
    wrong and catch it before it causes problems.<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">
          <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">&lt;<a moz-do-not-send="true"
                href="mailto:diego.sueiro@gmail.com" target="_blank">diego.sueiro@gmail.com</a>&gt;</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&nbsp;<span
                          dir="ltr">&lt;<a moz-do-not-send="true"
                            href="mailto:andrea.adami@gmail.com"
                            target="_blank">andrea.adami@gmail.com</a>&gt;</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 &lt;machine&gt; subdir?<br>
                            <br>
recipes-kernel/linux/linux-yocto-3.2/&lt;machine&gt;<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">&lt;<a moz-do-not-send="true"
                            href="mailto:andrea.adami@gmail.com"
                            target="_blank">andrea.adami@gmail.com</a>&gt;</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 &lt;<a moz-do-not-send="true"
                                href="mailto:diego.sueiro@gmail.com"
                                target="_blank">diego.sueiro@gmail.com</a>&gt;
                              wrote:<br>
                              &gt;<br>
                              &gt; 2013/10/28 Bruce Ashfield &lt;<a
                                moz-do-not-send="true"
                                href="mailto:bruce.ashfield@windriver.com"
                                target="_blank">bruce.ashfield@windriver.com</a>&gt;<br>
                              &gt;&gt;<br>
                              &gt;&gt; I'm using dylan for my yocto
                              checkout (not oe-core standalone, since<br>
                              &gt;&gt; this is a yocto list/question),<br>
                              &gt;<br>
                              &gt; I thought that opemenbedded-core and
                              poky were sharing the same core<br>
                              &gt; components, classes and functions.<br>
                              &gt;<br>
                              &gt;&gt;<br>
                              &gt;&gt; My build shows:<br>
                              &gt;&gt;<br>
                              &gt;&gt; meta<br>
                              &gt;&gt; meta-yocto<br>
                              &gt;&gt; meta-yocto-bsp &nbsp; &nbsp;=
                              "dylan:3dc4505f0e744177ae4ddff1e1ce8b31b95dfaa6"<br>
                              &gt;&gt; meta-ti &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
                              "master:c14c386946e1ea341faeea292580e37d538d645d"<br>
                              &gt;&gt; meta-alphalem &nbsp; &nbsp; =
                              "master:a5c0e8ff51297a4090cd47d669b4fc9c94696908"<br>
                              &gt;&gt; meta-alphalem-bsp =
                              "master:56086e4dc618e975c9a46491793041f0d18e47a2"<br>
                              &gt;&gt;<br>
                              &gt;&gt; Mike indicated that he was using
                              dylan for meta-ti, but that doesn't<br>
                              &gt;&gt; make a difference either, since
                              for our purposed. It's kernel.bbclass<br>
                              &gt;&gt; and the yocto kernel processing
                              that matters.<br>
                              &gt;<br>
                              &gt; I'll build a setup with yocto
                              (dylan), meta-beagleboard (dylan) and<br>
                              &gt; meta-mine to check if I can reproduce
                              the issues.<br>
                              &gt;<br>
                              &gt;&gt;<br>
                              &gt;&gt; In meta-alphalem-bsp, I have
                              linux-mainline_3.2.bbappend, with the<br>
                              &gt;&gt; following content:<br>
                              &gt;&gt;<br>
                              &gt;&gt; &gt; cat
                              linux-mainline_3.2.bbappend<br>
                              &gt;&gt; FILESEXTRAPATHS_prepend :=
                              "${THISDIR}/${PN}-3.2:"<br>
                              &gt;&gt;<br>
                              &gt;&gt; inherit kernel<br>
                              &gt;&gt; require
                              recipes-kernel/linux/linux-yocto.inc<br>
                              &gt;&gt;<br>
                              &gt;&gt; COMPATIBLE_MACHINE =
                              "(beagleboard)"<br>
                              &gt;&gt;<br>
                              &gt;&gt; SRC_URI_append = <a class="moz-txt-link-rfc2396E" href="file://defconfig">"
                              file://defconfig"</a><br>
                              &gt;&gt; SRC_URI_append = <a class="moz-txt-link-rfc2396E" href="file://my_frag.cfg">"
                              file://my_frag.cfg"</a><br>
                              &gt;&gt;<br>
                              &gt;&gt; And I added a fragment which has:<br>
                              &gt;&gt;<br>
                              &gt;&gt; &gt; cat my_frag.cfg<br>
                              &gt;&gt; CONFIG_WATCHDOG_NOWAYOUT=y<br>
                              &gt;&gt; CONFIG_NTFS_FS=y<br>
                              &gt;&gt; CONFIG_NTFS_RW=y<br>
                              &gt;&gt;<br>
                              &gt;&gt; When both are applied to the
                              kernel build, we should see CONFIG_NTFS_FS<br>
                              &gt;&gt; transition from =m to =y:<br>
                              &gt;&gt;<br>
                              &gt;&gt; &gt; grep CONFIG_NTFS_FS *<br>
                              &gt;&gt; defconfig:CONFIG_NTFS_FS=m<br>
                              &gt;&gt; my_frag.cfg:CONFIG_NTFS_FS=y<br>
                              &gt;&gt;<br>
                              &gt;&gt; After invoking linux-mainline's
                              configure task, I see the following:<br>
                              &gt;&gt;<br>
                              &gt;&gt; &gt; grep CONFIG_NTFS_FS
                              linux-beagleboard-standard-build/.config<br>
                              &gt;&gt; CONFIG_NTFS_FS=y<br>
                              &gt;&gt;<br>
                              &gt;&gt; And other elements of the
                              defconfig and fragment are properly
                              applied<br>
                              &gt;&gt; to the configuration phase.<br>
                              &gt;&gt;<br>
                              &gt;&gt; I'm also seeing good results on
                              master, which means that I'm at a<br>
                              &gt;&gt; standstill to reproduce any
                              problems.<br>
                              &gt;&gt;<br>
                              &gt;&gt; Diego: can you confirm for me
                              what triggers you are seeing that shows<br>
                              &gt;&gt; the defconfig and fragment are
                              not used. I assume the config options<br>
                              &gt;&gt; are not present, but I just want
                              to be sure.<br>
                              &gt;<br>
                              &gt; For the full defconfig replacement
                              after doing a do_configure I've checked<br>
                              &gt; .config on ${S} and it did not
                              included my CONFIGS.<br>
                              &gt; For config fragment it got stuck on
                              do_patch task.<br>
                              &gt;<br>
                              &gt;<br>
                              &gt;<br>
                              &gt; Regards,<br>
                              &gt;<br>
                              &gt; --<br>
                              &gt; *dS<br>
                              &gt; Diego Sueiro<br>
                              &gt;<br>
                              &gt; /*long live rock 'n roll*/<br>
                              &gt;<br>
                            </div>
                          </div>
                          <div>&gt;
                            _______________________________________________<br>
                            &gt; yocto mailing list<br>
                            &gt; <a moz-do-not-send="true"
                              href="mailto:yocto@yoctoproject.org"
                              target="_blank">yocto@yoctoproject.org</a><br>
                            &gt; <a moz-do-not-send="true"
                              href="https://lists.yoctoproject.org/listinfo/yocto"
                              target="_blank">https://lists.yoctoproject.org/listinfo/yocto</a><br>
                            &gt;<br>
                            <br>
                          </div>
                          I'll jump in one more time...<br>
                          <br>
                          Have you tried putting defconfig and patch
                          under &lt;machine&gt; subdir?<br>
                          <br>
recipes-kernel/linux/linux-yocto-3.2/&lt;machine&gt;<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>

--------------050101050703010705080605--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Bruce.Ashfield@windriver.com>
Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id EA5D3E017E8
	for <yocto@yoctoproject.org>; Sun,  3 Nov 2013 19:14:30 -0800 (PST)
Received: from ALA-HCB.corp.ad.wrs.com (ala-hcb.corp.ad.wrs.com
	[147.11.189.41])
	by mail1.windriver.com (8.14.5/8.14.3) with ESMTP id rA43ERJ3013784
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
	Sun, 3 Nov 2013 19:14:27 -0800 (PST)
Received: from bruce-ashfields-macbook.local (128.224.21.6) by
	ALA-HCB.corp.ad.wrs.com (147.11.189.41) with Microsoft SMTP Server id
	14.2.347.0; Sun, 3 Nov 2013 19:14:26 -0800
Message-ID: <52771111.5000604@windriver.com>
Date: Sun, 3 Nov 2013 22:14:25 -0500
From: Bruce Ashfield <bruce.ashfield@windriver.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
	rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Diego Sueiro <diego.sueiro@gmail.com>, Andrea Adami
	<andrea.adami@gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
	<52686723.4080305@windriver.com>
	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>
	<526B18BC.5050302@alphalem.com>
	<CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gmail.com>
	<526ECFF3.4060207@windriver.com>
	<CAMCfZKFnYB3DKSejuZ3JT-uwo=rNekOT3bUcFvuAHdnJnqFONg@mail.gmail.com>
	<CAAQYJAuCDgpYKA9VPA35pYEq31HRhxN3gM1S6LRrNqcJbTFK0Q@mail.gmail.com>
	<CAMCfZKFPhz4odA9iMZ5aWzWtT1XR8JX_EHxJQLXyVuy+S7KLqg@mail.gmail.com>
	<CAMCfZKHaRRVcx5YG+7DJ10-4DE_n9titOG7+aB3R+4H8iZjGvw@mail.gmail.com>
In-Reply-To: <CAMCfZKHaRRVcx5YG+7DJ10-4DE_n9titOG7+aB3R+4H8iZjGvw@mail.gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Paul Eggleton <paul.eggleton@linux.intel.com>
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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Nov 2013 03:14:34 -0000
X-Groupsio-MsgNum: 16929
Content-Type: multipart/mixed; boundary="------------020107030701090901030801"

--------------020107030701090901030801
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.
>
> 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

FYI: I went silent on this, since I was running a few experiments in the
background. Mainly on scenario 2, but I can say that I see the same 
behaviour
with scenario #1 as you do. Whether or not I use the yocto kernel tooling,
or the core kernel processing, I see exactly the same defconfig used.

The issue you are seeing is distinct from the kernel processing, since
the defconfig isn't treated any differently than anything else on the
SRC_URI from the fetcher point of view ... and it is the fetcher which
is matching file://defconfig from the meta-beagleboard layer before the
one you have in meta-mine, since FILESEXTRAPATHS are searched after the
FILESPATH for the elements in the SRC_URI. But I'm not a fetcher expert,
that's my understanding and empirical evidence.

As a debug, I called src_patches() in patches.bbclass explicitly, and
it is obvious that the source of the defconfig is from meta-beagleboard.
Renaming the file in meta-beagleboard, allows the one in meta-mine to
be found, since the search continues.

So for this question, your issue is with the ordering of the elements
on the SRC_URI, and you can have your layer prioritized by making sure
it is in the search paths first.

This may or may not contradict the docs, and there are several threads
ongoing about SRC_URI ordering in the various branches .. so I'm simply
watching and waiting on this one.

>
>   * 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)
>

As for this. I debugged it over the weekend, and you wouldn't see this on
master, but the tools on the dylan branch aren't using the proper kern-tools
SRCREVS. As such, I backported a change from master, and switched the
kern-tools to use the dylan branch.

What you were seeing as a hang, was really just an extremely long run
of the patch processing, the 700+ patches in the beagleboard kernel
recipe were being detected multiple times, and expanding to 47K entries.

Which the patch I've attached here, I was able to patch and configure the
kernel with the same layers.  Note: the run still takes a long time, since
even applying 700 patches at a couple of seconds per patch .. takes a
good chunk of time.

I've added Paul Eggleton to the cc: list, since I'm not sure if dylan is
still being updated, but if it is, the patch I'm attaching should be
applied to fix the kern-tools situation in that branch.

Cheers,

Bruce

>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/
>
>
> 2013/10/29 Diego Sueiro <diego.sueiro@gmail.com
> <mailto:diego.sueiro@gmail.com>>
>
>     2013/10/29 Andrea Adami <andrea.adami@gmail.com
>     <mailto: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
>     <mailto:andrea.adami@gmail.com>>
>
>         On Tue, Oct 29, 2013 at 11:33 AM, Diego Sueiro
>         <diego.sueiro@gmail.com <mailto:diego.sueiro@gmail.com>> wrote:
>          >
>          > 2013/10/28 Bruce Ashfield <bruce.ashfield@windriver.com
>         <mailto: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 <mailto: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
>
>
>


--------------020107030701090901030801
Content-Type: application/mbox;
	name="0001-kern-tools-use-dylan-branch.patch"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="0001-kern-tools-use-dylan-branch.patch"

RnJvbSBkNGY0YTNlMzlmYTc1ZDY0ODM0Mzc3MGQ5NmMwZWU3YTBhODA5MDVkIE1vbiBTZXAgMTcg
MDA6MDA6MDAgMjAwMQpGcm9tOiBCcnVjZSBBc2hmaWVsZCA8YnJ1Y2UuYXNoZmllbGRAd2luZHJp
dmVyLmNvbT4KRGF0ZTogU3VuLCAzIE5vdiAyMDEzIDAwOjIwOjEwIC0wNDAwClN1YmplY3Q6IFtQ
QVRDSF0ga2Vybi10b29sczogdXNlIGR5bGFuIGJyYW5jaAoKVGhpcyBzd2l0Y2hlcyB0aGUga2Vy
bi10b29scyB0byB1c2UgdGhlIG1hdGNoZWQgZHlsYW4gYnJhbmNoIHRoYXQgaXMgbWFpbnRhaW5l
ZAp0byB3b3JrIGFnYWluc3QgdGhlIGR5bGFuIHJlbGVhc2Ugb2YgeW9jdG8vb2UtY29yZS4KCkFz
IHBhcnQgb2YgdGhpcyBzd2l0Y2gsIHdlIGFsc28gdXBkYXRlIHRoZSBTUkNSRVYgdG8gbWF0Y2gg
dGhlIGxhdGVzdCBmaXhlcyBmb3IKdGhlIGR5bGFuIGtlcm5lbC10b29scy4KClNpZ25lZC1vZmYt
Ynk6IEJydWNlIEFzaGZpZWxkIDxicnVjZS5hc2hmaWVsZEB3aW5kcml2ZXIuY29tPgotLS0KIG1l
dGEvcmVjaXBlcy1rZXJuZWwva2Vybi10b29scy9rZXJuLXRvb2xzLW5hdGl2ZV9naXQuYmIgfCA0
ICsrLS0KIDEgZmlsZSBjaGFuZ2VkLCAyIGluc2VydGlvbnMoKyksIDIgZGVsZXRpb25zKC0pCgpk
aWZmIC0tZ2l0IGEvbWV0YS9yZWNpcGVzLWtlcm5lbC9rZXJuLXRvb2xzL2tlcm4tdG9vbHMtbmF0
aXZlX2dpdC5iYiBiL21ldGEvcmVjaXBlcy1rZXJuZWwva2Vybi10b29scy9rZXJuLXRvb2xzLW5h
dGl2ZV9naXQuYmIKaW5kZXggYTg2ZGRhMy4uM2Y3MzFlYyAxMDA2NDQKLS0tIGEvbWV0YS9yZWNp
cGVzLWtlcm5lbC9rZXJuLXRvb2xzL2tlcm4tdG9vbHMtbmF0aXZlX2dpdC5iYgorKysgYi9tZXRh
L3JlY2lwZXMta2VybmVsL2tlcm4tdG9vbHMva2Vybi10b29scy1uYXRpdmVfZ2l0LmJiCkBAIC00
LDEzICs0LDEzIEBAIExJQ19GSUxFU19DSEtTVU0gPSAiZmlsZTovL2dpdC90b29scy9rZ2l0O2Jl
Z2lubGluZT01O2VuZGxpbmU9OTttZDU9ZDhkMWQ3MjlhNzBjCiAKIERFUEVORFMgPSAiZ2l0LW5h
dGl2ZSBndWlsdC1uYXRpdmUiCiAKLVNSQ1JFViA9ICIxYTNjNTk1MjZkNmFiZTk1NjYyODIwYjk0
OTNjOGE2MmRhYjUyZDc5IgorU1JDUkVWID0gIjI3MDBjNWQxYzIxNDc2NmYwMWU2OGJkZmEyNTA0
OWZhMWE1OTYwYmMiCiBQUiA9ICJyMTIiCiBQViA9ICIwLjErZ2l0JHtTUkNQVn0iCiAKIGluaGVy
aXQgbmF0aXZlCiAKLVNSQ19VUkkgPSAiZ2l0Oi8vZ2l0LnlvY3RvcHJvamVjdC5vcmcveW9jdG8t
a2VybmVsLXRvb2xzLmdpdDtwcm90b2NvbD1naXQiCitTUkNfVVJJID0gImdpdDovL2dpdC55b2N0
b3Byb2plY3Qub3JnL3lvY3RvLWtlcm5lbC10b29scy5naXQ7cHJvdG9jb2w9Z2l0O2JyYW5jaD1k
eWxhbiIKIFMgPSAiJHtXT1JLRElSfSIKIAogZG9fY29tcGlsZSgpIHsgCi0tIAoxLjguMS4yCgo=

--------------020107030701090901030801--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <diego.sueiro@gmail.com>
Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com
	[209.85.223.181])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id E13A8E0055D
	for <yocto@yoctoproject.org>; Thu, 28 Nov 2013 07:37:24 -0800 (PST)
Received: by mail-ie0-f181.google.com with SMTP id e14so14770842iej.12
	for <yocto@yoctoproject.org>; Thu, 28 Nov 2013 07:37:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=sNYxibbaZCQwiewUkAWKVrngCSuKFxiHNkPn1OHTH5Y=;
	b=ehwnJEC4t/FUZ5e1o+r1EOrZ6L57GX8W6rJKDtC1Ni4IJww0DTYQJrkUDYV2SUoapl
	Es730qx1wItTdWuwUBfeIa3KqY/jtcNtE9pWvA8QZgfVA+oeBe5DylAxhhglVhNnYCy8
	Cv8i1oN0EWN+OlBj1CtsdEHT1Eh4hZ1GNdfCqWxHJySGQ38tzTlOlxZ9Aa+HPoApOKrA
	mZjfILNSzQkK/bdi21PVcNlMUEmnXZJ0IS1YQgEbWuGoSh+QVo1Y2Ilp6IcLs2glPudJ
	g4FHgVuFn2xREkSPLLKaJR1JB7ezLI/1i7SGa01Sp83+5qlE1a/NeGJRJAr4aK2fazWj
	ow0w==
X-Received: by 10.43.178.135 with SMTP id ow7mr12759926icc.43.1385653043639;
	Thu, 28 Nov 2013 07:37:23 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.26.233 with HTTP; Thu, 28 Nov 2013 07:37:03 -0800 (PST)
In-Reply-To: <52771111.5000604@windriver.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<525FE3C9.3070003@windriver.com>
	<CAMCfZKGUYAcO5FtOKC9iP_XZjRxJ_Xq12ERN=BL_JHA7FJW51w@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
	<52686723.4080305@windriver.com>
	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>
	<526B18BC.5050302@alphalem.com>
	<CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gmail.com>
	<526ECFF3.4060207@windriver.com>
	<CAMCfZKFnYB3DKSejuZ3JT-uwo=rNekOT3bUcFvuAHdnJnqFONg@mail.gmail.com>
	<CAAQYJAuCDgpYKA9VPA35pYEq31HRhxN3gM1S6LRrNqcJbTFK0Q@mail.gmail.com>
	<CAMCfZKFPhz4odA9iMZ5aWzWtT1XR8JX_EHxJQLXyVuy+S7KLqg@mail.gmail.com>
	<CAMCfZKHaRRVcx5YG+7DJ10-4DE_n9titOG7+aB3R+4H8iZjGvw@mail.gmail.com>
	<52771111.5000604@windriver.com>
From: Diego Sueiro <diego.sueiro@gmail.com>
Date: Thu, 28 Nov 2013 13:37:03 -0200
Message-ID: <CAMCfZKEE7wSrpg_7Gq5ScYbwroNn_G+gpvjnZRG36A=xEJu7pg@mail.gmail.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Paul Eggleton <paul.eggleton@linux.intel.com>
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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2013 15:37:25 -0000
Content-Type: multipart/alternative; boundary=001a11c30bec72bf7204ec3e7d5b

--001a11c30bec72bf7204ec3e7d5b
Content-Type: text/plain; charset=ISO-8859-1

Bruce,

Any updates on this?

Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/


On Mon, Nov 4, 2013 at 1:14 AM, Bruce Ashfield <bruce.ashfield@windriver.com
> wrote:

> 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.
>>
>> 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
>>
>
> FYI: I went silent on this, since I was running a few experiments in the
> background. Mainly on scenario 2, but I can say that I see the same
> behaviour
> with scenario #1 as you do. Whether or not I use the yocto kernel tooling,
> or the core kernel processing, I see exactly the same defconfig used.
>
> The issue you are seeing is distinct from the kernel processing, since
> the defconfig isn't treated any differently than anything else on the
> SRC_URI from the fetcher point of view ... and it is the fetcher which
> is matching file://defconfig from the meta-beagleboard layer before the
> one you have in meta-mine, since FILESEXTRAPATHS are searched after the
> FILESPATH for the elements in the SRC_URI. But I'm not a fetcher expert,
> that's my understanding and empirical evidence.
>
> As a debug, I called src_patches() in patches.bbclass explicitly, and
> it is obvious that the source of the defconfig is from meta-beagleboard.
> Renaming the file in meta-beagleboard, allows the one in meta-mine to
> be found, since the search continues.
>
> So for this question, your issue is with the ordering of the elements
> on the SRC_URI, and you can have your layer prioritized by making sure
> it is in the search paths first.
>
> This may or may not contradict the docs, and there are several threads
> ongoing about SRC_URI ordering in the various branches .. so I'm simply
> watching and waiting on this one.
>
>
>>   * 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)
>>
>>
> As for this. I debugged it over the weekend, and you wouldn't see this on
> master, but the tools on the dylan branch aren't using the proper
> kern-tools
> SRCREVS. As such, I backported a change from master, and switched the
> kern-tools to use the dylan branch.
>
> What you were seeing as a hang, was really just an extremely long run
> of the patch processing, the 700+ patches in the beagleboard kernel
> recipe were being detected multiple times, and expanding to 47K entries.
>
> Which the patch I've attached here, I was able to patch and configure the
> kernel with the same layers.  Note: the run still takes a long time, since
> even applying 700 patches at a couple of seconds per patch .. takes a
> good chunk of time.
>
> I've added Paul Eggleton to the cc: list, since I'm not sure if dylan is
> still being updated, but if it is, the patch I'm attaching should be
> applied to fix the kern-tools situation in that branch.
>
> Cheers,
>
> Bruce
>
>
>>
>> Regards,
>>
>> --
>> *dS
>> Diego Sueiro
>>
>> /*long live rock 'n roll*/
>>
>>
>> 2013/10/29 Diego Sueiro <diego.sueiro@gmail.com
>> <mailto:diego.sueiro@gmail.com>>
>>
>>     2013/10/29 Andrea Adami <andrea.adami@gmail.com
>>     <mailto: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
>>     <mailto:andrea.adami@gmail.com>>
>>
>>
>>         On Tue, Oct 29, 2013 at 11:33 AM, Diego Sueiro
>>         <diego.sueiro@gmail.com <mailto:diego.sueiro@gmail.com>> wrote:
>>          >
>>          > 2013/10/28 Bruce Ashfield <bruce.ashfield@windriver.com
>>         <mailto: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 <mailto: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
>>
>>
>>
>>
>

--001a11c30bec72bf7204ec3e7d5b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Bruce,<div><br></div><div style>Any updates on this?</div>=
<div class=3D"gmail_extra"><br clear=3D"all"><div><div dir=3D"ltr"><div>Reg=
ards,</div><div><br></div>--<br>*dS<br>Diego Sueiro<br><br>/*long live rock=
 &#39;n roll*/<br>

</div></div>
<br><br><div class=3D"gmail_quote">On Mon, Nov 4, 2013 at 1:14 AM, Bruce As=
hfield <span dir=3D"ltr">&lt;<a href=3D"mailto:bruce.ashfield@windriver.com=
" target=3D"_blank">bruce.ashfield@windriver.com</a>&gt;</span> wrote:<br><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">

<div class=3D"im">On <a href=3D"tel:13-10-29%2011" value=3D"+13102911" targ=
et=3D"_blank">13-10-29 11</a>:31 AM, Diego Sueiro wrote:<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div><div class=3D"h5">
Bruce,<br>
<br>
I&#39;ve created new build setup with this configuration:<br>
<br>
=A0 =A0 BB_VERSION =A0 =A0 =A0 =A0=3D &quot;1.18.0&quot;<br>
=A0 =A0 BUILD_SYS =A0 =A0 =A0 =A0 =3D &quot;x86_64-linux&quot;<br>
=A0 =A0 NATIVELSBSTRING =A0 =3D &quot;Ubuntu-12.10&quot;<br>
=A0 =A0 TARGET_SYS =A0 =A0 =A0 =A0=3D &quot;arm-poky-linux-gnueabi&quot;<br=
>
=A0 =A0 MACHINE =A0 =A0 =A0 =A0 =A0 =3D &quot;beaglebone&quot;<br>
=A0 =A0 DISTRO =A0 =A0 =A0 =A0 =A0 =A0=3D &quot;poky&quot;<br>
=A0 =A0 DISTRO_VERSION =A0 =A0=3D &quot;1.4.2&quot;<br>
=A0 =A0 TUNE_FEATURES =A0 =A0 =3D &quot;armv7a vfp neon&quot;<br>
=A0 =A0 TARGET_FPU =A0 =A0 =A0 =A0=3D &quot;vfp-neon&quot;<br>
=A0 =A0 meta<br>
=A0 =A0 meta-yocto<br>
=A0 =A0 meta-yocto-bsp =A0 =A0=3D &quot;dylan:<u></u>4e399f08d596197859214f=
db3b0640<u></u>3b87bf8789&quot;<br>
=A0 =A0 meta-oe =A0 =A0 =A0 =A0 =A0 =3D &quot;dylan:<u></u>a108b2203a997634=
f87ac687e81712<u></u>badaf3c546&quot;<br>
=A0 =A0 common-bsp =A0 =A0 =A0 =A0=3D &quot;dylan:<u></u>7fdf9c670a10c5031a=
2d5555c15c45<u></u>e453de8c21&quot;<br>
=A0 =A0 meta-mine =A0 =A0 =A0 =A0 =3D &quot;dylan:<u></u>4e399f08d596197859=
214fdb3b0640<u></u>3b87bf8789&quot;<br>
<br>
common-bsp comes from meta-beagleboard.<br>
meta-oe needed to be added because of machine_kernel_pr.bbclass.<br>
<br>
bblayers.conf:<br>
<br>
=A0 =A0 LCONF_VERSION =3D &quot;6&quot;<br>
=A0 =A0 BBPATH =3D &quot;${TOPDIR}&quot;<br>
=A0 =A0 BBFILES ?=3D &quot;&quot;<br>
=A0 =A0 BBLAYERS ?=3D &quot; \<br>
=A0 =A0 =A0 =A0${TOPDIR}/meta \<br>
=A0 =A0 =A0 =A0${TOPDIR}/meta-yocto \<br>
=A0 =A0 =A0 =A0${TOPDIR}/meta-yocto-bsp \<br>
=A0 =A0 =A0 =A0${TOPDIR}/meta-openembedded/<u></u>meta-oe \<br>
=A0 =A0 =A0 =A0${TOPDIR}/meta-beagleboard/<u></u>common-bsp \<br>
=A0 =A0 =A0 =A0${TOPDIR}/meta-mine \<br>
=A0 =A0 =A0 =A0&quot;<br>
<br>
meta-mine:<br>
<br>
=A0 =A0 conf/layer.conf:<br>
<br>
=A0 =A0 =A0 =A0 BBPATH .=3D &quot;:${LAYERDIR}&quot;<br>
=A0 =A0 =A0 =A0 BBFILES +=3D &quot;${LAYERDIR}/recipes*/*/*.bb<br>
=A0 =A0 =A0 =A0 ${LAYERDIR}/recipes*/*/*.<u></u>bbappend&quot;<br>
=A0 =A0 =A0 =A0 BBFILE_COLLECTIONS +=3D &quot;my-layer&quot;<br>
=A0 =A0 =A0 =A0 BBFILE_PATTERN_my-layer :=3D &quot;^${LAYERDIR}/&quot;<br>
=A0 =A0 =A0 =A0 BBFILE_PRIORITY_my-layer =3D &quot;10&quot;<br>
<br>
=A0 =A0 recipes-kernel/linux/linux-<u></u>mainline_3.8.bbappend (scenario 1=
):<br>
<br>
=A0 =A0 =A0 =A0 FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/${PN}-3.8:&qu=
ot;<br>
=A0 =A0 =A0 =A0 COMPATIBLE_MACHINE_beaglebone =3D &quot;(beaglebone)&quot;<=
br>
=A0 =A0 =A0 =A0 SRC_URI +=3D &quot; file://defconfig \<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 &quot;<br>
<br>
=A0 =A0 recipes-kernel/linux/linux-<u></u>mainline-3.8/defconfig (scenario =
1):<br>
<br>
=A0 =A0 =A0 =A0 <a href=3D"http://pastebin.com/qd8B3C5K" target=3D"_blank">=
http://pastebin.com/qd8B3C5K</a><br>
<br>
<br>
=A0 =A0 recipes-kernel/linux/linux-<u></u>mainline_3.8.bbappend (scenario 2=
):<br>
<br>
=A0 =A0 =A0 =A0 FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/${PN}-3.8:&qu=
ot;<br>
=A0 =A0 =A0 =A0 inherit kernel<br>
=A0 =A0 =A0 =A0 require recipes-kernel/linux/linux-<u></u>yocto.inc<br>
=A0 =A0 =A0 =A0 COMPATIBLE_MACHINE_beaglebone =3D &quot;(beaglebone)&quot;<=
br>
=A0 =A0 =A0 =A0 SRC_URI +=3D &quot; file://config-addons.cfg \<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 &quot;<br>
<br>
=A0 =A0 recipes-kernel/linux/linux-<u></u>mainline-3.8/config-addons.cfg (s=
cenario 2):<br>
<br>
=A0 =A0 =A0 =A0 CONFIG_WATCHDOG_NOWAYOUT=3Dy<br>
<br>
=A0 =A0 =A0 =A0 CONFIG_NTFS_FS=3Dy<br>
=A0 =A0 =A0 =A0 CONFIG_NTFS_RW=3Dy<br>
<br>
<br>
<br>
Results:<br>
<br></div></div>
=A0 * Scenario 1: Full defconfig replacement<div class=3D"im"><br>
<br>
=A0 =A0 ${WORKDIR}/defconfig comes from meta-beagleboard instead of meta-mi=
ne<br>
<br>
=A0 =A0 ${S}/.config comes from meta-beagleboard instead of meta-mine<br>
</div></blockquote>
<br>
FYI: I went silent on this, since I was running a few experiments in the<br=
>
background. Mainly on scenario 2, but I can say that I see the same behavio=
ur<br>
with scenario #1 as you do. Whether or not I use the yocto kernel tooling,<=
br>
or the core kernel processing, I see exactly the same defconfig used.<br>
<br>
The issue you are seeing is distinct from the kernel processing, since<br>
the defconfig isn&#39;t treated any differently than anything else on the<b=
r>
SRC_URI from the fetcher point of view ... and it is the fetcher which<br>
is matching file://defconfig from the meta-beagleboard layer before the<br>
one you have in meta-mine, since FILESEXTRAPATHS are searched after the<br>
FILESPATH for the elements in the SRC_URI. But I&#39;m not a fetcher expert=
,<br>
that&#39;s my understanding and empirical evidence.<br>
<br>
As a debug, I called src_patches() in patches.bbclass explicitly, and<br>
it is obvious that the source of the defconfig is from meta-beagleboard.<br=
>
Renaming the file in meta-beagleboard, allows the one in meta-mine to<br>
be found, since the search continues.<br>
<br>
So for this question, your issue is with the ordering of the elements<br>
on the SRC_URI, and you can have your layer prioritized by making sure<br>
it is in the search paths first.<br>
<br>
This may or may not contradict the docs, and there are several threads<br>
ongoing about SRC_URI ordering in the various branches .. so I&#39;m simply=
<br>
watching and waiting on this one.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
=A0 * Scenario 2: Config fragments<div class=3D"im"><br>
<br>
=A0 =A0 &quot;bitbake linux-mainline&quot; got stuck on do_patch<br>
<br>
=A0 =A0 log.do_patch:<br>
<br>
=A0 =A0 =A0 =A0 DEBUG: Executing shell function do_patch<br>
<br>
=A0 =A0 =A0 =A0 WARNING: no meta data branch found ...<br>
<br>
=A0 =A0 =A0 =A0 Switched to branch &#39;linux-3.8.y&#39;<br>
<br>
=A0 =A0 =A0 =A0 [INFO] validating against known patches =A0(beaglebone-stan=
dard-meta)<br>
<br>
</div></blockquote>
<br>
As for this. I debugged it over the weekend, and you wouldn&#39;t see this =
on<br>
master, but the tools on the dylan branch aren&#39;t using the proper kern-=
tools<br>
SRCREVS. As such, I backported a change from master, and switched the<br>
kern-tools to use the dylan branch.<br>
<br>
What you were seeing as a hang, was really just an extremely long run<br>
of the patch processing, the 700+ patches in the beagleboard kernel<br>
recipe were being detected multiple times, and expanding to 47K entries.<br=
>
<br>
Which the patch I&#39;ve attached here, I was able to patch and configure t=
he<br>
kernel with the same layers. =A0Note: the run still takes a long time, sinc=
e<br>
even applying 700 patches at a couple of seconds per patch .. takes a<br>
good chunk of time.<br>
<br>
I&#39;ve added Paul Eggleton to the cc: list, since I&#39;m not sure if dyl=
an is<br>
still being updated, but if it is, the patch I&#39;m attaching should be<br=
>
applied to fix the kern-tools situation in that branch.<br>
<br>
Cheers,<br>
<br>
Bruce<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">
<br>
<br>
Regards,<br>
<br>
--<br>
*dS<br>
Diego Sueiro<br>
<br>
/*long live rock &#39;n roll*/<br>
<br>
<br>
2013/10/29 Diego Sueiro &lt;<a href=3D"mailto:diego.sueiro@gmail.com" targe=
t=3D"_blank">diego.sueiro@gmail.com</a><br></div>
&lt;mailto:<a href=3D"mailto:diego.sueiro@gmail.com" target=3D"_blank">dieg=
o.sueiro@gmail.com</a><u></u>&gt;&gt;<br>
<br>
=A0 =A0 2013/10/29 Andrea Adami &lt;<a href=3D"mailto:andrea.adami@gmail.co=
m" target=3D"_blank">andrea.adami@gmail.com</a><br>
=A0 =A0 &lt;mailto:<a href=3D"mailto:andrea.adami@gmail.com" target=3D"_bla=
nk">andrea.adami@gmail.com</a><u></u>&gt;&gt;<div class=3D"im"><br>
<br>
=A0 =A0 =A0 =A0 I&#39;ll jump in one more time...<br>
<br>
=A0 =A0 =A0 =A0 Have you tried putting defconfig and patch under &lt;machin=
e&gt; subdir?<br>
<br>
=A0 =A0 =A0 =A0 recipes-kernel/linux/linux-<u></u>yocto-3.2/&lt;machine&gt;=
<br>
=A0 =A0 =A0 =A0 defconfig<br>
=A0 =A0 =A0 =A0 my-own.patch<br>
<br>
=A0 =A0 =A0 =A0 I&#39;ve recently added two similar entries for 3.10 and it=
 works.<br>
=A0 =A0 =A0 =A0 Afaik it was impossible to put a common patch under<br>
=A0 =A0 =A0 =A0 /linux-yocto-.3.2<br>
=A0 =A0 =A0 =A0 at the time.<br>
<br>
<br>
=A0 =A0 Andrea,<br>
<br>
=A0 =A0 I did it before and not worked.<br>
=A0 =A0 I&#39;ll do it again just to make sure.<br>
<br>
<br></div><div class=3D"im">
=A0 =A0 Regards,<br>
<br>
=A0 =A0 --<br>
=A0 =A0 *dS<br>
=A0 =A0 Diego Sueiro<br>
<br>
=A0 =A0 /*long live rock &#39;n roll*/<br>
<br>
<br>
=A0 =A0 2013/10/29 Andrea Adami &lt;<a href=3D"mailto:andrea.adami@gmail.co=
m" target=3D"_blank">andrea.adami@gmail.com</a><br></div>
=A0 =A0 &lt;mailto:<a href=3D"mailto:andrea.adami@gmail.com" target=3D"_bla=
nk">andrea.adami@gmail.com</a><u></u>&gt;&gt;<div class=3D"im"><br>
<br>
=A0 =A0 =A0 =A0 On Tue, Oct 29, 2013 at 11:33 AM, Diego Sueiro<br></div><di=
v class=3D"im">
=A0 =A0 =A0 =A0 &lt;<a href=3D"mailto:diego.sueiro@gmail.com" target=3D"_bl=
ank">diego.sueiro@gmail.com</a> &lt;mailto:<a href=3D"mailto:diego.sueiro@g=
mail.com" target=3D"_blank">diego.sueiro@gmail.com</a><u></u>&gt;&gt; wrote=
:<br>
=A0 =A0 =A0 =A0 =A0&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt; 2013/10/28 Bruce Ashfield &lt;<a href=3D"mailto:bru=
ce.ashfield@windriver.com" target=3D"_blank">bruce.ashfield@windriver.com</=
a><br></div>
=A0 =A0 =A0 =A0 &lt;mailto:<a href=3D"mailto:bruce.ashfield@windriver.com" =
target=3D"_blank">bruce.ashfield@<u></u>windriver.com</a>&gt;&gt;<div><div =
class=3D"h5"><br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; I&#39;m using dylan for my yocto checkout (not =
oe-core<br>
=A0 =A0 =A0 =A0 standalone, since<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; this is a yocto list/question),<br>
=A0 =A0 =A0 =A0 =A0&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt; I thought that opemenbedded-core and poky were shar=
ing the<br>
=A0 =A0 =A0 =A0 same core<br>
=A0 =A0 =A0 =A0 =A0&gt; components, classes and functions.<br>
=A0 =A0 =A0 =A0 =A0&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; My build shows:<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; meta<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; meta-yocto<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; meta-yocto-bsp =A0 =A0=3D<br>
=A0 =A0 =A0 =A0 &quot;dylan:<u></u>3dc4505f0e744177ae4ddff1e1ce8b<u></u>31b=
95dfaa6&quot;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; meta-ti =A0 =A0 =A0 =A0 =A0 =3D<br>
=A0 =A0 =A0 =A0 &quot;master:<u></u>c14c386946e1ea341faeea292580e3<u></u>7d=
538d645d&quot;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; meta-alphalem =A0 =A0 =3D<br>
=A0 =A0 =A0 =A0 &quot;master:<u></u>a5c0e8ff51297a4090cd47d669b4fc<u></u>9c=
94696908&quot;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; meta-alphalem-bsp =3D<br>
=A0 =A0 =A0 =A0 &quot;master:<u></u>56086e4dc618e975c9a46491793041<u></u>f0=
d18e47a2&quot;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; Mike indicated that he was using dylan for meta=
-ti, but that<br>
=A0 =A0 =A0 =A0 doesn&#39;t<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; make a difference either, since for our purpose=
d. It&#39;s<br>
=A0 =A0 =A0 =A0 kernel.bbclass<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; and the yocto kernel processing that matters.<b=
r>
=A0 =A0 =A0 =A0 =A0&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt; I&#39;ll build a setup with yocto (dylan), meta-bea=
gleboard<br>
=A0 =A0 =A0 =A0 (dylan) and<br>
=A0 =A0 =A0 =A0 =A0&gt; meta-mine to check if I can reproduce the issues.<b=
r>
=A0 =A0 =A0 =A0 =A0&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; In meta-alphalem-bsp, I have linux-mainline_3.2=
.bbappend,<br>
=A0 =A0 =A0 =A0 with the<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; following content:<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; &gt; cat linux-mainline_3.2.bbappend<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; FILESEXTRAPATHS_prepend :=3D &quot;${THISDIR}/$=
{PN}-3.2:&quot;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; inherit kernel<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; require recipes-kernel/linux/linux-<u></u>yocto=
.inc<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; COMPATIBLE_MACHINE =3D &quot;(beagleboard)&quot=
;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; SRC_URI_append =3D &quot; file://defconfig&quot=
;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; SRC_URI_append =3D &quot; file://my_frag.cfg&qu=
ot;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; And I added a fragment which has:<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; &gt; cat my_frag.cfg<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; CONFIG_WATCHDOG_NOWAYOUT=3Dy<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; CONFIG_NTFS_FS=3Dy<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; CONFIG_NTFS_RW=3Dy<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; When both are applied to the kernel build, we s=
hould see<br>
=A0 =A0 =A0 =A0 CONFIG_NTFS_FS<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; transition from =3Dm to =3Dy:<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; &gt; grep CONFIG_NTFS_FS *<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; defconfig:CONFIG_NTFS_FS=3Dm<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; my_frag.cfg:CONFIG_NTFS_FS=3Dy<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; After invoking linux-mainline&#39;s configure t=
ask, I see the<br>
=A0 =A0 =A0 =A0 following:<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; &gt; grep CONFIG_NTFS_FS linux-beagleboard-stan=
dard-<u></u>build/.config<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; CONFIG_NTFS_FS=3Dy<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; And other elements of the defconfig and fragmen=
t are<br>
=A0 =A0 =A0 =A0 properly applied<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; to the configuration phase.<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; I&#39;m also seeing good results on master, whi=
ch means that I&#39;m<br>
=A0 =A0 =A0 =A0 at a<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; standstill to reproduce any problems.<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; Diego: can you confirm for me what triggers you=
 are seeing<br>
=A0 =A0 =A0 =A0 that shows<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; the defconfig and fragment are not used. I assu=
me the config<br>
=A0 =A0 =A0 =A0 options<br>
=A0 =A0 =A0 =A0 =A0&gt;&gt; are not present, but I just want to be sure.<br=
>
=A0 =A0 =A0 =A0 =A0&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt; For the full defconfig replacement after doing a do=
_configure<br>
=A0 =A0 =A0 =A0 I&#39;ve checked<br>
=A0 =A0 =A0 =A0 =A0&gt; .config on ${S} and it did not included my CONFIGS.=
<br>
=A0 =A0 =A0 =A0 =A0&gt; For config fragment it got stuck on do_patch task.<=
br>
=A0 =A0 =A0 =A0 =A0&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt; Regards,<br>
=A0 =A0 =A0 =A0 =A0&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt; --<br>
=A0 =A0 =A0 =A0 =A0&gt; *dS<br>
=A0 =A0 =A0 =A0 =A0&gt; Diego Sueiro<br>
=A0 =A0 =A0 =A0 =A0&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt; /*long live rock &#39;n roll*/<br>
=A0 =A0 =A0 =A0 =A0&gt;<br>
=A0 =A0 =A0 =A0 =A0&gt; ______________________________<u></u>______________=
___<br>
=A0 =A0 =A0 =A0 =A0&gt; yocto mailing list<br></div></div>
=A0 =A0 =A0 =A0 =A0&gt; <a href=3D"mailto:yocto@yoctoproject.org" target=3D=
"_blank">yocto@yoctoproject.org</a> &lt;mailto:<a href=3D"mailto:yocto@yoct=
oproject.org" target=3D"_blank">yocto@yoctoproject.org</a><u></u>&gt;<div c=
lass=3D"im"><br>


=A0 =A0 =A0 =A0 =A0&gt; <a href=3D"https://lists.yoctoproject.org/listinfo/=
yocto" target=3D"_blank">https://lists.yoctoproject.<u></u>org/listinfo/yoc=
to</a><br>
=A0 =A0 =A0 =A0 =A0&gt;<br>
<br>
=A0 =A0 =A0 =A0 I&#39;ll jump in one more time...<br>
<br>
=A0 =A0 =A0 =A0 Have you tried putting defconfig and patch under &lt;machin=
e&gt; subdir?<br>
<br>
=A0 =A0 =A0 =A0 recipes-kernel/linux/linux-<u></u>yocto-3.2/&lt;machine&gt;=
<br>
=A0 =A0 =A0 =A0 defconfig<br>
=A0 =A0 =A0 =A0 my-own.patch<br>
<br>
=A0 =A0 =A0 =A0 I&#39;ve recently added two similar entries for 3.10 and it=
 works.<br>
=A0 =A0 =A0 =A0 Afaik it was impossible to put a common patch under<br>
=A0 =A0 =A0 =A0 /linux-yocto-.3.2<br>
=A0 =A0 =A0 =A0 at the time.<br>
<br>
=A0 =A0 =A0 =A0 Regards<br>
<br>
=A0 =A0 =A0 =A0 Andrea<br>
<br>
<br>
<br>
</div></blockquote>
<br>
</blockquote></div><br></div></div>

--001a11c30bec72bf7204ec3e7d5b--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Bruce.Ashfield@windriver.com>
Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id C0AABE0055D
	for <yocto@yoctoproject.org>; Thu, 28 Nov 2013 07:49:28 -0800 (PST)
Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com
	[147.11.189.40])
	by mail1.windriver.com (8.14.5/8.14.5) with ESMTP id rASFnPer028713
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
	Thu, 28 Nov 2013 07:49:25 -0800 (PST)
Received: from server.local (128.224.22.47) by ALA-HCA.corp.ad.wrs.com
	(147.11.189.40) with Microsoft SMTP Server id 14.2.347.0;
	Thu, 28 Nov 2013 07:49:25 -0800
Message-ID: <52976604.4010908@windriver.com>
Date: Thu, 28 Nov 2013 10:49:24 -0500
From: Bruce Ashfield <bruce.ashfield@windriver.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
	rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Diego Sueiro <diego.sueiro@gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
	<52686723.4080305@windriver.com>
	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>
	<526B18BC.5050302@alphalem.com>
	<CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gmail.com>
	<526ECFF3.4060207@windriver.com>
	<CAMCfZKFnYB3DKSejuZ3JT-uwo=rNekOT3bUcFvuAHdnJnqFONg@mail.gmail.com>
	<CAAQYJAuCDgpYKA9VPA35pYEq31HRhxN3gM1S6LRrNqcJbTFK0Q@mail.gmail.com>
	<CAMCfZKFPhz4odA9iMZ5aWzWtT1XR8JX_EHxJQLXyVuy+S7KLqg@mail.gmail.com>
	<CAMCfZKHaRRVcx5YG+7DJ10-4DE_n9titOG7+aB3R+4H8iZjGvw@mail.gmail.com>
	<52771111.5000604@windriver.com>
	<CAMCfZKEE7wSrpg_7Gq5ScYbwroNn_G+gpvjnZRG36A=xEJu7pg@mail.gmail.com>
In-Reply-To: <CAMCfZKEE7wSrpg_7Gq5ScYbwroNn_G+gpvjnZRG36A=xEJu7pg@mail.gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Paul Eggleton <paul.eggleton@linux.intel.com>
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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2013 15:49:30 -0000
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

On 11/28/2013, 10:37 AM, Diego Sueiro wrote:
> Bruce,
>
> Any updates on this?

Which part ? :) The defconfig "selection" (prioritization) was
explained by instrumenting the SRC_URI processing order, and it
was behaving as expected.

And the patch I attached for the kern-tools to use the dedicated
release branch for dylan fixed the other patching issue you were
seeing.

Cheers,

Bruce

>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/
>
>
> On Mon, Nov 4, 2013 at 1:14 AM, Bruce Ashfield
> <bruce.ashfield@windriver.com <mailto:bruce.ashfield@windriver.com>> wrote:
>
>     On 13-10-29 11 <tel:13-10-29%2011>: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:__4e399f08d596197859214fdb3b0640__3b87bf8789"
>              meta-oe           =
>         "dylan:__a108b2203a997634f87ac687e81712__badaf3c546"
>              common-bsp        =
>         "dylan:__7fdf9c670a10c5031a2d5555c15c45__e453de8c21"
>              meta-mine         =
>         "dylan:__4e399f08d596197859214fdb3b0640__3b87bf8789"
>
>         common-bsp comes from meta-beagleboard.
>         meta-oe needed to be added because of machine_kernel_pr.bbclass.
>
>         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
>
>
>     FYI: I went silent on this, since I was running a few experiments in the
>     background. Mainly on scenario 2, but I can say that I see the same
>     behaviour
>     with scenario #1 as you do. Whether or not I use the yocto kernel
>     tooling,
>     or the core kernel processing, I see exactly the same defconfig used.
>
>     The issue you are seeing is distinct from the kernel processing, since
>     the defconfig isn't treated any differently than anything else on the
>     SRC_URI from the fetcher point of view ... and it is the fetcher which
>     is matching file://defconfig from the meta-beagleboard layer before the
>     one you have in meta-mine, since FILESEXTRAPATHS are searched after the
>     FILESPATH for the elements in the SRC_URI. But I'm not a fetcher expert,
>     that's my understanding and empirical evidence.
>
>     As a debug, I called src_patches() in patches.bbclass explicitly, and
>     it is obvious that the source of the defconfig is from meta-beagleboard.
>     Renaming the file in meta-beagleboard, allows the one in meta-mine to
>     be found, since the search continues.
>
>     So for this question, your issue is with the ordering of the elements
>     on the SRC_URI, and you can have your layer prioritized by making sure
>     it is in the search paths first.
>
>     This may or may not contradict the docs, and there are several threads
>     ongoing about SRC_URI ordering in the various branches .. so I'm simply
>     watching and waiting on this one.
>
>
>            * 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)
>
>
>     As for this. I debugged it over the weekend, and you wouldn't see
>     this on
>     master, but the tools on the dylan branch aren't using the proper
>     kern-tools
>     SRCREVS. As such, I backported a change from master, and switched the
>     kern-tools to use the dylan branch.
>
>     What you were seeing as a hang, was really just an extremely long run
>     of the patch processing, the 700+ patches in the beagleboard kernel
>     recipe were being detected multiple times, and expanding to 47K entries.
>
>     Which the patch I've attached here, I was able to patch and
>     configure the
>     kernel with the same layers.  Note: the run still takes a long time,
>     since
>     even applying 700 patches at a couple of seconds per patch .. takes a
>     good chunk of time.
>
>     I've added Paul Eggleton to the cc: list, since I'm not sure if dylan is
>     still being updated, but if it is, the patch I'm attaching should be
>     applied to fix the kern-tools situation in that branch.
>
>     Cheers,
>
>     Bruce
>
>
>
>         Regards,
>
>         --
>         *dS
>         Diego Sueiro
>
>         /*long live rock 'n roll*/
>
>
>         2013/10/29 Diego Sueiro <diego.sueiro@gmail.com
>         <mailto:diego.sueiro@gmail.com>
>         <mailto:diego.sueiro@gmail.com <mailto:diego.sueiro@gmail.com>__>>
>
>              2013/10/29 Andrea Adami <andrea.adami@gmail.com
>         <mailto:andrea.adami@gmail.com>
>              <mailto:andrea.adami@gmail.com
>         <mailto: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
>         <mailto:andrea.adami@gmail.com>
>              <mailto:andrea.adami@gmail.com
>         <mailto:andrea.adami@gmail.com>__>>
>
>
>                  On Tue, Oct 29, 2013 at 11:33 AM, Diego Sueiro
>                  <diego.sueiro@gmail.com <mailto:diego.sueiro@gmail.com>
>         <mailto:diego.sueiro@gmail.com
>         <mailto:diego.sueiro@gmail.com>__>> wrote:
>                   >
>                   > 2013/10/28 Bruce Ashfield
>         <bruce.ashfield@windriver.com <mailto:bruce.ashfield@windriver.com>
>                  <mailto:bruce.ashfield@__windriver.com
>         <mailto: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:__3dc4505f0e744177ae4ddff1e1ce8b__31b95dfaa6"
>                   >> meta-ti           =
>                  "master:__c14c386946e1ea341faeea292580e3__7d538d645d"
>                   >> meta-alphalem     =
>                  "master:__a5c0e8ff51297a4090cd47d669b4fc__9c94696908"
>                   >> meta-alphalem-bsp =
>                  "master:__56086e4dc618e975c9a46491793041__f0d18e47a2"
>                   >>
>                   >> 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
>         <mailto:yocto@yoctoproject.org> <mailto:yocto@yoctoproject.org
>         <mailto:yocto@yoctoproject.org>__>
>
>                   > https://lists.yoctoproject.__org/listinfo/yocto
>         <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
>
>
>
>
>



From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <diego.sueiro@gmail.com>
Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com
	[209.85.223.176])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 898B1E0055D
	for <yocto@yoctoproject.org>; Thu, 28 Nov 2013 08:26:59 -0800 (PST)
Received: by mail-ie0-f176.google.com with SMTP id at1so14013802iec.7
	for <yocto@yoctoproject.org>; Thu, 28 Nov 2013 08:26:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=dAjw4vc9vCg+7B5xeYaX8sWnCgCN0+Q2zLhm0t0fuHw=;
	b=xwHwKgrEOGlbFBoJrt24Y2nVu78Lh5sB+cQy9IZ0BPwHm25VSbzJX1LTfC4rL5s0yn
	Vfa5unoc83+KL3tq3ZWO5y0mHBdUB2PoEcHdcufmQlzsjSDxesSGVUWPaGCZ9STGSaL/
	oKX4v4iVOi/lQ7suEoNV3qBqg4bewVG63u5Su91I7fGvDZQzZWOHAdDEQO6UskST1tkn
	e+yPMhFstEj5RLJJDu7Vm4qtPYFTnSObManmLPi3498MOPzjp4NKzduVbjgdjjKO2cIH
	wZTWE8rrxCggGA3hzshkuFgN8KwTHh9Xag1yGG3UsQ/wvMHR0O2wZ7PyC1ZSKj03E6dx
	TeMA==
X-Received: by 10.50.119.4 with SMTP id kq4mr2765602igb.40.1385656017757; Thu,
	28 Nov 2013 08:26:57 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.26.233 with HTTP; Thu, 28 Nov 2013 08:26:37 -0800 (PST)
In-Reply-To: <52976604.4010908@windriver.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<5260BDA6.4020807@windriver.com>
	<CAMCfZKFf3iJCyjMgGQ=y6ng6Kh3_MeEMymgZTE=bTnLpBGN9Mg@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
	<52686723.4080305@windriver.com>
	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>
	<526B18BC.5050302@alphalem.com>
	<CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gmail.com>
	<526ECFF3.4060207@windriver.com>
	<CAMCfZKFnYB3DKSejuZ3JT-uwo=rNekOT3bUcFvuAHdnJnqFONg@mail.gmail.com>
	<CAAQYJAuCDgpYKA9VPA35pYEq31HRhxN3gM1S6LRrNqcJbTFK0Q@mail.gmail.com>
	<CAMCfZKFPhz4odA9iMZ5aWzWtT1XR8JX_EHxJQLXyVuy+S7KLqg@mail.gmail.com>
	<CAMCfZKHaRRVcx5YG+7DJ10-4DE_n9titOG7+aB3R+4H8iZjGvw@mail.gmail.com>
	<52771111.5000604@windriver.com>
	<CAMCfZKEE7wSrpg_7Gq5ScYbwroNn_G+gpvjnZRG36A=xEJu7pg@mail.gmail.com>
	<52976604.4010908@windriver.com>
From: Diego Sueiro <diego.sueiro@gmail.com>
Date: Thu, 28 Nov 2013 14:26:37 -0200
Message-ID: <CAMCfZKHzjj6n2pxe6H_QETQRSPbQ=tGWim54NkakiHxyL5feZA@mail.gmail.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Paul Eggleton <paul.eggleton@linux.intel.com>
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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2013 16:27:00 -0000
Content-Type: multipart/alternative; boundary=089e013c6e4ab82e4c04ec3f2ef1

--089e013c6e4ab82e4c04ec3f2ef1
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Nov 28, 2013 at 1:49 PM, Bruce Ashfield <
bruce.ashfield@windriver.com> wrote:

> And the patch I attached for the kern-tools to use the dedicated
> release branch for dylan fixed the other patching issue you were
> seeing.
>

This patch was applied in some repo?

Regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/

--089e013c6e4ab82e4c04ec3f2ef1
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 28, 2013 at 1:49 PM, Bruce Ashfield <span dir="ltr">&lt;<a href="mailto:bruce.ashfield@windriver.com" target="_blank">bruce.ashfield@windriver.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":3fm" style="overflow:hidden">And the patch I attached for the kern-tools to use the dedicated<br>
release branch for dylan fixed the other patching issue you were<br>
seeing.<br></div></blockquote></div><br>This patch was applied in some repo?<br><br clear="all"><div><div dir="ltr"><div>Regards,</div><div><br></div>--<br>*dS<br>Diego Sueiro<br><br>/*long live rock &#39;n roll*/<br></div>

</div>
</div></div>

--089e013c6e4ab82e4c04ec3f2ef1--

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Bruce.Ashfield@windriver.com>
Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 1F701E0055D
	for <yocto@yoctoproject.org>; Thu, 28 Nov 2013 08:28:45 -0800 (PST)
Received: from ALA-HCB.corp.ad.wrs.com (ala-hcb.corp.ad.wrs.com
	[147.11.189.41])
	by mail1.windriver.com (8.14.5/8.14.5) with ESMTP id rASGSgoq029781
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
	Thu, 28 Nov 2013 08:28:42 -0800 (PST)
Received: from server.local (128.224.22.47) by ALA-HCB.corp.ad.wrs.com
	(147.11.189.41) with Microsoft SMTP Server id 14.2.347.0;
	Thu, 28 Nov 2013 08:28:42 -0800
Message-ID: <52976F39.6050003@windriver.com>
Date: Thu, 28 Nov 2013 11:28:41 -0500
From: Bruce Ashfield <bruce.ashfield@windriver.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
	rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Diego Sueiro <diego.sueiro@gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<5261974C.7010202@windriver.com> <5266A665.8030303@alphalem.com>
	<52686723.4080305@windriver.com>
	<CAMCfZKG1A_c-oy6KLZuctX4Nmca7f1ryBKRaR-sqFVVqNwuSrA@mail.gmail.com>
	<CADkTA4OWiOmDYDskpe6=uCX+XEE8R0C2aUxjCph+tAjdX=Ae2Q@mail.gmail.com>
	<526B18BC.5050302@alphalem.com>
	<CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gmail.com>
	<526ECFF3.4060207@windriver.com>
	<CAMCfZKFnYB3DKSejuZ3JT-uwo=rNekOT3bUcFvuAHdnJnqFONg@mail.gmail.com>
	<CAAQYJAuCDgpYKA9VPA35pYEq31HRhxN3gM1S6LRrNqcJbTFK0Q@mail.gmail.com>
	<CAMCfZKFPhz4odA9iMZ5aWzWtT1XR8JX_EHxJQLXyVuy+S7KLqg@mail.gmail.com>
	<CAMCfZKHaRRVcx5YG+7DJ10-4DE_n9titOG7+aB3R+4H8iZjGvw@mail.gmail.com>
	<52771111.5000604@windriver.com>
	<CAMCfZKEE7wSrpg_7Gq5ScYbwroNn_G+gpvjnZRG36A=xEJu7pg@mail.gmail.com>
	<52976604.4010908@windriver.com>
	<CAMCfZKHzjj6n2pxe6H_QETQRSPbQ=tGWim54NkakiHxyL5feZA@mail.gmail.com>
In-Reply-To: <CAMCfZKHzjj6n2pxe6H_QETQRSPbQ=tGWim54NkakiHxyL5feZA@mail.gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Paul Eggleton <paul.eggleton@linux.intel.com>
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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2013 16:28:48 -0000
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

On 11/28/2013, 11:26 AM, Diego Sueiro wrote:
>
> On Thu, Nov 28, 2013 at 1:49 PM, Bruce Ashfield
> <bruce.ashfield@windriver.com <mailto:bruce.ashfield@windriver.com>> wrote:
>
>     And the patch I attached for the kern-tools to use the dedicated
>     release branch for dylan fixed the other patching issue you were
>     seeing.
>
>
> This patch was applied in some repo?

That's why I cc'd Paul on the submission, but I suspect it got lost, since
I never did get a comment .. and we are all pretty busily juggling multiple
things at once.

Paul: can you find the patch in the history of this thread ? If not I
can resend it directly.

Bruce

>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/



From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <paul.eggleton@linux.intel.com>
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id DA5E8E0055D
	for <yocto@yoctoproject.org>; Thu, 28 Nov 2013 08:41:10 -0800 (PST)
Received: from orsmga001.jf.intel.com ([10.7.209.18])
	by orsmga102.jf.intel.com with ESMTP; 28 Nov 2013 08:37:31 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.93,791,1378882800"; d="scan'208";a="416572280"
Received: from unknown (HELO helios.localnet) ([10.252.122.17])
	by orsmga001.jf.intel.com with ESMTP; 28 Nov 2013 08:41:09 -0800
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>,
	Diego Sueiro <diego.sueiro@gmail.com>
Date: Thu, 28 Nov 2013 16:41:08 +0000
Message-ID: <4684047.2lGL8cktov@helios>
Organization: Intel Corporation
User-Agent: KMail/4.10.5 (Linux/3.8.0-31-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <52976F39.6050003@windriver.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CAMCfZKHzjj6n2pxe6H_QETQRSPbQ=tGWim54NkakiHxyL5feZA@mail.gmail.com>
	<52976F39.6050003@windriver.com>
MIME-Version: 1.0
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2013 16:41:11 -0000
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

Hi Bruce / Diego,

On Thursday 28 November 2013 11:28:41 Bruce Ashfield wrote:
> On 11/28/2013, 11:26 AM, Diego Sueiro wrote:
> > On Thu, Nov 28, 2013 at 1:49 PM, Bruce Ashfield
> > 
> > <bruce.ashfield@windriver.com <mailto:bruce.ashfield@windriver.com>> wrote:
> >     And the patch I attached for the kern-tools to use the dedicated
> >     release branch for dylan fixed the other patching issue you were
> >     seeing.
> > 
> > This patch was applied in some repo?
> 
> That's why I cc'd Paul on the submission, but I suspect it got lost, since
> I never did get a comment .. and we are all pretty busily juggling multiple
> things at once.
> 
> Paul: can you find the patch in the history of this thread ? If not I
> can resend it directly.

I've still got it in my queue. I'll try to process and send that out tomorrow, 
sorry for the delay.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Bruce.Ashfield@windriver.com>
Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13])
	by yocto-www.yoctoproject.org (Postfix) with ESMTP id 5FFF7E0055D
	for <yocto@yoctoproject.org>; Thu, 28 Nov 2013 09:26:24 -0800 (PST)
Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com
	[147.11.189.40])
	by mail1.windriver.com (8.14.5/8.14.5) with ESMTP id rASHQHfD001138
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
	Thu, 28 Nov 2013 09:26:18 -0800 (PST)
Received: from server.local (128.224.22.47) by ALA-HCA.corp.ad.wrs.com
	(147.11.189.40) with Microsoft SMTP Server id 14.2.347.0;
	Thu, 28 Nov 2013 09:26:17 -0800
Message-ID: <52977CB8.3070304@windriver.com>
Date: Thu, 28 Nov 2013 12:26:16 -0500
From: Bruce Ashfield <bruce.ashfield@windriver.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
	rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Paul Eggleton <paul.eggleton@linux.intel.com>, Diego Sueiro
	<diego.sueiro@gmail.com>
References: <CAMCfZKFBvSiRSMk5wrEpSEiNNiZeHJw18fbHgHzepo__U=UWNA@mail.gmail.com>
	<CAMCfZKHzjj6n2pxe6H_QETQRSPbQ=tGWim54NkakiHxyL5feZA@mail.gmail.com>
	<52976F39.6050003@windriver.com> <4684047.2lGL8cktov@helios>
In-Reply-To: <4684047.2lGL8cktov@helios>
Cc: "yocto@yoctoproject.org" <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 <yocto.yoctoproject.org>
List-Unsubscribe: <https://lists.yoctoproject.org/options/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=unsubscribe>
List-Archive: <http://lists.yoctoproject.org/pipermail/yocto>
List-Post: <mailto:yocto@yoctoproject.org>
List-Help: <mailto:yocto-request@yoctoproject.org?subject=help>
List-Subscribe: <https://lists.yoctoproject.org/listinfo/yocto>,
	<mailto:yocto-request@yoctoproject.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2013 17:26:25 -0000
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

On 11/28/2013, 11:41 AM, Paul Eggleton wrote:
> Hi Bruce / Diego,
>
> On Thursday 28 November 2013 11:28:41 Bruce Ashfield wrote:
>> On 11/28/2013, 11:26 AM, Diego Sueiro wrote:
>>> On Thu, Nov 28, 2013 at 1:49 PM, Bruce Ashfield
>>>
>>> <bruce.ashfield@windriver.com <mailto:bruce.ashfield@windriver.com>> wrote:
>>>      And the patch I attached for the kern-tools to use the dedicated
>>>      release branch for dylan fixed the other patching issue you were
>>>      seeing.
>>>
>>> This patch was applied in some repo?
>>
>> That's why I cc'd Paul on the submission, but I suspect it got lost, since
>> I never did get a comment .. and we are all pretty busily juggling multiple
>> things at once.
>>
>> Paul: can you find the patch in the history of this thread ? If not I
>> can resend it directly.
>
> I've still got it in my queue. I'll try to process and send that out tomorrow,
> sorry for the delay.

No worries. I of all people understand a merge backlog (as I look at my 
pending
BSP merge list :)

Bruce

>
> Cheers,
> Paul
>