| Summary: | Upgrade kernel to 3.8 | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Alexandru Damian <alexandru.damian> |
| Component: | kernel | Assignee: | Bruce Ashfield <bruce.ashfield> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Undecided | CC: | bruce.ashfield, dvhart, tom.zanussi |
| Version: | 1.4 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Alexandru Damian
2012-12-10 11:18:00 UTC
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. 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 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. 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. 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! 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. |