From: Clem Cole <clemc@ccc.com>
To: Ed Bradford <egbegb2@gmail.com>
Cc: UNIX Heritage Society <tuhs@tuhs.org>
Subject: Re: [TUHS] AT&T 3B1 - Emulation available
Date: Wed, 3 Feb 2021 09:58:37 -0500 [thread overview]
Message-ID: <CAC20D2M_33YdQyuHdb7EM-UVNcdM0TXz9eJXpTftHekWxK0=Dg@mail.gmail.com> (raw)
In-Reply-To: <CAHTagfGOC7vgE2Os+kuP4oGzvot2kG3MERpQdLb2EoEhUoFpyg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
On Wed, Feb 3, 2021 at 5:14 AM Ed Bradford <egbegb2@gmail.com> wrote:
> Hay, Arnold,
>
> MC 68K was created in 1980 or thereabouts. We talked about 10's of
> Megahertz, I think, in those times.
>
The original X series part was originally unnumbered but a sticker was
later set for the lids that said X68000 (I had one on my desk - which was
used for the Tektronix Magnolia prototype).[1] The X series ran at 8 Mhz,
but the original released (distributed - MC68000) part was binned at 8 and
10 as were the later versions with the updated paging microcode called the
MC68010 a year later. When the 68020 was released Moto got the speeds up
to 16Mhz and later 20. By the '040 I think they were running at 50MHz
[1] I think I still have the draft list of issues in my files. There was a
halt and catch fire style error you had to be careful about (I've forgotten
the details - but if you executed it in supervisor mode, the ucode turned
on the address drivers in such a manner that they stopped working after
that and the chip was ruined). I only did that once ;-) when we were
debugging Magix (the OS for Magnolia)
[-- Attachment #2: Type: text/html, Size: 2138 bytes --]
next prev parent reply other threads:[~2021-02-03 14:59 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 10:49 Arnold Robbins
2021-01-29 13:49 ` Ronald Natalie
2021-01-29 14:37 ` Clem Cole
2021-01-31 7:57 ` arnold
2021-01-31 8:41 ` Rich Morin
2021-02-03 7:53 ` emanuel stiebler
2021-02-03 7:59 ` arnold
2021-02-03 8:53 ` Ed Bradford
2021-02-03 8:58 ` arnold
2021-02-03 10:13 ` Ed Bradford
2021-02-03 14:58 ` Clem Cole [this message]
2021-02-03 15:33 ` Henry Bent
2021-02-03 16:53 ` Clem Cole
2021-02-04 0:41 ` [TUHS] 68k prototypes & microcode John Gilmore
2021-02-04 0:52 ` Al Kossow
2021-02-04 1:10 ` Arthur Krewat
2021-02-04 1:33 ` Larry McVoy
2021-02-04 1:47 ` Al Kossow
2021-02-04 1:57 ` Al Kossow
2021-02-04 7:23 ` Arno Griffioen
2021-02-04 11:28 ` Toby Thain
2021-02-04 15:47 ` Arthur Krewat
2021-02-04 16:03 ` emanuel stiebler
2021-02-04 21:55 ` Dave Horsfall
2021-02-04 22:11 ` Steve Nickolas
2021-02-04 22:39 ` Adam Thornton
2021-02-04 22:47 ` Henry Bent
2021-02-05 14:42 ` Michael Parson
2021-02-04 22:56 ` Richard Salz
2021-02-04 23:14 ` Steve Nickolas
2021-02-04 1:35 ` Clem Cole
2021-02-04 2:18 ` Dave Horsfall
2021-02-04 15:53 ` Arthur Krewat
2021-02-05 2:16 ` Dave Horsfall
2021-02-05 2:53 ` Larry McVoy
2021-02-04 1:14 ` Clem Cole
2021-02-04 1:20 ` Clem Cole
2021-02-04 14:56 ` John Cowan
2021-02-03 15:20 ` [TUHS] AT&T 3B1 - Emulation available emanuel stiebler
2021-02-03 16:48 ` Doug McIntyre
2021-02-03 10:46 ` emanuel stiebler
2021-02-03 11:13 ` arnold
2021-02-05 12:44 ` Sergio Pedraja
2021-02-07 7:32 ` arnold
2021-02-17 16:07 ` emanuel stiebler
2021-02-17 22:00 ` Ed Carp
2021-02-17 22:14 ` Larry McVoy
2021-02-18 1:30 ` Ed Carp
2021-02-18 7:59 ` arnold
2021-02-18 18:07 ` Brad Spencer
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='CAC20D2M_33YdQyuHdb7EM-UVNcdM0TXz9eJXpTftHekWxK0=Dg@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=egbegb2@gmail.com \
--cc=tuhs@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).