-
Notifications
You must be signed in to change notification settings - Fork 103
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #234 from keepkey/version-6.5.1
firmware version 6.5.1
- Loading branch information
Showing
203 changed files
with
28,159 additions
and
25,550 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
--- | ||
BasedOnStyle: Google | ||
# Google style has a default of 80 lines, but clang-format 7 disregards it in | ||
# a weird case in modtrezorio-fatfs.h. Setting it explicitly helps. | ||
ColumnLimit: 80 | ||
# This setting differs between clang-format 7 and 9. | ||
# Let's set it explicitly to v7 value | ||
IncludeBlocks: Preserve | ||
SortIncludes: false |
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 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
Submodule python-keepkey
updated
13 files
+2 −2 | .circleci/config.yml | |
+2 −1 | keepkeyctl | |
+3 −0 | keepkeylib/client.py | |
+57 −37 | keepkeylib/transport_hid.py | |
+1 −1 | setup.py | |
+4 −0 | tests/common.py | |
+1 −1 | tests/run.sh | |
+15 −3 | tests/test_msg_clearsession.py | |
+20 −0 | tests/test_msg_loaddevice.py | |
+22 −4 | tests/test_msg_ping.py | |
+3 −0 | tests/test_msg_signtx_segwit.py | |
+12 −2 | tests/test_protection_levels.py | |
+149 −0 | tests/test_vuln20007.py |
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 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 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 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 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 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 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
Oops, something went wrong.
a988325
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.
I see a v6.5.1 tag in the
Releases
section. But where is the corresponding firmware binary for it? It looks like the bootloader also got bumped up to v2.1.0, Is that required over v2.0.0 for this to work? Again where is the bootloader binary for v2.1.0?