From: emanuel stiebler <emu@e-bbes.com>
To: Paul Ruizendaal <pnr@planet.nl>, TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Blit source
Date: Tue, 17 Dec 2019 07:04:42 +0100 [thread overview]
Message-ID: <d288dee4-6a0e-8c84-44e6-b0f6aa3afef4@e-bbes.com> (raw)
In-Reply-To: <E98B9D8E-FD64-40A8-BE95-404DD3AE6868@planet.nl>
On 2019-12-16 12:06, Paul Ruizendaal wrote:
> It would seem that the circuit was intentionally simple and straightforward: a M68K cpu, ram, rom, two 6850 UARTS and the circuit to drive the display. The key aspects of the video circuitry (and mouse circuitry) are discussed in this paper:
> https://9p.io/cm/cs/doc/87/archtr.ps.gz ("Hardware/Software Tradeoffs for Bitmap Graphics on the Blit”).
Thanks!
> It would seem to me that doing a version of the Blit that runs on a FPGA board and generates 720p HDMI output would not be impossible to do,
It actually pretty simple, all this stuff is avalable on AMIGA emulators
for FPGAs ...
> if the software can be configured to deal with a different geometry (e.g. 1024x720 instead of 800x1024). Whether that would be much different from running the emulator on a PC remains unclear, of course.
It is on my list of things to do, but not on the first page ;-)
Still waiting, that schematics & sources show up ...
next prev parent reply other threads:[~2019-12-17 6:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 20:45 Paul Ruizendaal
2019-12-15 21:17 ` Angelo Papenhoff
2019-12-16 6:25 ` emanuel stiebler
2019-12-16 11:06 ` Paul Ruizendaal
2019-12-17 6:04 ` emanuel stiebler [this message]
2019-12-18 3:53 ` Paul Ruizendaal
2019-12-18 4:30 ` Rob Pike
2019-12-18 10:43 ` Julius Schmidt
2019-12-18 12:11 ` Angelo Papenhoff
2019-12-18 15:53 ` Dan Cross
2019-12-18 12:19 ` Paul Ruizendaal
2019-12-19 0:20 ` Paul Ruizendaal
2019-12-19 0:16 Norman Wilson
2019-12-19 0:26 ` Rob Pike
2019-12-19 3:47 ` Mike Haertel
2019-12-19 6:49 ` Angelo Papenhoff
2019-12-19 5:12 ` Dan Cross
2019-12-19 6:54 ` Rob Pike
2019-12-19 8:03 ` arnold
2019-12-19 15:32 ` Chet Ramey
2019-12-19 9:09 Paul Ruizendaal
2020-01-06 21:01 Norman Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d288dee4-6a0e-8c84-44e6-b0f6aa3afef4@e-bbes.com \
--to=emu@e-bbes.com \
--cc=pnr@planet.nl \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).