summaryrefslogtreecommitdiffstats
path: root/meta-yocto-bsp/recipes-kernel
Commit message (Collapse)AuthorAgeFilesLines
* linux-yocto: Fix SRCREVs in linux-yocto_3.2Paul Barker2013-07-291-4/+4
| | | | | | | | | | | The KERNEL_VERSION set by linux-yocto_3.2.bb in openembedded-core is 3.2.32 but the SRCREVs in the bbappend in meta-yocto-bsp referred to version 3.2.18. These SRCREVs are updated to the correct values. (From meta-yocto rev: ead5d53222c811c68e3bed74a297bb0a11a72156) Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/meta-yocto-bsps: update h/w references to v3.4.36Bruce Ashfield2013-03-261-5/+4
| | | | | | | | | 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: use KERNEL_IMAGE_MAXSIZE to test the imageMichel Thebeau2013-03-221-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | 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>
* meta-yocto/linux-yocto: update qemu BSPs to 3.8 kernelBruce Ashfield2013-03-023-40/+14
| | | | | | | | | | | | | | | | 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>
* linux-yocto/meta-yocto: update hardware reference BSPs to 3.4.26 and LTSIBruce Ashfield2013-01-201-4/+5
| | | | | | | | | | 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>
* linux-yocto-bsps/3.4: perf: parallel build and tools fixesBruce Ashfield2012-10-081-4/+4
| | | | | | | | | | | | | | | | | | | | | | 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>
* linux-yocto-bsps: update hardware reference BSPs to v3.4.11Bruce Ashfield2012-10-081-5/+4
| | | | | | | | | | | | | | | 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>
* beagleboard: update to 3.4Bruce Ashfield2012-09-251-1/+1
| | | | | | | | | | | | | | | 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>
* linux-yocto/meta-yocto/3.4: update machine SRCREVsBruce Ashfield2012-09-241-4/+4
| | | | | | | | | | 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>
* meta-yocto: Split into distro and bsp componentsRichard Purdie2012-09-054-0/+69
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>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-12 05:51:14 +0000