9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: ? Plan 9 for Sun 3/80 ?
Date: Tue,  5 Sep 1995 07:23:54 -0400	[thread overview]
Message-ID: <19950905112354.JnLIC1ZkboPz0Q_wrkADJddCjvBxOaM0iyxvgL1Xyqo@z> (raw)

>>Is there a 68030 version of Plan 9 anywhere? Perhaps for some of

a student here (davesc) started with my sun3 port and the existing next 68040 port, and
attempted a port to the 3/80.  in a few weeks he got a very long way
before he ran out of time (the machine had to go back to its owners).
amongst other things, he made the required changes to 2a and 2l
to support the 68030 instructions and registers required for the mmu.
the kernel booted, started /boot, but there was some problem with
the Lance (ethernet).

i used that as a basis for a working port to an Eltec 68030 VME crate.
in the process, i discovered a few small errors in the sun3x code
that might have caused the Lance to fail (but that failure might have been
unrelated).

i recently made the 68030 changes to 2a etc for the new release, but i haven't
made the small changes to the Eltec kernel required for the new release.
once i've done that, in the next few days, i'll know that things are
working as well as they ever were, and i can make the 2a/2l changes,
the 68030 kernel changes, and the basic sun3x (sun 3/80) package available
to anyone with a licence who wants them.  they might be useful
as part of a port to a 68030 NeXt machine, for instance.
they might also be useful if you've got a similar VME crate.
we used it as part of a student project to drive a robot.
i'll probably put the bits out for anon. ftp in some suitable form,
rather than dole them out on demand.






             reply	other threads:[~1995-09-05 11:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-09-05 11:23 forsyth [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-09-04  7:09 sharris

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=19950905112354.JnLIC1ZkboPz0Q_wrkADJddCjvBxOaM0iyxvgL1Xyqo@z \
    --to=forsyth@plan9.cs.york.ac.uk \
    /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).