64bit LBA support (> 2TiB disk support) #68
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
Closed
antoinevg
force-pushed
the
support_64bit_LBA
branch
from
62aaab7 to
0fcd485
Compare
antoinevg
force-pushed
the
support_64bit_LBA
branch
from
0fcd485 to
be15182
Compare
|
Rebased in #89 |
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.
The current code only supports 32-bit LBAs and does not support 64-bit LBAs.
Therefore, when a disk of 2 TiB or larger is connected, "READ CAPACITY" does not report the correct capacity. (However, if the disk is initialized with GPT, the current code can still be used.)
To improve this, "READ CAPACITY (16)", "READ (16)", and "WRITE (16)" have been implemented.