Jump to content

uyjulian

6502
  • Content Count

    90
  • Joined

  • Last visited

Recent Profile Visitors

441 profile views
  1. Latest GCC has more proper support for language features and has more optimizations. Also, it has a higher possibility to be automated with Continuous Integration compared to older toolchains.
  2. Looks like only emulation of fastram, IDE, mmu, fpu, and CPU. Rest is real hardware. I think the idea of PiStorm is nice, as you could have similar possibilities as RaSCSI but with more bandwidth. It looks like A314 (trapdoor expansion for Raspberry Pi) services can be integrated on the PiStorm.
  3. On Pi4, USB is implemented over PCIe. On CM4, the PCIe bus is exposed, allowing you to add USB or another interface. (PCIe<->PCI<->NuBus?)
  4. Most likely. The eMMC would take up the place of the SD connection.
  5. You can also use an eMMC to microSD adapter for your Raspberry Pi. eMMC are more reliable than microSD
  6. Binutils does not require any patches. The version used is 2.10.1. The last version of Binutils to support m68k-coff format is 2.16.1. GCC requires patches. I ported the patch to 2.7.2.3 in unified format. Retro68 exists, but it creates applications for the Macintosh environment, not the UNIX environment. https://github.com/autc04/Retro68
  7. If I remember correctly, GCC is pre-installed on this image: https://github.com/unxmaal/aux_sdcard Be aware that it is an older GCC based on the 2.7 series. I planned to port GCC 10 but other things took my time. You cannot use the GCC patch as-is when cross-compiling, since it requires the native assembler instead of the one from GNU Binutils. It would be nice to use QEMU userspace emulation to run the programs from A/UX…
  8. I think it would be possible for terminator power. However, as mentioned before, the Raspberry Pi needs to be up first before the Mac. Powering the Raspberry Pi using the terminator power would be possible if the Mac has a lot of RAM, and thus takes a while doing the RAM check, giving time for the Raspberry Pi to start up.
  9. A SCSI Manager API shim on the Pi side would be nice so you don't have to learn 2 different APIs… https://developer.apple.com/library/archive/documentation/mac/pdf/Devices/SCSI_Manager.pdf // Constants enum { /* TIB instruction opcodes */ scInc = 1, /* transfer data, increment buffer pointer */ scNoInc = 2, /* transfer data, don’t increment pointer */ scAdd = 3, /* add long to address */ scMove = 4, /* move long to address */ scLoop = 5, /* decrement counter and loop if > 0 */ scNop = 6, /* no operation */ scStop = 7, /* stop TIB execution */ scComp = 8, /* c
  10. The Unarchiver already exists. For something written in C, this project was made to extract System 6 disk images, based on The Unarchiver sources: https://www.gryphel.com/c/minivmac/extras/ua608d/index.html
  11. https://github.com/autc04/Retro68#apple-universal-interfaces-vs-multiversal-interfaces
  12. Retro68 has assembler and C compiler targeting classic Mac OS.
  13. For the ethernet driver, someone developed some hardware that can be used with existing driver: I wonder how portable it is to RaSCSI… I haven't taken a look at the sources
  14. I would recommend that you check out unar source code, which can extract Stuffit files (including resfork): https://cdn.theunarchiver.com/downloads/TheUnarchiverSource.zip
  15. Source code is up, so you can start manufacturing your own now. https://github.com/saybur/scuznet
×
×
  • Create New...