The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Chris Hanson <cmhanson@eschatologist.net>
To: tuhs@tuhs.org
Subject: [TUHS] Historical sources for 68010 + 68451 systems?
Date: Tue, 15 Sep 2020 16:28:36 -0700	[thread overview]
Message-ID: <DFA6E8C5-FA9A-42AA-B46C-289E373E053A@eschatologist.net> (raw)

I have an MVME121 that I’d like to run some stuff on. I’m planning what I’ll need to do to port MINIX 1.5 but since this has a 68451 segmented MMU, I’d like to actually make use of it.

Have any historical sources been published for UNIX on the various 68010 + 68451 systems from the early-mid 1980s? I’m curious how they used segmented MMUs.

I figure at minimum I could have several segments set up to enforce protections and a stable per-process address space, but it’d be good to have an example.

  — Chris


             reply	other threads:[~2020-09-15 23:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 23:28 Chris Hanson [this message]
2020-09-15 23:55 ` Gregg Levine
2020-09-16  3:05   ` Chris Hanson
2020-09-16  5:21 ` Arno Griffioen
2020-09-16  8:53 ` Al Kossow
2020-09-16 23:47   ` Dave Horsfall
2020-09-16 19:53 Nelson H. F. Beebe

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=DFA6E8C5-FA9A-42AA-B46C-289E373E053A@eschatologist.net \
    --to=cmhanson@eschatologist.net \
    --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).