| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
Updating the hardware reference boards to the korg 3.4.36 -stable release.
(From meta-yocto rev: bd862239aaaa3ea874f110e4ffb04488db83de47)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
routerstationpro is limited to 16mb flash size. Exceeding that size may
not be noticed immediately, which we don't want.
"The current latest kernel for the routerstationpro machine is far
beyond the 16MB of it's flash size [0]. I think it would be good to
[test if the size of the image is above that size]."
Setting this variable will enable the do_sizecheck task and produce an
error when the image is too large:
"ERROR: This kernel (size=90230265 > 16777216) is too big for your
device. Please reduce the size of the kernel by making more of it
modular."
[YOCTO #3514]
(From meta-yocto rev: bb25e15c62cdde749f34050933d056a79dd2d3c5)
Signed-off-by: Michel Thebeau <michel.thebeau@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change linux-yocto preferred version to 3.8 for the qemu BSPs. The
non-qemu default stays at 3.4 until the hardware reference platforms
can be validated on the 3.8 kernel.
At the same time, we remove the 3.0 linux-yocto bbappends, since they
have been removed in the core layers and will cause dangling append
problems if left in place.
(From meta-yocto rev: 896b845e0e574f4c4f2205e0516c00f178dde185)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
| |
Bumping the yocto reference BSPs to pickup the latest oe-core 3.4.26, -rt
and LTSI updates.
(From meta-yocto rev: fa7adfafb521e7de81beebd4525a5d2ce1763dc3)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
korg commit 42dcd1f4e [perf tools: Fix parallel build] fixes parallel
build issues that are being seen in the autobuilder.
We also have a fix from Tom:
[
perf annotate: replace 'expand' with equivalent sed expression
We don't have 'expand' in our userspace so we need to accomplish the
same thing using 'sed', which we do have.
]
So we apply it to all BSP branches and kernel types.
(From meta-yocto rev: 54fc1fd107f907a208b41a66c0a7b9b40cb428c7)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The hardware reference BSPs are missing the update to 3.4.11
that the qemu* machines received several weeks ago.
Bumping to 3.4.11 specifically addresses the segfaults being
seen with rpm on the beagleboard.
[YOCTO #3186]
(From meta-yocto rev: f2d93f4e79d0c8c0035774cfa7dc4beb197899f4)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updating the default preference of the beagleboard to the 3.4
kernel.
build, boot and testing has been done on the beagleboard (revC) and
beagleboard XM. Existing functionality has been confirmed using
core-image-sato, and in particular mouse, keyboard and graphics have
been re-validated.
(From meta-yocto rev: 32c46737618a7e2b084d807a901000ae9abc1354)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
| |
The hardware reference BSPs are lagging the oe-core qemu BSPs. Bumping
their SRCREVs to pickup 3.4.10 and minor bug fixes.
(From meta-yocto rev: 87881c14af993b27aad71dc3584ef488c8c41ab0)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
Now we have settled on best practises and compliance criteria, bring meta-yocto
into compliance by separating out the hardware support components into
meta-yocto-bsp leaving policy configuration in meta-yocto.
Also rename the meta-yocto scripts directory to OE-Core can be a clearly
isolated component in poky.
(From meta-yocto rev: eac90e27a032ea23d9a4f35c7eef8b1940c80e22)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
