Skip to content
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

Initiator configuration options #523

Merged
merged 2 commits into from
Feb 21, 2025
Merged

Initiator configuration options #523

merged 2 commits into from
Feb 21, 2025

Conversation

PetteriAimonen
Copy link
Collaborator

Adds two new .ini configuration options for initiator mode:

  • InitiatorMSCReadOnly: Prevents writes to the drive through USB MSC mode
  • InitiatorUseRead10: Forces usage of either READ6 (setting 0) or READ10 (setting 1) SCSI command. If config option is not specified, the support is autodetected.

The autodetection is added to resolve the #519 problems without having to do any configuration. The config option is provided in case we find some drive which totally freaks out on unknown commands, instead of gracefully returning error status.

@aperezbios I have tested this with the drives I have, but they all support READ10 command.
If you still have Apple Quantum ProDrive 80S and time to test it with initiator mode, that could be a good idea before merging this pull request.

IBM H3171-S2 reports SCSI version 1 and supports both READ10 and READ6.
But READ6 fails in weird ways.

Changed the logic so that:
1) If InitiatorUseRead10 is specified in zuluscsi.ini, it forces the mode.
2) Otherwise READ10 support is detected by trying to run the command.
USB MSC drive can be configured as readonly by setting in .ini:

[SCSI]
InitiatorMSC = 1 # Needed to enable MSC mode with SD card present
InitiatorMSCReadOnly = 1
@aperezbios aperezbios merged commit 959f27f into main Feb 21, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants