Files
RASCSI/cpp/controllers/sasi_controller.h
T
Daniel Markstedt e57893893c restore support for SASI disk drive device
Introduce a SASI controller and SAHD disk implementation alongside the existing SCSI path. Select the appropriate controller when attaching a device, prevent SASI and SCSI devices from sharing a target ID, and implement SASI-specific selection, message, status, timing, and LUN handling.

Restore SAHD in the protocol and expose it consistently through the device factory, command-line client, configuration validation, web interface, drive profiles, and manual. Enforce the two-LUN limit for SASI targets wherever device definitions are created or parsed.

Bring back handling of the hdf image format and map it to the SAHD device type. The hdf file ending is the established one for SASI raw disk images used in the X68000 emulation community, however it is a raw data format without any special header.

Add focused C++ and Go coverage for SASI devices, controller selection, LUN validation, and web-facing behavior.
2026-08-30 08:27:35 +02:00

31 lines
844 B
C++

//---------------------------------------------------------------------------
//
// SCSI Target Emulator PiSCSI
// for Raspberry Pi
//
// Copyright (C) 2026 Daniel Markstedt <daniel@mindani.net>
//
//---------------------------------------------------------------------------
#pragma once
#include <algorithm>
#include "scsi_controller.h"
class SasiController final : public ScsiController
{
public:
SasiController(BUS&, int);
~SasiController() override = default;
bool IsSasi() const override { return true; }
int GetEffectiveLun() const override;
void MsgOut() override;
protected:
// Use a 100 us baseline for SASI commands rather than the SCSI default
// of 50 us, needed for timing-sensitive initiators such as the X68000.
unsigned int GetMinimumExecutionTime() const override { return std::max(100U, MIN_EXEC_TIME); }
};