Re: Accessing the C64 memory between 65xx chips operations.

From: Justin Cordesman <shadow_at_darksideresearch.com>
Date: Sun, 19 Apr 2020 13:46:34 -0700
I like this reinvention of Infiniband for the 6502. With 1024 of them it would only be 14x slower than the Princeton Engine I used to code for.

Justin

> On Apr 19, 2020, at 12:51, "groepaz_at_gmx.net" <groepaz_at_gmx.net> wrote:
> 
> Am Sonntag, 19. April 2020, 19:37:53 CEST schrieb Gerrit Heitsch:
> 
>> So you see, there is not enough free time to add an additional RAM access.
> 
> to come back to the original idea - if i'd wanted to do an actual
> "multiprocessor" system on/for the C64 - i'd do what "the final chesscard"
> did: a seperate CPU with its own RAM, and a shared dualport ram that both CPUs
> can access. that will give you much better performance (and requires much less
> hardware redesign)
> 
> --
> 
> http://hitmen.eu                 http://ar.pokefinder.org

> http://vice-emu.sourceforge.net  http://magicdisk.untergrund.net

> 
> Some electronic components are now so small that more time is spent looking
> for them than using them.
> <Arthur C. Clarke>
> 
> 
> 
> 
> 

--=_GybDD3W7NS9vTZclyS80KqEk2C02fn3G9AapvToBWJiBmqlm
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="Zarafa HTML builder 1.0">
<TITLE></TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT STYLE="font-family: courier" SIZE=2>
I like this reinvention of Infiniband for the 6502. With 1024 of them it would only be 14x slower than the Princeton Engine I used to code for.<br>
<br>
Justin<br>
<br>
&gt; On Apr 19, 2020, at 12:51, &quot;groepaz_at_gmx.net&quot; &lt;groepaz_at_gmx.net&gt; wrote:<br>
&gt; <br>
&gt; Am Sonntag, 19. April 2020, 19:37:53 CEST schrieb Gerrit Heitsch:<br>
&gt; <br>
&gt;&gt; So you see, there is not enough free time to add an additional RAM access.<br>
&gt; <br>
&gt; to come back to the original idea - if i'd wanted to do an actual<br>
&gt; &quot;multiprocessor&quot; system on/for the C64 - i'd do what &quot;the final chesscard&quot;<br>
&gt; did: a seperate CPU with its own RAM, and a shared dualport ram that both CPUs<br>
&gt; can access. that will give you much better performance (and requires much less<br>
&gt; hardware redesign)<br>
&gt; <br>
&gt; --<br>
&gt; <br>
&gt; http://hitmen.eu&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; http://ar.pokefinder.org<br>
&gt; http://vice-emu.sourceforge.net&nbsp; http://magicdisk.untergrund.net<br>
&gt; <br>
&gt; Some electronic components are now so small that more time is spent looking<br>
&gt; for them than using them.<br>
&gt; &lt;Arthur C. Clarke&gt;<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
</FONT>
</P>

</BODY></HTML>
--=_GybDD3W7NS9vTZclyS80KqEk2C02fn3G9AapvToBWJiBmqlm--
Received on 2020-05-30 01:31:55

Archive generated by hypermail 2.3.0.