From: cym224 at gmail.com (Nemo Nusquam)
Subject: [COFF] AT&T 3B1 - Emulation available
Date: Fri, 5 Feb 2021 12:41:09 -0500 [thread overview]
Message-ID: <8cf725f9-7f6c-1c3b-7212-a496692bc0ec@gmail.com> (raw)
In-Reply-To: <YB0HbaQezaZ8MiaR@server.rulingia.com>
On 02/05/21 03:53, Peter Jeremy via COFF wrote (in part):
> 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.
I know not how much of the embedded market used ColdFire but I recall a
lot of our embedded projects used ColdFire.
N.
next prev parent reply other threads:[~2021-02-05 17:41 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 ` [COFF] [TUHS] " peter
2021-02-05 17:41 ` cym224 [this message]
[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=8cf725f9-7f6c-1c3b-7212-a496692bc0ec@gmail.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).