The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Ruizendaal <pnr@planet.nl>
To: emanuel stiebler <emu@e-bbes.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Blit source
Date: Thu, 19 Dec 2019 01:20:18 +0100	[thread overview]
Message-ID: <744AB73C-9970-450E-8B1A-5BACF9FE3E11@planet.nl> (raw)
In-Reply-To: <6be1d013-2323-9850-03fd-c4014c4a69e7@e-bbes.com>

[-- Attachment #1: Type: text/plain, Size: 3017 bytes --]


> On Dec 16, 2019, at 7:25 AM, emanuel stiebler <emu@e-bbes.com> wrote:
> 
> On 2019-12-15 21:45, Paul Ruizendaal wrote:
>> I’m looking for source code of the original Blit as described here:
>> http://doc.cat-v.org/bell_labs/blit/blit.pdf
> 
> Thanks for trying again. It pops up on this list every few years, but
> still no schematics (2002, 2012) ...
> 
> Cheers

Have you seen the 5620 schematics on bitsavers?

http://bitsavers.org/pdf/att/5620/schematic/5620_logic.pdf <http://bitsavers.org/pdf/att/5620/schematic/5620_logic.pdf>

Of course it is not the Blit schematics, but it looks like a close derivative. When comparing the Hardware & Software Tradeoffs paper with the schematics and the theory of operation notes at the back, it would seem to me that much of it is (near) identical to the 68K Blit.

- The video timing circuit was probably identical (also see the figures at the back with exact timing specifications).
- The memory grid was probably (near) identical - maybe changed slightly for the option to use 256Kx1 drams.
- The arbitration circuit may have been redesigned, but it looks like the bus arbitration of the M68K was not all that different from the Bellmac. A memory cycle takes 11 ticks of the 32.7 MHz pixel clock, or about 335ns. This is consistent with the numbers mentioned in the Blit papers (e.g. the display using about 30% of memory bandwidth, etc.).
- The mouse movement circuit appears unchanged from the Blit paper, with a two-phase motion signal counted for the first 4 bits in a PAL and the rest in a TTL counter

Some things are of course different (beyond the different CPU). The 5620 has an I/O expansion port and a bit of non-volatile memory, neither of which is mentioned in the Blit papers. The memory map is totally different and the protection for null pointer dereference appears gone.

The 2x 6850 UART appears to be replaced by a single 2681 programmable DUART. The button signals are routed through the additional parallel I/O bits that this chip provides, which also takes care of interrupt generation. According to the Blit papers there were several other versions of the Blit before the final design was arrived upon. Maybe earlier designs used a 2681 DUART as well, or its close cousin SCN68681. Maybe the earlier version of button.c could work with both. If this is true, it would stand to reason that the various features of the 2681/68681 were replicated with the two 6850’s and some supporting circuitry. This hypothesis seems to fit with some of aiju’s observations in the “mmap” information file included with the Blit emulator (e.g. accessing register 25 and 27, the timer/counter and its use for sound generation).

The Blit promotional video that AT&T put on youtube in 2012 has a brief shot (at 0:45) of the logic board. This appears to show two 24 pin packages in the bottom center of the board, which are in all likelihood the 6850’s. There is no 40 pin package (i.e. no 2681/68681 chip) on that board.


[-- Attachment #2: Type: text/html, Size: 4055 bytes --]

  parent reply	other threads:[~2019-12-19  0:20 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
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 [this message]
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=744AB73C-9970-450E-8B1A-5BACF9FE3E11@planet.nl \
    --to=pnr@planet.nl \
    --cc=emu@e-bbes.com \
    --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).