The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] lost ports
Date: Wed, 4 Jan 2017 17:52:04 -0800	[thread overview]
Message-ID: <20170105015204.GA31939@mcvoy.com> (raw)
In-Reply-To: <20170104215839.GA6931@mcvoy.com>

On Wed, Jan 04, 2017 at 01:58:39PM -0800, Larry McVoy wrote:
> I worked on the ETA-10 (CDC spinoff, Neil Lincoln was the architect):
> 
> https://en.wikipedia.org/wiki/ETA10
> 
> No idea if the code is still around, I would guess it's lost.  Be fun
> if it showed up, I wrote a kmem "driver" so I could get my own version
> of ps(1) to run.  As I recall, it was an ioctl that just fed me back
> everything I needed, it wasn't a kmem driver at all, this was my first
> real job after grad school and I had no idea how to write a driver :)

I am apparently wrong, this has made be go through my notes.  I actually
wrote some drivers for the ETA project (I'm sure by copying other ones
and hacking them).

The ETA had local memory and then a big pool of shared memory but it 
was bcopy() shared.  I wrote the driver that let you access the shared
memory.

The proc/kmem thing was driven by the fact that nlist was slow.  So I
wrote a driver that gave you the process table.  Pretty simple.

There was something called an Ibis disk, I didn't do the controller
part, I did the Unix part that talked to the controller.  My notes say
"I wrote the Unix side of the driver which involved mapping the IOU into
shared memory.  Both interrupt and polled versions were used, currently
the polled is used due to interrupt problems with I/O channels."

All that said, I'm not a driver person, I suck at that.


  reply	other threads:[~2017-01-05  1:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 21:24 ron minnich
2017-01-04 21:41 ` Ron Natalie
2017-01-04 21:58 ` Larry McVoy
2017-01-05  1:52   ` Larry McVoy [this message]
2017-01-04 22:01 ` Robert Swierczek
2017-01-04 22:01 ` Dan Cross
2017-01-05 16:01 ` Clem Cole
2017-01-05 16:20   ` Clem Cole
2017-01-05 17:23   ` ron minnich
2017-01-05 19:08     ` Clem Cole
2017-01-05 19:16       ` ron minnich
2017-01-05 20:08         ` Clem Cole
     [not found]           ` <E3DA30C5-7227-4143-8DA1-401A161C74C6@gmail.com>
     [not found]             ` <CAP6exYLvXvtGEWSg_t5bqjJwunGKC1xiiaoLj7yb5QxkHsMvuA@mail.gmail.com>
2017-01-05 23:40               ` Lawrence Stewart
2017-01-05 16:15 ` Derek Fawcus
2017-01-05 18:34   ` Pierre DAVID
2017-01-05 12:28 Rudi Blom

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=20170105015204.GA31939@mcvoy.com \
    --to=lm@mcvoy.com \
    /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).