From: Toby Thain <toby@telegraphics.com.au>
To: Jason Stevens <jsteve@superglobalmegacorp.com>,
'Gregg Levine' <gregg.drwho8@gmail.com>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] 68k prototypes & microcode
Date: Sat, 13 Feb 2021 01:05:07 -0500 [thread overview]
Message-ID: <94b9ad5c-dd0b-9195-d391-787bafdf510f@telegraphics.com.au> (raw)
In-Reply-To: <0F0B9BFC06289346B88512B91E55670D300F@EXCHANGE>
On 2021-02-12 11:34 p.m., Jason Stevens wrote:
> Apparently they are getting 68040 levels of performance with a Pi... and
> that interpreted. Going with JIT it's way higher.
Before we get too breathless, this is roughly what was achieved with a
PowerPC 601 emulating 68K ...approximately 28 years ago.
--T
>
> -----Original Message-----
> From: Gregg Levine [SMTP:gregg.drwho8@gmail.com]
> Sent: Saturday, February 13, 2021 10:30 AM
> To: Jason Stevens; The Eunuchs Hysterical Society
> Subject: Re: [TUHS] 68k prototypes & microcode
>
> An amazing idea.
> -----
> Gregg C Levine gregg.drwho8@gmail.com
> "This signature fought the Time Wars, time and again."
>
> On Fri, Feb 12, 2021 at 7:51 PM Jason Stevens
> <jsteve@superglobalmegacorp.com> wrote:
> >
> > You might find this interesting
> >
> > https://twitter.com/i/status/1320767372853190659
> > <https://twitter.com/i/status/1320767372853190659>
> >
> > It's a pi (arm) running Musashi a 68000 core, but using voltage
> buffers it's
> > plugged into the 68000 socket of an Amiga!
> >
> > You can find more info on their github:
> >
> > https://github.com/captain-amygdala/pistorm
> > <https://github.com/captain-amygdala/pistorm>
> >
> > Maybe we are at the point where numerous cheap CPU's can eliminate
> FPGA's?
> >
> > -----Original Message-----
> > From: Michael Parson [SMTP:mparson@bl.org]
> > Sent: Friday, February 05, 2021 10:43 PM
> > To: The Eunuchs Hysterical Society
> > Subject: Re: [TUHS] 68k prototypes & microcode
> >
> > On 2021-02-04 16:47, Henry Bent wrote:
> > > On Thu, Feb 4, 2021, 17:40 Adam Thornton
> <athornton@gmail.com>
> > wrote:
> > >
> > >> I'm probably Stockholm Syndrommed about 6502. It's
> what I grew
> > up on,
> > >> and
> > >> I still like it a great deal. Admittedly
> register-starved (well,
> >
> > >> unless
> > >> you consider the zero page a whole page of registers),
> > but...simple,
> > >> easy
> > >> to fit in your head, kinda wonderful.
> > >>
> > >> I'd love a 64-bit 6502-alike (but I'd probably give it
> more than
> > three
> > >> registers). I mean given how little silicon (or how
> few FPGA
> > gates) a
> > >> reasonable version of that would take, might as well
> include
> > 65C02 and
> > >> 65816 cores in there too with some sort of
> mode-switching
> > instruction.
> > >> Wouldn't a 6502ish with 64-bit wordsize and a 64-bit
> address bus
> > be
> > >> fun?
> > >> Throw in an onboard MMU and FPU too, I suppose, and
> then you
> > could
> > >> have a
> > >> real system on it.
> > >>
> > >>
> > > Sounds like a perfect project for an FPGA. If there's
> already a
> > 6502
> > > implementation out there, converting to 64 bit should be
> fairly
> > easy.
> >
> > There are FPGA implementations of the 6502 out there. If
> you've not
> > seen
> > it, check out the MiSTer[0] project, FPGA implementations
> of a LOT
> > of
> > computers, going back as far as the EDSAC, PDP-1, a LOT of
> 8, 16,
> > and 32
> > bit systems from the 70s and 80s along with gaming
> consoles from the
> > 70s
> > and 80s.
> >
> > Keeping this semi-TUHS related, one guy[1] has even
> implemented a
> > Sparc 32m[2] (I think maybe an SS10), which boots SunOS 4,
> 5, Linux,
> > NetBSD, and even the Sparc version of NeXTSTEP, but it's
> not part of
> > the
> > "official" MiSTer bits (yet?).
> >
> > --
> > Michael Parson
> > Pflugerville, TX
> > KF5LGQ
> >
> > [0] https://github.com/MiSTer-devel/Main_MiSTer/wiki
> > [1] https://temlib.org/site/
> > [2] https://temlib.org/pub/mister/SS/
>
next prev parent reply other threads:[~2021-02-13 6:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 4:34 Jason Stevens
2021-02-13 6:05 ` Toby Thain [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-13 1:06 Jason Stevens
2021-02-13 2:30 ` Gregg Levine
2021-01-29 10:49 [TUHS] AT&T 3B1 - Emulation available Arnold Robbins
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
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
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=94b9ad5c-dd0b-9195-d391-787bafdf510f@telegraphics.com.au \
--to=toby@telegraphics.com.au \
--cc=gregg.drwho8@gmail.com \
--cc=jsteve@superglobalmegacorp.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).