3553 2012-12-10 11:18:00 +0000 Upgrade kernel to 3.8 2012-12-13 15:35:38 +0000 1 1 7 Build System, Metadata & Runtime OE-Core kernel 1.4 x86 Multiple RESOLVED NOTABUG Undecided enhancement --- 0 alexandru.damian bruce.ashfield bruce.ashfield dvhart tom.zanussi --- --- --- oldest_to_newest 28111 0 alexandru.damian 2012-12-10 11:18:00 +0000 Current situation: --------------------- kernel version: 3.0 / 3.4 on different BSPs. Desired outcome: --------------------- Kernel 3.7 on all BSPs. Details ------- We need to move all the Yocto project kernels to 3.7 (When will be available) in accordance to the policy of having up-to-date upstream sources. Significant speed improvements and support for QEMU DRM device make this an important update. Need to also activate CONFIG_DRM_CIRRUS_QEMU=y for the qemu configs. 28112 1 bruce.ashfield 2012-12-10 12:27:59 +0000 We won't do an urev to 3.7. The dev kernel is already there, but it is too old for 1.4. The next official version bump and BSP uprev will be the 3.8 kernel. We'll work through the -rc's of its development and port features accordingly. When dev starts I'll open a bugzilla at that point. 28113 2 alexandru.damian 2012-12-10 12:37:03 +0000 I would like more details on what do you mean by - it is too old for 1.4; what is "it", and why it is too old for 1.4 - what are there the reasons for jumping to 3.8 when 3.7 is not even out yet 28114 3 bruce.ashfield 2012-12-10 12:58:01 +0000 Sure, I can explain. The kernel is not managed like any other package in the system, we have a defined cadence and update cycle. The details used to be accessible from the main yocto page, but I'm not sure if they are at the moment. We do not jump to each and every kernel that is available, each release has a sliding window of three kernels available: - "the latest" - a LTSI kernel (usually the previous release's "latest kernel") - the last non-LTSI kernel released i.e. 3.4, 3.2, and 3.0 for yocto 1.3. There is also a linux-yocto-dev that continually chances the latest kernel for those that want to work on something bleeding edge, and linux-yocto-custom for those that want random other kernel versions. We don't lock the latest kernel version until roughly 6 weeks before the release, and that's just the kernel version, not the actual BSP uprevs. We sometimes can predict the version more than 6 weeks out, and it those cases, we'll declare it early. 3.7 will release in the next few days, making it too old for the "latest" kernel in the 1.4. 3.8 is the likely bet for the yocto 1.4 release kernel, but even with that said, we won't confirm it yet. We also do the kernel updates and BSP uprevs as part of the kernel teams planning for each yocto release planning, so there is always a plan with respect to kernel versions. 28115 4 alexandru.damian 2012-12-10 13:02:59 +0000 This is very clear, thanks. I edited the bug to say upgrade to 3.8. I also moved the bug to "UNCONFIRMED" because it seems we don't have a state for "waiting for upstream". I think any kernel post 3.6 should be in the final release to make sure wayland/weston is able to run on top of QEMU. 28116 5 bruce.ashfield 2012-12-10 13:04:42 +0000 ok. This is fine, I'll put it under my name as well, since I'll definitely be updating the kernel and pushing out new recipes in the not too distant future! 28242 6 dvhart 2012-12-13 15:35:26 +0000 We'll continue to handle this via the process Bruce described. If there are any other concerns on this topic, please contact Bruce and myself.