The 65C02 only triggers the I/O. The actual I/O is done completely by the host in a paravirtualization style. From the 65C02 perspective, the I/O happens during a single cycle.
Notes:
I'm personally not interested in providing any Neo6502 firmware to the public. Neither do I see myself contributing regularly to any Neo6502 firmware. So I'd really appreciate if you would merge this pull request.
It is supposed to be very easy to replace the hard disk image(s) integrated into the firmware with actual .po files in an FAT filesystem on a USB mass storage class device or an SD card. Although I haven't tested it, I presume hard disk write operations to work out-of-the box there.
oliverschmidt
commented
1 year ago
The 65C02 only triggers the I/O. The actual I/O is done completely by the host in a paravirtualization style. From the 65C02 perspective, the I/O happens during a single cycle.
Notes:
I'm personally not interested in providing any Neo6502 firmware to the public. Neither do I see myself contributing regularly to any Neo6502 firmware. So I'd really appreciate if you would merge this pull request.
It is supposed to be very easy to replace the hard disk image(s) integrated into the firmware with actual .po files in an FAT filesystem on a USB mass storage class device or an SD card. Although I haven't tested it, I presume hard disk write operations to work out-of-the box there.