The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: emanuel stiebler <emu@e-bbes.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Pdp11 implementations on fpga in 2018
Date: Wed, 26 Dec 2018 10:04:10 -0600	[thread overview]
Message-ID: <8B9AF6DF-94D1-4278-B734-B926302D11D2@gmail.com> (raw)
In-Reply-To: <77412cac-ff78-0b16-0f21-e72e2fa77bea@e-bbes.com>



Sent from my iPhone

> On Dec 26, 2018, at 7:43 AM, emanuel stiebler <emu@e-bbes.com> wrote:
> 
>> On 2018-12-23 13:17, Will Senn wrote:
>> Hi folks,
>> 
>> This is a little sideways from on topic, but no too far. Is there a good open source implementation of a pdp11 for fpga in verilog/vhdl that works well for Unix v6+? Google turns up a number, but I’m hoping some of y’all have actual experience with one that you could recommend over others. I’m financially challenged so it’s a requirement that it run on cheap fpga’s not some Tesla prototype :)
> 
> I know of two:
> 
> https://opencores.org/projects/w11
> 
> and
> 
> http://pdp2011.sytse.net/wordpress/pdp-11/
> 
> 
> Both projects are so old, they should run on FPGA boards you probably
> could get for free ...
> 
> Have fun!

I need to find those free boards :). Those are the best sites, I’ve seen, too. I’m not entirely sure why I’m wanting to do the fpga thing when simh seems to work just fine for everything I’ve ever wanted to use it for, but having a switch controlled machine that can be put on a shelf and taken off and plugged in and run is appealing. Not quite as appealing as having a PiDP-11, but for those of us on a budget, it seems right somehow!

Will

      reply	other threads:[~2018-12-26 16:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-23 18:17 Will Senn
2018-12-26 13:43 ` emanuel stiebler
2018-12-26 16:04   ` Will Senn [this message]

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=8B9AF6DF-94D1-4278-B734-B926302D11D2@gmail.com \
    --to=will.senn@gmail.com \
    --cc=emu@e-bbes.com \
    --cc=tuhs@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).