-
Notifications
You must be signed in to change notification settings - Fork 417
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
Update kernel/firmaware #1220
Update kernel/firmaware #1220
Conversation
Signed-off-by: Khem Raj <[email protected]>
recipes-kernel/linux-firmware-rpidistro/linux-firmware-rpidistro_git.bb
Outdated
Show resolved
Hide resolved
Signed-off-by: Khem Raj <[email protected]>
Symlinks are no longer needed as they already exist in the new raspbian firmware tarball Signed-off-by: Khem Raj <[email protected]>
Drop a backport already in 1.2-4+rpt10 Signed-off-by: Khem Raj <[email protected]>
Signed-off-by: Khem Raj <[email protected]>
* oe-core switched to nanbield in: https://git.openembedded.org/openembedded-core/commit/?id=f212cb12a0db9c9de5afd3cc89b1331d386e55f6 Signed-off-by: Martin Jansa <[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!
@kraj I can't seem to find much information on what the latest version of the RPI firmware is. I see some tags, in some repos, but I can't seem to figure it out. I was wondering if you could help me to understand why you are updating to the buster version of the firmware and not the latest version of bullseye? It is my understanding that if we are on the 6.1.54 kernel for the yocto recipe, we would want to also have the bullseye firmware as it will support that kernel (as opposed to 5.x.x version for buster). I have tried the latest bullseye and it works just fine. Should I expect issues? or should I be fine? https://github.com/RPi-Distro/firmware/blob/pios/bullseye/debian/changelog |
You should be fine if it tests out fine infact post a pull here as well |
Sounds good thanks, we've been testing quite a bit if don't see any issues I might open a PR. |
- What I did
- How I did it