Re: [yocto] Custom defconfig is not used
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.ashfi...@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:7fdf9c670a10c5031a2dc15c45e453de8c21
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
Re: [yocto] Custom defconfig is not used
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.ashfi...@windriver.com mailto:bruce.ashfi...@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:__7fdf9c670a10c5031a2dc15c45__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
Re: [yocto] Custom defconfig is not used
On Thu, Nov 28, 2013 at 1:49 PM, Bruce Ashfield bruce.ashfi...@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*/ ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
On 11/28/2013, 11:26 AM, Diego Sueiro wrote: On Thu, Nov 28, 2013 at 1:49 PM, Bruce Ashfield bruce.ashfi...@windriver.com mailto:bruce.ashfi...@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*/ ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
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.ashfi...@windriver.com mailto:bruce.ashfi...@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 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
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:7fdf9c670a10c5031a2dc15c45e453de8c21
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,
Re: [yocto] Custom defconfig is not used
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
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
On Wed, Oct 30, 2013 at 3:57 AM, Jukka Rissanen
jukka.rissa...@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
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
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:7fdf9c670a10c5031a2dc15c45e453de8c21
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.sue...@gmail.com
mailto:diego.sue...@gmail.com
2013/10/29 Andrea Adami andrea.ad...@gmail.com
mailto:andrea.ad...@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.ad...@gmail.com
mailto:andrea.ad...@gmail.com
On Tue, Oct 29, 2013 at 11:33 AM, Diego Sueiro
diego.sue...@gmail.com mailto:diego.sue...@gmail.com wrote:
2013/10/28 Bruce Ashfield bruce.ashfi...@windriver.com
mailto:bruce.ashfi...@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
Re: [yocto] Custom defconfig is not used
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:7fdf9c670a10c5031a2dc15c45e453de8c21
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.sue...@gmail.com
mailto:diego.sue...@gmail.com
2013/10/29 Andrea Adami andrea.ad...@gmail.com
mailto:andrea.ad...@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.ad...@gmail.com
mailto:andrea.ad...@gmail.com
On Tue, Oct 29, 2013 at 11:33 AM, Diego Sueiro
diego.sue...@gmail.com mailto:diego.sue...@gmail.com wrote:
2013/10/28 Bruce Ashfield bruce.ashfi...@windriver.com
mailto:bruce.ashfi...@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
Re: [yocto] Custom defconfig is not used
2013/10/30 Bruce Ashfield bruce.ashfi...@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*/ ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
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:7fdf9c670a10c5031a2dc15c45e453de8c21
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.sue...@gmail.com
mailto:diego.sue...@gmail.com
2013/10/29 Andrea Adami andrea.ad...@gmail.com
mailto:andrea.ad...@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.ad...@gmail.com
mailto:andrea.ad...@gmail.com
On Tue, Oct 29, 2013 at 11:33 AM, Diego Sueiro
diego.sue...@gmail.com mailto:diego.sue...@gmail.com wrote:
2013/10/28 Bruce Ashfield bruce.ashfi...@windriver.com
mailto:bruce.ashfi...@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
Re: [yocto] Custom defconfig is not used
2013/10/28 Bruce Ashfield bruce.ashfi...@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
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
On Tue, Oct 29, 2013 at 11:33 AM, Diego Sueiro diego.sue...@gmail.com wrote:
2013/10/28 Bruce Ashfield bruce.ashfi...@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
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
2013/10/29 Andrea Adami andrea.ad...@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.ad...@gmail.com
On Tue, Oct 29, 2013 at 11:33 AM, Diego Sueiro diego.sue...@gmail.com
wrote:
2013/10/28 Bruce Ashfield bruce.ashfi...@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
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
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 mikele...@alphalem.com
mailto:mikele...@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.sue...@gmail.com mailto:diego.sue...@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.ashfi...@windriver.com
mailto:bruce.ashfi...@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.ashfi...@windriver.com
mailto:bruce.ashfi...@windriver.com
Re: [yocto] Custom defconfig is not used
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 mikele...@alphalem.com
mailto:mikele...@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.sue...@gmail.com mailto:diego.sue...@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.ashfi...@windriver.com
mailto:bruce.ashfi...@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
Re: [yocto] Custom defconfig is not used
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 mikele...@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.sue...@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.htmlhttp://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.ashfi...@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.ashfi...@windriver.com
mailto:bruce.ashfield@**windriver.combruce.ashfi...@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.githttps://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/yoctohttps://lists.yoctoproject.org/listinfo/yocto
__**_
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.**org/listinfo/yoctohttps://lists.yoctoproject.org/listinfo/yocto
__**_
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.**org/listinfo/yoctohttps://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
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 mikele...@alphalem.com
mailto:mikele...@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.sue...@gmail.com mailto:diego.sue...@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.ashfi...@windriver.com
mailto:bruce.ashfi...@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.ashfi...@windriver.com
mailto:bruce.ashfi...@windriver.com
mailto:bruce.ashfield@__windriver.com
mailto:bruce.ashfi...@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 \
Re: [yocto] Custom defconfig is not used
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.ashfi...@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.ashfi...@windriver.com
mailto:bruce.ashfield@**windriver.com bruce.ashfi...@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.githttps://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/yoctohttps://lists.yoctoproject.org/listinfo/yocto
__**_
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.**org/listinfo/yoctohttps://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
On Fri, Oct 25, 2013 at 7:43 AM, Diego Sueiro diego.sue...@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.ashfi...@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.ashfi...@windriver.com
mailto:bruce.ashfi...@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
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
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.sue...@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.ashfi...@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.ashfi...@windriver.com
mailto:bruce.ashfi...@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
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
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.ashfi...@windriver.com
mailto:bruce.ashfi...@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
Re: [yocto] Custom defconfig is not used
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.ashfi...@windriver.com
mailto:bruce.ashfi...@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
Re: [yocto] Custom defconfig is not used
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.ashfi...@windriver.com
mailto:bruce.ashfi...@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
Re: [yocto] Custom defconfig is not used
2013/10/18 Bruce Ashfield bruce.ashfi...@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*/
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
On 13-10-18 05:17 AM, Diego Sueiro wrote:
2013/10/18 Bruce Ashfield bruce.ashfi...@windriver.com
mailto:bruce.ashfi...@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
Re: [yocto] Custom defconfig is not used
2013/10/17 Bruce Ashfield bruce.ashfi...@gmail.com
On Wed, Oct 16, 2013 at 2:19 PM, Diego Sueiro diego.sue...@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*/
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
On 13-10-17 06:39 AM, Diego Sueiro wrote:
2013/10/17 Bruce Ashfield bruce.ashfi...@gmail.com
mailto:bruce.ashfi...@gmail.com
On Wed, Oct 16, 2013 at 2:19 PM, Diego Sueiro
diego.sue...@gmail.com mailto:diego.sue...@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
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
2013/10/17 Bruce Ashfield bruce.ashfi...@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*/ ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
On 13-10-17 09:15 AM, Diego Sueiro wrote: 2013/10/17 Bruce Ashfield bruce.ashfi...@windriver.com mailto:bruce.ashfi...@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
Re: [yocto] Custom defconfig is not used
On Thu, Oct 17, 2013 at 3:19 PM, Bruce Ashfield bruce.ashfi...@windriver.com wrote: On 13-10-17 09:15 AM, Diego Sueiro wrote: 2013/10/17 Bruce Ashfield bruce.ashfi...@windriver.com mailto:bruce.ashfi...@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 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
2013/10/17 Bruce Ashfield bruce.ashfi...@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*/
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
On 13-10-17 11:47 AM, Diego Sueiro wrote:
2013/10/17 Bruce Ashfield bruce.ashfi...@windriver.com
mailto:bruce.ashfi...@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*/
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
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:
.
├── files
│ ├── mine.patch
│ └── defconfig
└── linux-mainline_3.8.bbappend
And my linux-mainline_3.8.bbappend recipe:
FILESEXTRAPATHS_prepend := ${THISDIR}/files:
SRC_URI += 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/recipes-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.ad...@gmail.com
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
rstr...@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.sue...@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
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Custom defconfig is not used
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
Re: [yocto] Custom defconfig is not used
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.sue...@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
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
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.sue...@gmail.comwrote:
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
Re: [yocto] Custom defconfig is not used
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
rstr...@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.sue...@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
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
