Fix for handle 256bytes sectors format not to use fast seek#348
Open
sweproj wants to merge 2 commits intoBlueSCSI:mainfrom
Open
Fix for handle 256bytes sectors format not to use fast seek#348sweproj wants to merge 2 commits intoBlueSCSI:mainfrom
sweproj wants to merge 2 commits intoBlueSCSI:mainfrom
Conversation
added 2 commits
March 12, 2026 17:52
…l add wrong data into the buffer
Contributor
|
Thanks for taking the time to dig in and open a PR! 256 byte does not get tested as much so glad you were able to test and propose a solution. I'll hopefully have some time to review your PR's in the next few days. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fast seek will add wrong data into the buffer due to 512b buffer