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:
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
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
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
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:
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
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:
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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:
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
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
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
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
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
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
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
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
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
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
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
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 \
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
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
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.
39 matches
Mail list logo
