(WIP) Rpi arm64 support #16
Closed
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
added support for raspberry pi 4
Update typing in fablib/installer.py.
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.
Until this PR is merged, when using an RPi, please ensure that you use, and where relevant issue PRs against, the
rpi-arm64branch.Important note: As development proceeds, from time to time, this branch will be rebased on
master(and force pushed if/when needed). That may make things tricky at times, but please post a comment here if you have any troubles.[update] actually, I might merge other code changes into this branch first, then merge it all into master. That will reduce need to rebase (and force push) plus will allow more testing of other dev code (on RPI) before merged into master. This can allow development to happen a bit faster too.
To date includes: