-
Notifications
You must be signed in to change notification settings - Fork 10
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
Yocto 3.0.x upgrade #28
Open
pcouto64
wants to merge
10
commits into
master
Choose a base branch
from
yocto-3.0.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is the latest Zeus release, although there is a dunfell-23.0.1 which I'll upgrade to next...
…rade Stricter checks on strncpy() args, etc.
There is also a new 3.1.2 release that perhaps should be added to this branch: http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.2/RELEASENOTES |
Latest in this stream, still need to update to 3.1.x now that it is more mature.
Are these changes ready to merge? |
Hmm, these could go in if anyone cares at this point. They are “old” by now, Yocto has moved on to later releases but I can’t say I’ve had the time to play with this older hardware recently. I don’t think I updated the v3 hub with these changes, but no one really has that hardware from what I recall.
Paul Couto
Couto Software Consulting, LLC
o: (617) 475-0750
c: (978) 430-9553
… On Jan 29, 2022, at 4:04 PM, Andrew Sorensen ***@***.***> wrote:
Are these changes ready to merge?
—
Reply to this email directly, view it on GitHub <#28 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJLX75IGPFR5CT7K4ZVY5DUYRI6HANCNFSM4OKUTTQA>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Turns out this wasn't as problematic upgrade as other major ones have been for the meta-iris code, just some compiler issues to sort out. For the v2 hub, the kernel remains the same since it is newer than the default beaglebone-black one in this release. For the v3 hub, there is a 4.19.x kernel which we could switch to - I will create a new issue for that as it will take a bit more work to update our kernel patches and test.