English fork of the Japanese RaSCSI project. RaSCSI allows a Raspberry Pi to function as emulated SCSI devices (hard disk, CD-ROM, and others) for vintage SCSI-based computers and devices.
Go to file
akuker ebf4cec6ee
Hardware Version 2.5 (#720)
* Added header for external ENB LED

* test fixture for rascsi

* test fixture for rascsi

* Updated to Kicad 6 and modified act LED

* Regenerated Gerber files to fix drill placement. Added CE logo

* Regeneraged gerbers

Co-authored-by: Tony Kuker <akuker@gmail.com>
2022-03-03 11:06:40 -08:00
.github Disable the rpi build for develop and master (#330) 2021-10-14 13:20:57 -07:00
doc Fixed missing media change handling (#690) 2022-02-21 21:01:17 +01:00
docs Merge Hw 2p4 to develop (#109) 2021-06-08 19:06:29 -05:00
hw Hardware Version 2.5 (#720) 2022-03-03 11:06:40 -08:00
python 8bit encoder detection + debounced button detection, numpy removal (#710) 2022-03-01 20:27:14 -06:00
src Validate SEEK block address (#719) 2022-03-03 12:53:11 -06:00
test/robot Create new test cases for checking that the user can specify the TCP Port number (#154) 2021-07-27 18:40:00 -05:00
_config.yml
.gitignore restructuring towards python client library #455 (#613) 2022-01-21 15:08:29 -08:00
easyinstall.sh 8bit encoder detection + debounced button detection, numpy removal (#710) 2022-03-01 20:27:14 -06:00
LICENSE Updated copyrights and versions 2021-10-29 21:55:24 -05:00
lido-driver.img
README.md Support ICD (Atari ACSI) command semantics (#640) 2022-02-04 19:45:10 -06:00

What is RaSCSI?

RaSCSI is a virtual SCSI device emulator that runs on a Raspberry Pi. It runs in userspace, and can emulate several SCSI devices at one time. There is a control interface to attach / detach drives during runtime, as well as insert and eject removable media. This project is aimed at users of vintage Macintosh and Atari computers and more (see compatibility list) from the 1980's and 1990's.

Please check out the full story with much more detail on the wiki!

How do I contribute?

RaSCSI is using the Gitflow Workflow. A quick overview:

  • The master branch should always reflect the contents of the last stable release
  • The develop branch should contain the latest tested & approved updates. Pull requests should be used to merge changes into develop.
  • The rest of the feature branches are for developing new features
  • A tag will be created for each "release". The releases will be named . (for the first release of the month). Hot fixes, if necessary, will be released as ... For example, the first release in January 2021 will be release "21.01". If a hot-fix is needed for this release, the first hotfix will be "21.01.1".

Typically, releases will only be planned every few months.

I sell on Tindie

Github Sponsors

Thank you to all of the Github sponsors who support the development community!

Special thank you to the Gold level sponsors!

Special thank you to the Silver level sponsors!