On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
Richard/Saul,
Here's my consolidated set of changes that represent the biggest chunk
of work for the Yocto 1.5 release. The obvious change is that the 3.10
kernel is now the latest linux-yocto kernel (and linux-yocto-dev will
mark on). I've built
On 13-08-24 2:33 AM, Saul Wold wrote:
On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
Richard/Saul,
Here's my consolidated set of changes that represent the biggest chunk
of work for the Yocto 1.5 release. The obvious change is that the 3.10
kernel is now the latest linux-yocto kernel (and
On 13-08-23 8:57 PM, Jonathan Liu wrote:
On 24/08/2013 4:08 AM, Bruce Ashfield wrote:
Introduce the 3.10 kernel. This is based on the 3.10.9 upstream kernel
and replaces the 3.8 recipes, which will be removed once all reference
boards have been updated.
3.10 also the latest LTSI and will be
On 13-08-24 9:34 AM, Bruce Ashfield wrote:
On 13-08-24 2:33 AM, Saul Wold wrote:
On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
Richard/Saul,
Here's my consolidated set of changes that represent the biggest chunk
of work for the Yocto 1.5 release. The obvious change is that the 3.10
kernel is
On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
On 13-08-24 9:34 AM, Bruce Ashfield wrote:
On 13-08-24 2:33 AM, Saul Wold wrote:
On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
Richard/Saul,
Here's my consolidated set of changes that represent the biggest chunk
of work for the Yocto 1.5 release.
On 13-08-24 9:50 AM, Saul Wold wrote:
On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
On 13-08-24 9:34 AM, Bruce Ashfield wrote:
On 13-08-24 2:33 AM, Saul Wold wrote:
On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
Richard/Saul,
Here's my consolidated set of changes that represent the biggest
On 13-08-24 9:50 AM, Saul Wold wrote:
On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
On 13-08-24 9:34 AM, Bruce Ashfield wrote:
On 13-08-24 2:33 AM, Saul Wold wrote:
On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
Richard/Saul,
Here's my consolidated set of changes that represent the biggest
On 13-08-24 9:50 AM, Saul Wold wrote:
On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
On 13-08-24 9:34 AM, Bruce Ashfield wrote:
On 13-08-24 2:33 AM, Saul Wold wrote:
On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
Richard/Saul,
Here's my consolidated set of changes that represent the biggest
There is a good chance we might want to support a bitbake operator
_remove which works in a similar way to _append and _prepend. As
such, we can't use those keywords in function or variable names.
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
diff --git
On 13-08-24 9:50 AM, Saul Wold wrote:
On 08/24/2013 06:45 AM, Bruce Ashfield wrote:
On 13-08-24 9:34 AM, Bruce Ashfield wrote:
On 13-08-24 2:33 AM, Saul Wold wrote:
On 08/23/2013 11:08 AM, Bruce Ashfield wrote:
Richard/Saul,
Here's my consolidated set of changes that represent the biggest
This patch adds a patch for Qt-Embedded to only
destroy semaphores in the process which created
them.
Original patch by Neil Jerram for the OpenMoko project:
http://lists.openmoko.org/pipermail/community/2012-November/067806.html
See also Bug 31254:
On Thu, 2013-08-22 at 18:04 -0500, Jason Wessel wrote:
This patch aims to fix the following two cases for the INITRAMFS generation.
1) Allow an image recipe to specify a paired INITRAMFS recipe such
as core-image-minimal-initramfs. This allows building a base
image which always
On 08/24/2013 09:49 AM, Eric Nelson wrote:
This patch adds a patch for Qt-Embedded to only
destroy semaphores in the process which created
them.
Original patch by Neil Jerram for the OpenMoko project:
http://lists.openmoko.org/pipermail/community/2012-November/067806.html
See also Bug
This is strange. According to the bugtracker it should be in 4.8.5
already... and the recipe seems to be about 4.8.5. It needs more
investigation.
On Sat, Aug 24, 2013 at 8:13 PM, Saul Wold s...@linux.intel.com wrote:
On 08/24/2013 09:49 AM, Eric Nelson wrote:
This patch adds a patch for
Hi Laszlo,
On 08/24/2013 12:15 PM, Laszlo Papp wrote:
This is strange. According to the bugtracker it should be in 4.8.5
already... and the recipe seems to be about 4.8.5. It needs more
investigation.
I saw this, but there's no evidence that any change was committed
and I verified that the
Well, you should ask upstream about it... maybe it ended up in a decision
it is the wrong way, and something better went in, or being planned to go
in. I think a change should not be integrated like this in grey area.
On Sat, Aug 24, 2013 at 8:25 PM, Eric Nelson
eric.nel...@boundarydevices.com
Thanks Laszlo,
On 08/24/2013 12:28 PM, Laszlo Papp wrote:
Well, you should ask upstream about it... maybe it ended up in a
decision it is the wrong way, and something better went in, or being
planned to go in. I think a change should not be integrated like this in
grey area.
I just posted to
I replied in there.
On Sat, Aug 24, 2013 at 8:51 PM, Eric Nelson
eric.nel...@boundarydevices.com wrote:
Thanks Laszlo,
On 08/24/2013 12:28 PM, Laszlo Papp wrote:
Well, you should ask upstream about it... maybe it ended up in a
decision it is the wrong way, and something better went in,
From: Stefan Stanacar stefanx.stana...@intel.com
A layer can add tests in lib/oeqa/runtime (provided it extends BBPATH as
normal) and enable them with TEST_SUITES_append = testname. Test
module names shouldn't collide though.
Signed-off-by: Stefan Stanacar stefanx.stana...@intel.com
Completion of an earlier work-in-progress change by Stefan. I had
earlier suggested using a special tests/runtime directory in other
layers that wish to add their own tests, but when I looked into it I
figured it was actually a lot simpler if we kept the same structure as
the tests in OE-Core i.e.
With the introduction of the 3.10 linux-yocto tree, 3.4 being the previous
LTSI kernel, and no reference BSPs using 3.8 as their reference BSP it
3.8 is no longer supported or required.
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
meta/recipes-kernel/linux/linux-yocto-rt_3.8.bb
Introduce the 3.10 kernel. This is based on the 3.10.9 upstream kernel
and replaces the 3.8 recipes, which will be removed once all reference
boards have been updated.
3.10 also the latest LTSI and will be updated with that content when it
becomes available.
Other features of the 3.10 kernel
Now that the 3.10 kernel has been released we can bump the libc-headers to
that version and remove the 3.8 variant. Userspace compatibility is
maintained through kernel versions, we also make the single 3.10 version the
toolchain default.
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
Updating the kern-tools SRCREV to pick up the following fixes:
60a894e kgit-s2q: add proper commit ID handling for mixed am/apply usage
3b08257 kgit-s2q: delete pruning of path support.
c5868b4 kgit-s2q: Restore implicit exit status to git apply section
1bd00b9 kgit-scc: mask warnings
kernel commit 24b9f5017 [[media] V4L: Remove deprecated image centering
controls]
removed the definitions of V4L2_CID_HCENTER and V4L2_CID_VCENTER after three
years of depreciation.
The ioctl values are still free, and the case statement which processess them
in v4l2 userspace falls through to
Uprev guilt to the latest guilt version from its upstream repository.
As part of the uprev all of the previous changes required for the
yocto kernel tools to use git to manipulate series files have been
dropped. These changes were specific to circumventing parts of guilt's
internal santiy checking
Richard/Saul,
I managed to find enough time to turn around some fixes ..
This series completely replaces the one that I had sent before. It fixes
the two issues that Saul reported: a patch issue with the 3.8 arm BSPs
and the ptrace.h related build failures from the 3.10 libc-headers
Changes
linux kernel commit 84c751bd [ptrace: add ability to retrieve signals without
removing from a queue (v4)]
added ptrace_peeksiginfo_args to the exported kernel user api.
This leads to build errors such as:
| In file included from
28 matches
Mail list logo
