Simon,
Please send me your kernel bb recipes as there is probably an issue in
them.
Regards,
Nick
On 2015-01-08 03:58 PM, Simon Bolek wrote:
NIck, thank you. what do you mean by that? I followed the instructions from
here:
How about adding in local.conf the following line? Does it work for you?
USE_DEVFS = 0
Regards,
Chen Qi
On 01/08/2015 05:59 AM, Simon Bolek wrote:
Hello folks!
I have the following problem/question.
1) I built a standard .hddimg core-image-sato genericx86 on ubuntu 14.10
2) Afterwards, this
Packages lttng-viewer and lttng-control were removed quite some time
ago, replace references in example with current lttng-tools.
Signed-off-by: Robert P. J. Day rpj...@crashcourse.ca
---
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml
On Wednesday 07 January 2015 16:36:37 Khem Raj wrote:
On Jan 7, 2015, at 1:25 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
I was informed on irc yesterday that bug reports are hard and that
debugging via irc is easier. I think I need to remind people why good
bug
Dear List,
I am using Yocto dylan release, and I have two external kernel modules
on two different Yocto recipes. One is exporting symbols that the
other one will use. When I load the modules to the target with
modprobe I see the message unresolved symbols. In order to solve the
issue, I copied
Thank you Nick. I will try that, but this is not the point. I am trying to
figure out why
*bitbake core-image-sato *
does not create /dev/ram nodes, although linux-yocto has them defiined in
.config file.
I also created:
mylayer/recipes-kernel/linux/linux_yocto_3.4.bbapend
* Robert P. J. Day rpj...@crashcourse.ca [150105 18:09]:
On Mon, 5 Jan 2015, Rifenbark, Scott M wrote:
If anyone can locate some scripts or something that actually does
require meta- to be prepended please let me know. That changes
how we describe this.
as an admittedly simple
On Thu, 8 Jan 2015, Anders Darander wrote:
* Robert P. J. Day rpj...@crashcourse.ca [150105 18:09]:
On Mon, 5 Jan 2015, Rifenbark, Scott M wrote:
If anyone can locate some scripts or something that actually does
require meta- to be prepended please let me know. That changes
how we
Hi,
This is v2 as Paul's comments, please take them if any.
Cheers,
Zumeng
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
From: Lai Jiangshan la...@cn.fujitsu.com
commit 9625ab1727743f6a164df26b7b1eeeced7380b42 upstream
worker_idr is highly bound to managers and is always/only accessed in manager
lock context. So we don't need pool-lock for it.
Signed-off-by: Lai Jiangshan la...@cn.fujitsu.com
Signed-off-by: Tejun
From: Lai Jiangshan la...@cn.fujitsu.com
commit 60f5a4bcf852b5dec698b08cd34efc302ea72f2b upstream
worker destruction includes these parts of code:
adjust pool's stats
remove the worker from idle list
detach the worker from the pool
kthread_stop() to wait for the
From: Lai Jiangshan la...@cn.fujitsu.com
commit 7cda9aae0596d871a8d7a6888d7b447c60e5ab30 upstream
We no longer iterate workers via worker_idr and worker_idr is used
only for allocating/freeing ID, so we can convert it to worker_ida.
By using ida_simple_get/remove(), worker_ida doesn't require
Message: 6
Date: Thu, 8 Jan 2015 08:31:58 -0500 (EST)
From:
Robert P. J. Day rpj...@crashcourse.ca
To: Anders Darander
and...@chargestorm.se
Cc: Yocto discussion list
yocto@yoctoproject.org,
peterengcomau...@adam.com.au
peterengcomau...@adam.com.au
Subject: Re: [yocto] is it not a
On Jan 8, 2015, at 8:59 AM, Bruce Ashfield bruce.ashfi...@gmail.com wrote:
Assigning and scoping the actual work doesn't scale based on email threads
(as someone who has been thrashing to keep information straight, and reproduce
issues .. I feel this pain greatly).
if you are a talking
On Thu, Jan 8, 2015 at 12:29 PM, Khem Raj raj.k...@gmail.com wrote:
On Jan 8, 2015, at 8:59 AM, Bruce Ashfield bruce.ashfi...@gmail.com wrote:
Assigning and scoping the actual work doesn't scale based on email threads
(as someone who has been thrashing to keep information straight, and
Simon,
Why are you not linking your kernels to the core-image-sato build.
This seems to be the issue.
Regards Nick
On 2015-01-08 05:59 AM, Simon Bolek wrote:
Thank you Nick. I will try that, but this is not the point. I am trying to
figure out why
*bitbake core-image-sato *
does not create
On Thu, 8 Jan 2015, micke.p...@telldus.se wrote:
Message: 6
Date: Thu, 8 Jan 2015 08:31:58 -0500 (EST)
From: Robert P. J. Day rpj...@crashcourse.ca
To: Anders Darander and...@chargestorm.se
Cc: Yocto discussion list yocto@yoctoproject.org,
peterengcomau...@adam.com.au
Pulled into master. Thanks,
-b
On 24 December 2014 at 14:06, Damian, Alexandru
alexandru.dam...@intel.com wrote:
Sure, thanks !
Happy holidays !
On 24 Dec 2014 00:46, Flanagan, Elizabeth elizabeth.flana...@intel.com
wrote:
On 23 December 2014 at 07:20, Damian, Alexandru
On Jan 8, 2015, at 2:01 AM, Paul Eggleton paul.eggle...@linux.intel.com
wrote:
On Wednesday 07 January 2015 16:36:37 Khem Raj wrote:
On Jan 7, 2015, at 1:25 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
I was informed on irc yesterday that bug reports are hard and that
On Thu, Jan 8, 2015 at 11:40 AM, Khem Raj raj.k...@gmail.com wrote:
On Jan 8, 2015, at 2:01 AM, Paul Eggleton paul.eggle...@linux.intel.com
wrote:
On Wednesday 07 January 2015 16:36:37 Khem Raj wrote:
On Jan 7, 2015, at 1:25 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
I
NIck, thank you. what do you mean by that? I followed the instructions from
here:
http://www.yoctoproject.org/docs/1.7/kernel-dev/kernel-dev.html#changing-the-configuration
is there something there I might be missing? Where is the part, 'linking
your kernels to the core-image-sato build' that you
21 matches
Mail list logo
