Computer Old Farts Forum
 help / color / mirror / Atom feed
From: peter at rulingia.com (Peter Jeremy)
Subject: [COFF] [TUHS] AT&T 3B1 - Emulation available
Date: Fri, 5 Feb 2021 19:53:01 +1100	[thread overview]
Message-ID: <YB0HbaQezaZ8MiaR@server.rulingia.com> (raw)
In-Reply-To: <CAC20D2M_33YdQyuHdb7EM-UVNcdM0TXz9eJXpTftHekWxK0=Dg@mail.gmail.com>

On 2021-Feb-03 09:58:37 -0500, Clem Cole <clemc at ccc.com> wrote:
>but the original released (distributed - MC68000) part was binned at 8 and
>10

There was also a 4MHz version.  I had one in my MEX68KECB but I'm not
sure if they were ever sold separately.  ISTR I got the impression
that it was a different (early) mask or microcode variant because some
of the interface timings weren't consistent with the 8/10 MHz versions
(something like one of the bus timings was a clock-cycle slower).

>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

I also really liked the M68k architecture.  Unfortunately, as with the
M6800, Motorola lost out to Intel's inferior excuse for an architecture.

Moving more off-topic, M68k got RISC-ified as the ColdFire MCF5206.
That seemed (to me) to combine the feel of the M68k with the
clock/power gains from RISC.  Unfortunately, it didn't take off.

-- 
Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20210205/d80c6490/attachment.sig>


       reply	other threads:[~2021-02-05  8:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1l5RL3-0002iv-Qv@tanda>
     [not found] ` <abf50209-5730-f5a0-0fd6-aec13ee68440@e-bbes.com>
     [not found]   ` <202102030759.1137x7C2013543@freefriends.org>
     [not found]     ` <CAHTagfHdykiYmqPCkhQkUQTU8fLqJBukPOyj-k1ef=Ur9rqH+Q@mail.gmail.com>
     [not found]       ` <202102030858.1138wuqd011051@freefriends.org>
     [not found]         ` <CAHTagfGOC7vgE2Os+kuP4oGzvot2kG3MERpQdLb2EoEhUoFpyg@mail.gmail.com>
     [not found]           ` <CAC20D2M_33YdQyuHdb7EM-UVNcdM0TXz9eJXpTftHekWxK0=Dg@mail.gmail.com>
2021-02-05  8:53             ` peter [this message]
2021-02-05 17:41               ` [COFF] " cym224
     [not found]             ` <27567.1612399305@hop.toad.com>
     [not found]               ` <bce2c77e-dd8d-a0f2-5b27-0f9239c76738@kilonet.net>
     [not found]                 ` <alpine.BSF.2.21.9999.2102041316080.70858@aneurin.horsfall.org>
     [not found]                   ` <4db6108e-73f0-6498-fe45-3fd422d1f389@kilonet.net>
     [not found]                     ` <alpine.BSF.2.21.9999.2102051312440.70858@aneurin.horsfall.org>
2021-02-05  2:53                       ` [COFF] [TUHS] 68k prototypes & microcode lm
     [not found]                 ` <20210204013356.GA16541@mcvoy.com>
2021-02-05  9:09                   ` peter
2021-02-05 14:36                   ` [COFF] Architectures -- was " clemc
2021-02-05 14:56                     ` [COFF] [SPAM] " lm
2021-02-05 18:31                       ` david
2021-02-05 22:02                       ` dave
2021-02-05 19:16                     ` [COFF] " athornton

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=YB0HbaQezaZ8MiaR@server.rulingia.com \
    --to=coff@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).