-
Notifications
You must be signed in to change notification settings - Fork 423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
linux-raspberrypi_6.1.bb: Update to 6.1.61 release #1245
Conversation
Signed-off-by: Khem Raj <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Approved and merged.
kirkstone doesn't even have a 6.X version, and changing a major kernel version in a stable branch is not something that I would jump onto without some deep considerations on regressions. Is mixin layer something we could work with as a workaround here? I can't speak of other branches as this needs to be dealt with on a case-by-case basis. |
Kirkstone being the LTS release supported until 2026 I think it would make sense to have kernel updates on that branch, especially since we'd need a kernel update to support the Pi 5. |
I was thinking of something like: https://docs.yoctoproject.org/ref-manual/terms.html#term-Mixin I could create a |
If you never plan on updating the kernel version in a LTS release then I guess we could try mixins. |
@agherzan you can hold on that for the moment, I don't think we'll go the mixin path after all. |
Can this PR instead be ported to nanbield? Or mickledore if nanbield is not supported by meta-raspberrypi outside of master? |
I am okay with a backport on supported Yocto versions as long as it is a patch update as this MR. |
No description provided.