On 2016-07-21 08:58 AM, Bruce Ashfield wrote:
On 2016-07-21 02:35 AM, Jacob Kroon wrote:
On Thu, Jul 21, 2016 at 5:22 AM, Bruce Ashfield
wrote:
On 2016-07-20 4:19 PM, Jacob Kroon wrote:
Hi,
I'm trying to get the SDK to be able to run the kernel's "make
menuconfig" ta
On 2016-07-21 10:24 AM, Jacob Kroon wrote:
On Thu, Jul 21, 2016 at 3:06 PM, Bruce Ashfield
wrote:
On 2016-07-21 08:58 AM, Bruce Ashfield wrote:
On 2016-07-21 02:35 AM, Jacob Kroon wrote:
On Thu, Jul 21, 2016 at 5:22 AM, Bruce Ashfield
wrote:
On 2016-07-20 4:19 PM, Jacob Kroon wrote
On 2016-07-24 6:09 PM, Chris Tapp wrote:
I’m using the meta-intel “valley-island” BSP under “krogoth” and think I may
have run into https://bugzilla.kernel.org/show_bug.cgi?id=109051.
I’m using a J1900 (listed as affected) and the system locks up totally (running
a graphics-based application)
On Sun, Jul 24, 2016 at 2:42 PM, Chris Sykes <
ch...@newforest-technology.co.uk> wrote:
> Hi,
>
> At the end of last week I hit a known kernel memory leak in the
> linux-yocto 4.1 branch, as delivered in 2.1 / krogoth. It rather quickly
> results in an OOM kernel panic on my platform (x86, 1G RAM
On 2016-07-25 2:47 AM, Chris Tapp wrote:
Hi Bruce,
On 25 Jul 2016, at 03:40, Bruce Ashfield wrote:
On 2016-07-24 6:09 PM, Chris Tapp wrote:
I’m using the meta-intel “valley-island” BSP under “krogoth” and think I may
have run into https://bugzilla.kernel.org/show_bug.cgi?id=109051.
I’m
On 2016-07-26 05:15 AM, Jacob Kroon wrote:
Hi,
I've added kernel-devsrc to TOOLCHAIN_TARGET_TASK for the SDK.
After installing the SDK, /usr/src/kernel/ contains a
.kernel-meta/ directory of size ~18MB. After some rebuilds, and new SDK
generation/installation, that directory has grown to 512MB.
On 2016-07-26 02:32 AM, Mircea Gliga wrote:
Hello
I have my own layer and I am trying to configure the kernel using
partial configs.
I'm trying to enable netfilter support into the kernel - not as modules,
so I set the CONFIG to "y"
I've created a bbappend file in my layer, here:
recipes-ker
On 2016-07-28 12:00 AM, Zhenhua Luo wrote:
Hi,
I want to understand the kernel version selection criteria of Yocto
release, can somebody please help to comment on it? I recall that Yocto
uses the LTSI kernel, may I know if this is still the case?
I was about to describe the process .. but the
On Mon, Aug 1, 2016 at 7:32 AM, Simon Fels wrote:
> Hey everyone,
>
> I've worked on a new layer recently which brings snaps to any
> Yocto/OpenEmbedded based system.
>
> If you have never heard about snaps yet you will find most details at
> http://snapcraft.io/ but generally snaps are a new pac
Wrong mailing list (it should be meta-virtualizat...@yoctoproject.org), but
I can
pick up this change from here
No need to resend.
Bruce
On Thu, Aug 4, 2016 at 5:38 AM, wrote:
> From: Kai Kang
>
> Upgrade libvirt from 1.3.2 to 1.3.5.
>
> * update checksums and remove PR
> * remove trailing w
On Thu, Aug 4, 2016 at 11:52 AM, Kumar, Anil K
wrote:
>
>
> Anil K Kumar, PhD
> Principal Engineer
> Lead System Architect
> Makers & Innovators Group (MIG) / New Technology Group (NTG)
>
A clean resend would have been better, since this history comes through
somewhat mangled
with a forward like
On Sun, Aug 7, 2016 at 10:33 PM, wrote:
> From: Kai Kang
>
> When build for qemuarm, it fails to do compile_ptest_base.
>
>
Wrong mailing list (use meta-virtualizat...@yoctoproject.org).
But I've grabbed this and merged it anyway.
Bruce
> Kai Kang (1):
> libvirt: fix build error for arm
>
Still going to the wrong list use: meta-virtualizat...@yoctoproject.org.
On 2016-08-15 11:21 PM, kai.k...@windriver.com wrote:
From: Kai Kang
Backport patch to fix CVE-2016-5008 from:
https://libvirt.org/git/?p=libvirt.git;a=commit;h=f32441c
I typically prefer uprevs to backports for these
On 2016-08-17 6:08 PM, Paul Eggleton wrote:
On Tue, 16 Aug 2016 11:18:53 Bruce Ashfield wrote:
Still going to the wrong list use: meta-virtualizat...@yoctoproject.org.
FYI I can recommend the following to make this easy in future (it's how I deal
with the issue):
On Mon, Aug 29, 2016 at 5:19 AM, Ioan-Adrian Ratiu
wrote:
> merge_configs.sh calls make on the generated kernel config from
> the defconfig + fragments to fill in any missing symbols. make
> can fail and this can lead to nasty errors further on in the
> build like generating an unbootable kernel
On 2016-08-29 08:07 AM, Bruce Ashfield wrote:
On Mon, Aug 29, 2016 at 5:19 AM, Ioan-Adrian Ratiu mailto:adrian.ra...@ni.com>> wrote:
merge_configs.sh calls make on the generated kernel config from
the defconfig + fragments to fill in any missing symbols. make
can fail and th
On 2016-08-29 07:34 AM, Mircea Gliga wrote:
Hi
I'm using krogoth and trying to create a qemu arm machine with the
latest stable kernel 4.7.2.
I created a recipe,recipes-kernel/linux/linux-stable_4.7.bb, in my layer
with the following contents:
---
inherit kernel
require recipes-kernel/linux/lin
On 2016-08-29 09:22 AM, Ioan-Adrian Ratiu wrote:
On Mon, 29 Aug 2016, Bruce Ashfield wrote:
On 2016-08-29 08:07 AM, Bruce Ashfield wrote:
On Mon, Aug 29, 2016 at 5:19 AM, Ioan-Adrian Ratiu mailto:adrian.ra...@ni.com>> wrote:
merge_configs.sh calls make on the generated kernel
Latest Stable Kernel, any
suggestions on how to accomplish this ? It looks like the patch is not
enough for kernel 4.7.2.
I'm finishing up 4.8 today, but without doing a boot test, I can't say
for sure. I'll see if I can cycle in some korg 4.7.x testing tomorrow to
see if I can get a
On 2016-08-31 6:23 PM, Paul Eggleton wrote:
Hi Daniel,
On Tue, 30 Aug 2016 17:18:44 Daniel. wrote:
While writing software we're used to delivery packages, libraries and
stacks. There are out there a lot of continuos integration solutions
to automaticaly build and test these kinds of software. B
e 4.8 kernel, but I *think*
the coast is clear on that front (for the moment).
I can try and spin up a korg based 4.7.x build and see how it goes.
Bruce
Thanks
Mircea
On 08/30/2016 06:09 PM, Bruce Ashfield wrote:
I'm finishing up 4.8 today, but without doing a boot test, I can't say
On 2016-09-02 09:58 AM, Bruce Ashfield wrote:
On 2016-09-02 03:51 AM, Mircea Gliga wrote:
Hi Bruce,
Do you have any new input in regards with qemuarm booting with kernel
4.7.2 LTS ?
Have you managed to test this ?
I wander if this can be reproduce elsewhere and what's the solution
for it
The issue is that x86 defaults to 64bit, and this is a 32 bit build. We had
to force disable
it, to get the kernel to build 32bit.
The commit is here (on git://git.yoctoproject.org/yocto-kernel-cache
yocto-4.4 branch):
commit ff423148afe0b7e48ea8a8c0758391f9b4790912
Author: Bruce Ashfield
Date
On 2016-09-05 6:06 AM, Mircea Gliga wrote:
Thanks Bruce for your help!
It works now, with the defconfig from 4.8.
Great news!
Bruce
Have a nice day !
Mircea
On 09/02/2016 06:26 PM, Bruce Ashfield wrote:
On 2016-09-02 09:58 AM, Bruce Ashfield wrote:
On 2016-09-02 03:51 AM, Mircea Gliga
On 2016-09-06 2:17 PM, Clark, Mark A wrote:
Did a complete clone / checkout of krogoth this morning. Same
results. Can’t get a core-image-rt build of the latest poky.
I'll fire off a build for this on Wednesday. As I mentioned, I've
fixed this in other branches, and this is very likely the s
On 2016-09-06 8:42 PM, Bruce Ashfield wrote:
On 2016-09-06 2:17 PM, Clark, Mark A wrote:
Did a complete clone / checkout of krogoth this morning. Same
results. Can’t get a core-image-rt build of the latest poky.
I'll fire off a build for this on Wednesday. As I mentioned, I've
to finish:
Summary: 1 task failed:
/home/yocto/poky-contrib-1a167ae1d023bfb27eee741a9ee6765f9ea732b7/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb,
do_package_qa
Summary: There was 1 WARNING message shown.
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
-Orig
On 2016-09-09 2:33 PM, Clark, Mark A wrote:
All, I am still running into issues on building the RT image. I was
able to configure poky/jethro to create the core-image-rt. That being
said the kernel boot would hang at switching clock source “Switching to
clocksource tsc”. I was attempting to
From: Kevin Hao
Boot test for all these boards.
Signed-off-by: Kevin Hao
Signed-off-by: Bruce Ashfield
---
meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux
From: Kevin Hao
Boot test for all these boards.
Signed-off-by: Kevin Hao
Signed-off-by: Bruce Ashfield
---
meta-yocto-bsp/conf/machine/beaglebone.conf | 2 +-
meta-yocto-bsp/conf/machine/edgerouter.conf | 2 +-
meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf
From: Kevin Hao
Boot test for all these boards.
Signed-off-by: Kevin Hao
Signed-off-by: Bruce Ashfield
---
meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux
Hi all,
As a follow on to the pull request to oe-core, this is an update for the
hardware reference BSPs.
I tweaked the commits from Kevin Hao to have slightly newer SRCREVs, but
they are otherwise unchanged.
With this we shouldn't have mismatches in the PV, and will be building and
booting the
On 2016-09-22 03:42 AM, kai.k...@windriver.com wrote:
From: Kai Kang
When do split_and_strip_files, it may calls debugedit to deal elf files.
For ptest sub-package, it fails to run debugedit with .o files. So remove
the .o files which are redundant to run ptest cases.
Wrong mailing list (stil
On 10-11-08 03:32 PM, Kamble, Nitin A wrote:
Saul/RP,
This is a pull request for upgrading most of the devel/toolchain recipes.
This one is still missing the perl upgrade, and some gnome libs related python
modules.
I have done basic build testing of these recipes. And would like to see i
The force revisions is largely cosmetic, but it is used
by my upcoming kernel dev layer and I think it is more in
the spirit of other variables that are set from local
configurations.
The following changes since commit e417aa98e4b4170f4b4aaf805cc8ea20f8593604:
Bruce Ashfield (1):
wrs
It is useful to override revision checking from a layer or other
recipe. In order to show the global nature of the variable rename
it KERNEL_REVISION_CHECKING and make it a weak assignment.
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-wrs_git.bb |6 +++---
1 files
kernel does not produce one.
Signed-off-by: Bruce Ashfield
---
meta/classes/kernel.bbclass |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 4c79a98..bb76285 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta
On 10-11-08 7:41 PM, Kamble, Nitin A wrote:
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Out of curiosity. What's the logic/requirement behind this
change ? Since we don't have a 'supported' 2.6.36 kernel, using
these would be a m
On 10-11-09 6:31 PM, Richard Purdie wrote:
On Tue, 2010-11-09 at 09:18 -0600, Mark Hatle wrote:
On 11/9/10 12:12 AM, Bruce Ashfield wrote:
On 10-11-08 7:41 PM, Kamble, Nitin A wrote:
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Out of curiosity. What's the logic/requir
On 10-11-10 01:46 AM, Kumar Gala wrote:
Why does the meta/conf/machine/mpc8315e-rdb.conf list TARGET_FPU as SPE. This
isn't correct for an MPC8313 SoC.
It isn't used at the moment, so we can safely
ignore this.
It was a hold over from when I initially created
the BSP, and I've since changed
On 10-11-10 06:41 AM, João Henrique Freitas wrote:
Hi,
I am novice yocto user.
My target is create a BSP to my hardware+application. Is Yocto a
suitable project to do it?
I want to create two layers:
bsp-myhardware: linux kernel, firmware, specific hardware configuration
bsp-myapplication: li
On 10-11-10 08:38 AM, Bruce Ashfield wrote:
On 10-11-10 01:46 AM, Kumar Gala wrote:
Why does the meta/conf/machine/mpc8315e-rdb.conf list TARGET_FPU as
SPE. This isn't correct for an MPC8313 SoC.
It isn't used at the moment, so we can safely
ignore this.
It was a hold over f
On 10-11-10 09:11 AM, Kumar Gala wrote:
On Nov 10, 2010, at 7:58 AM, Bruce Ashfield wrote:
On 10-11-10 08:38 AM, Bruce Ashfield wrote:
On 10-11-10 01:46 AM, Kumar Gala wrote:
Why does the meta/conf/machine/mpc8315e-rdb.conf list TARGET_FPU as
SPE. This isn't correct for an MPC8313 SoC.
On 10-11-10 10:03 AM, Kumar Gala wrote:
On Nov 10, 2010, at 8:23 AM, Bruce Ashfield wrote:
On 10-11-10 09:11 AM, Kumar Gala wrote:
On Nov 10, 2010, at 7:58 AM, Bruce Ashfield wrote:
On 10-11-10 08:38 AM, Bruce Ashfield wrote:
On 10-11-10 01:46 AM, Kumar Gala wrote:
Why does the meta
On 10-11-11 7:15 PM, Saul Wold wrote:
Distro / User Space Folks:
Attached is a spread sheet that shows the recipes we plan to update for
the 1.0 release. This list is based on the reorganization that will be
coming into master soon and shows that there are 231 recipes that need
updating and ano
able
to build and test a 'qemumips-variant' quickly.
Cheers,
Bruce
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/kernel
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Thanks,
Bruce Ashfield
---
Bruce Ashfield (2):
linux-wrs: impl
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-wrs_git.bb | 40 ++-
1 files changed, 32 insertions(+), 8 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-wrs_git.bb
b/meta/recipes-kernel/linux/linux-wrs_git.bb
index 1f2b11e..209648b 10
Updating the kern-tools SRCREV to pickup changes required for
BSP bootstrapping:
commit 9722d8decacd2b750f079b3fde7918810700f80e
Author: Bruce Ashfield
Date: Thu Nov 11 01:28:33 2010 -0500
createme: improve BSP bootstrapping
To streamline BSP bootstrapping, createme now actually
On 10-11-12 5:29 PM, Zhang, Jessica wrote:
Here's another thread about sysprof, my question is should we support both
oprofile and sysprof or we should be using sysprof which seems a better
tool...
Both. There's still no one tracer to rule them all (*cough*
perf *cough*), and until there is som
On 10-11-12 5:25 PM, Tom Zanussi wrote:
Hi,
For the 1.0 Yocto release, we'd like to have as complete a set of
tracing and profiling tools as possible, enough so that most users will
be satisfied with what's available, but not so many as to produce a
maintenance burden.
The current set is pretty
well.
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/kernel-rename
Browse:
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-rename
Thanks,
Bruce Ashfield
---
Bruce Ashfield (3):
linux-wrs: rename to linux-yocto
linux-yocto: update board configurations
linux-y
Now that linuy-wrs has been renamed linux-yocto, we need
to rename and update an board configurations and append
files.
Signed-off-by: Bruce Ashfield
---
meta-emenlow/conf/machine/emenlow.conf |2 +-
...x-wrs_git.bbappend => linux-yocto_git.bbappend} |0
meta/conf/mach
The existing preferred yocto kernel wasn't named appropriately
and needs to be updated.
In keeping the changes small and isolated, this commit simply
renames the recipe and some internal variables. Future commits
will refactor the code into more usable blocks.
Signed-off-by: Bruce Ash
Now that linux-wrs has been renamed linux-yocto, we need to
update the SRCREVs to have the new name.
Signed-off-by: Bruce Ashfield
---
.../conf/distro/include/poky-default-revisions.inc | 24 ++--
1 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/meta/conf
On Mon, Nov 15, 2010 at 4:09 PM, Darren Hart wrote:
> On 11/15/2010 08:56 AM, Bruce Ashfield wrote:
>>
>> This is the first of several staged changes to update the
>> kernel support for the 1.0 release.
>>
>> This series is step 1:
>>
>> - rename the
On Mon, Nov 15, 2010 at 4:09 PM, Darren Hart wrote:
> On 11/15/2010 08:56 AM, Bruce Ashfield wrote:
>>
>> This is the first of several staged changes to update the
>> kernel support for the 1.0 release.
>>
>> This series is step 1:
>>
>> - rename the
On 10-11-17 8:29 PM, Darren Hart wrote:
On 11/17/2010 03:32 PM, Saul Wold wrote:
Folks,
After reviewing the emails from the first attempt and review bugzilla,
there are a couple of different approaches that can be taken. It's
important to note that bugzilla supports 3 layers, Classification,
P
On 10-11-18 12:23 AM, Saul Wold wrote:
On 11/17/2010 09:13 PM, Bruce Ashfield wrote:
On 10-11-17 8:29 PM, Darren Hart wrote:
On 11/17/2010 03:32 PM, Saul Wold wrote:
Folks,
After reviewing the emails from the first attempt and review bugzilla,
there are a couple of different approaches that
On 10-11-18 05:36 AM, Chris Tapp wrote:
Hi,
I've been evaluating OpenEmbedded and saw the announcement of 'Yocto'
on the mailing list. Yocto looks like it may be better for my needs as
it is more refined.
As there isn't currently support for the ALIX 3D3 (a Geode LX based
system), I am interest
On 10-11-28 3:39 AM, Robert Berger wrote:
Hi,
As far as I saw the beagleboard is supported by the yocto project.
What about the beaglebaord-xm?
I will create a training for the beaglebaord-xm and would like to show
yocto with it.
We don't currently have a kernel branch for it, but if sommeone
In message: [yocto] [PATCH] meta-bsp-kirkwood: created layer for Marvellkirkwood
on 28/11/2010 Frans Meulenbroeks wrote:
> This layer is a first attempt to create a layer for kirkwoord.
> It is based upon the OpenEmbedded recipes (most of which I have
> added too)
Sorry for the slow reply, the 3.
On 10-11-30 04:17 PM, Tim Bird wrote:
Hi all,
I am trying out yocto, and I get the following error during an initial build:
ERROR: Task failed: Fetch failed: Unable to fetch URL
git://git.pokylinux.org/linux-2.6-windriver.git;protocol=git;fullclone=1;branch=common_pc-standard;name=machine
fro
On 10-12-02 05:16 AM, Lu, Lianhao wrote:
Hi fellows,
Could anyone tell me why does the cp in do_install() change the file permission
mode? Thanks!
do_install () {
rm -rf ${D}${installed_dir}
install -d ${D}${installed_dir}
cp -rp ${S}/* ${D}${installed_dir}
}
After "bi
On 10-12-03 02:11 PM, Xianghua Xiao wrote:
On Fri, Dec 3, 2010 at 12:46 PM, Petr Štetiar wrote:
Michael J. Hammel [2010-12-03 11:01:27]:
Hi,
I've heard of Yocto only in passing. I'm assuming it's another
bitbake-based metabuild system? Is there some reasoning why
Meego/Linaro/OpenEmbedded
On 10-12-07 5:00 PM, Elizabeth Flanagan wrote:
I wanted to give people a heads up about the addition of a few more
targets to the nightly build and how they'll effect the nightly (and our
overall efficency).
This bug asks for the addition of a few targets:
arm: beagleboard: poky-image-sato, po
ylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Thanks,
Bruce Ashfield
---
Bruce Ashfield (3):
yocto-kernel: factor common routes, update to 2.6.37 and branch
renaming
linux-libc-headers-yocto: use common linux-yocto routines
qemu: update arm timer handling
meta-emenlo
backport two patches from the latest qemu
repositories that fix the timer handling under emulation. Long
term, these will be dropped when qemu is upreved.
Signed-off-by: Bruce Ashfield
---
.../qemu-0.12.4/arm_timer-fix-oneshot-mode.patch | 32
.../arm_timer-reload-timer-when
Modify linux-libc-headers-yocto to use the common linux-yocto
routines, so headers exported to userspace will track the
branches in the yocto kernel git repository.
This commit also switches supported boards to prefer the
yocto libc headers.
Signed-off-by: Bruce Ashfield
---
.../linux-libc
or the new kernel they will move from
-stable to the development kernel. As of now, only the
emulated targets have moved to 2.6.37-rcX
Signed-off-by: Bruce Ashfield
---
meta-emenlow/conf/machine/emenlow.conf |3 +-
meta/classes/kernel-yocto.bbclass
On 10-12-08 09:35 AM, Bruce Ashfield wrote:
Richard,
FYI: Darren pointed out that these should go to poky@
as well, so any follow ups will go to both lists. Sorry
about the initial miss!
Cheers,
Bruce
Consider these patches for merging. I've been building and working
with these
On 10-12-08 09:35 AM, Bruce Ashfield wrote:
In order to extend and create more kernel recipes based on the
supported yocto kernel common routines need to be placed in
re-usable blocks.
There may be a minor problem with this, stay tuned.
I just had a strange failure when I built the 2.6.37
On 10-12-08 09:35 AM, Bruce Ashfield wrote:
In order to extend and create more kernel recipes based on the
supported yocto kernel common routines need to be placed in
re-usable blocks.
To accomplish this meta/recipes-kernel/linux/linux-yocto_git.bb
is broken into three parts
On 10-12-08 03:20 PM, Bruce Ashfield wrote:
On 10-12-08 09:35 AM, Bruce Ashfield wrote:
In order to extend and create more kernel recipes based on the
supported yocto kernel common routines need to be placed in
re-usable blocks.
There may be a minor problem with this, stay tuned.
I just had
On 10-12-08 09:35 AM, Bruce Ashfield wrote:
Richard,
Consider these patches for merging. I've been building and working
with these for 2 weeks now, and while they aren't perfect, they
work and we need more eyes on 2.6.37.
Does anyone with the right admin privs have time to look
On 10-12-09 03:49 PM, Darren Hart wrote:
On 12/08/2010 06:35 AM, Bruce Ashfield wrote:
In order to extend and create more kernel recipes based on the
supported yocto kernel common routines need to be placed in
re-usable blocks.
To accomplish this meta/recipes-kernel/linux/linux-yocto_git.bb
is
On 10-12-09 3:49 PM, Darren Hart wrote:
On 12/08/2010 06:35 AM, Bruce Ashfield wrote:
In order to extend and create more kernel recipes based on the
supported yocto kernel common routines need to be placed in
re-usable blocks.
To accomplish this meta/recipes-kernel/linux/linux-yocto_git.bb
is
.git
Branch: zedd/kernel
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Thanks,
Bruce Ashfield
---
Bruce Ashfield (3):
yocto-kernel: factor common routes, update to 2.6.37 and branch
renaming
linux-libc-headers-yocto: use common linux-yocto routines
qe
or the new kernel they will move from
-stable to the development kernel. As of now, only the
emulated targets have moved to 2.6.37-rcX
Signed-off-by: Bruce Ashfield
---
meta-emenlow/conf/machine/emenlow.conf |3 +-
meta/classes/kernel-yocto.bbclass
Modify linux-libc-headers-yocto to use the common linux-yocto
routines, so headers exported to userspace will track the
branches in the yocto kernel git repository.
This commit also switches supported boards to prefer the
yocto libc headers.
Signed-off-by: Bruce Ashfield
---
.../linux-libc
backport two patches from the latest qemu
repositories that fix the timer handling under emulation. Long
term, these will be dropped when qemu is upreved.
Signed-off-by: Bruce Ashfield
---
.../qemu-0.12.4/arm_timer-fix-oneshot-mode.patch | 32
.../arm_timer-reload-timer-when
On 10-12-13 12:03 AM, Xu, Jiajun wrote:
On Sun, Dec 12, 2010 at 9:10 PM, Xu, Jiajun wrote:
[Resend with correct mailing lists]
Yocto / Poky Folks:
Thanks to everyone's hard work, we are currently on working getting
the first build of M2 started and available for QA testing on Monday.
I have
x.org/poky-contrib.git
Branch: zedd/kernel
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Thanks,
Bruce Ashfield
---
Bruce Ashfield (1):
qemuppc: update 2.6.37 SRCREV
.../conf/distro/include/poky-default-revisions.inc |2 +-
1 files changed, 1 insert
Fixes [BUGID: 585]
The qemuppc irq handling was only partially updated to 2.6.37,
this completes the job. qemuppc builds and boots with this
change.
Signed-off-by: Bruce Ashfield
---
.../conf/distro/include/poky-default-revisions.inc |2 +-
1 files changed, 1 insertions(+), 1 deletions
On Sun, Dec 12, 2010 at 9:10 PM, Xu, Jiajun wrote:
>> [Resend with correct mailing lists]
>>
>>
>> Yocto / Poky Folks:
>>
>> Thanks to everyone's hard work, we are currently on working getting
>> the first build of M2 started and available for QA testing on Monday.
>>
>> I have pushed out the last
On Mon, Dec 13, 2010 at 12:05 AM, Bruce Ashfield
wrote:
> On 10-12-13 12:03 AM, Xu, Jiajun wrote:
>>>
>>> On Sun, Dec 12, 2010 at 9:10 PM, Xu, Jiajun wrote:
>>>>>
>>>>> [Resend with correct mailing lists]
>>>>>
>>>>
s and
updated the emenlow to have a -stable bbappend.
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/kernel
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Thanks,
Bruce Ashfield
---
Bruce Ashfield (1):
linux-yocto: fix machine compatib
s and
updated the emenlow to have a -stable bbappend.
Signed-off-by: Bruce Ashfield
---
...it.bbappend => linux-yocto-stable_git.bbappend} |0
.../recipes-kernel/linux/linux-yocto-stable_git.bb |2 ++
meta/recipes-kernel/linux/linux-yocto.inc |2 --
meta/recipes-kernel/lin
On 10-12-13 11:47 AM, Scott Garman wrote:
On 12/13/2010 01:20 AM, Yu, Ke wrote:
Hi,
I hate to raise this question, but there is still bunch of bugs that
is fixed but not verified. According to the process, it is reporter's
responsibility to verify the bug, so could I ask the reporter's help
on
://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/blktrace
Thanks,
Bruce Ashfield
---
Bruce Ashfield (1):
linux-yocto/stable: add blktrace configuration to standard branch
.../conf/distro/include/poky-default-revisions.inc |2 +-
1 files changed, 1 insertions(+), 1 deletions
Enable the kernel configuration values required for blktrace
by default. Individual boards can opt out as required.
Signed-off-by: Bruce Ashfield
---
.../conf/distro/include/poky-default-revisions.inc |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta/conf/distro
On 10-12-14 02:40 AM, Ke, Liping wrote:
Hi, Jessica
I found qemu bin file name convention is different for different archs, for
example, for x86, it is bzImage-qemuXXX.
For arm, it is zImage-qemuXXX. My question is why it is bzXXX or zXXX, is there
any reason of such naming convention?
The l
required. This gives us the flexibility to map multiple
boards to a single branch for building.
Signed-off-by: Bruce Ashfield
---
meta/classes/kernel-yocto.bbclass | 12 +---
.../conf/distro/include/poky-default-revisions.inc |2 +-
.../recipes-kernel/linux/linux
kylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Thanks,
Bruce Ashfield
---
Bruce Ashfield (1):
linux-yocto: remove or adjust to _ in branch names
meta/classes/kernel-yocto.bbclass | 12 +---
.../conf/distro/include/poky-default-revisions.inc |2 +-
.../
On Fri, Dec 17, 2010 at 3:50 PM, Bruce Ashfield
wrote:
> The existing 2.6.34 kernel tree uses _ where poky typically
> uses -. This is a historical artifact, since working with
> gnu Make and shells means avoiding - is wise. The opposite
> is true in Yocto.
>
> To avoid us
The mapping of qemu to kernel branch name for the stable
kernel had a small leak from the devel kernel. Nothing
broke since qemux86 prefers the 2.6.37 kernel and this was
hidden.
This fixes the mapping for anyone who does want a 2.6.34 based
qemux86 kernel.
Signed-off-by: Bruce Ashfield
As the yocto-kernel advances, the libc headers must also
advance. This commit fixes the SRC_URI and SRCPV to work
properly with the latest linux-yocto kernel. It also switches
the qemu* targets to prefer this libc recipe.
Signed-off-by: Bruce Ashfield
---
meta/conf/machine/include/qemu.inc
Fixes [BUGID #596]
Updating the SRCREVs of the target branches in the linux-yocto
development kernel to point to 2.6.37-rc6 content.
At this point branches have been switched from _ to - and we
are able to remove the old branch names.
Signed-off-by: Bruce Ashfield
---
.../conf/distro/include
nches have been switched
from _ to - and we are able to remove the old branch names. (which
I have done).
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/kernel
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Thanks,
Bruce Ashfield
---
Br
On 10-12-22 11:09 AM, Cliff Brake wrote:
Hello,
I've started collecting ideas from various emails on multiple
repository support.
http://wiki.openembedded.org/index.php/MultipleRepositoryMethods
Please feel free to update the above page.
In my mind, this is a key problem we need to solve, not
The _ to - mass change mangled a config file name, which was
dropped from the update. This adds the fixed file back to the
meta branch of the kernel.
Signed-off-by: Bruce Ashfield
---
.../conf/distro/include/poky-default-revisions.inc |2 +-
1 files changed, 1 insertions(+), 1 deletions
1001 - 1100 of 1414 matches
Mail list logo
