From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] 68000 vs. 8086 ( was Algol68 vs. C at Bell Labs)
Date: Thu, 30 Jun 2016 21:59:29 +0200 [thread overview]
Message-ID: <57757a21.LPn+mSLKqXszpxKR%schily@schily.net> (raw)
In-Reply-To: <CAEoi9W6ugA9A9FR6yFEyL=fupTkRL2Xm3-kO3630NCpsigi=dQ@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
Dan Cross <crossd at gmail.com> wrote:
> Still, the point that the 68451 MMU was pretty lame is well taken. The
> segment table was too small (96 entries?) and it was clearly designed to
> support segmented memory rather than paging. It is inadequate to the latter
> task. The 68851 available for the 68020 got it right; supposedly this could
> be used with the 68010 as well, but I don't know that anyone ever tried
> that in a real product.
We at H.Berthold AG in Berlin did manage to use 12 68451 in parallel for our
virtual UNOS variant.
Jörg
--
EMail:joerg at schily.net (home) Jörg Schilling D-13353 Berlin
joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'
next prev parent reply other threads:[~2016-06-30 19:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 13:44 [TUHS] Algol68 vs. C at Bell Labs Noel Chiappa
2016-06-30 14:28 ` William Cheswick
2016-06-30 17:17 ` [TUHS] 68000 vs. 8086 ( was Algol68 vs. C at Bell Labs) scj
2016-06-30 17:27 ` Joerg Schilling
2016-06-30 18:52 ` Dan Cross
2016-06-30 19:59 ` Joerg Schilling [this message]
2016-06-30 20:06 ` Dan Cross
2016-06-30 20:27 ` Joerg Schilling
2016-06-30 19:23 ` [TUHS] Algol68 vs. C at Bell Labs John Cowan
2016-06-30 18:49 [TUHS] 68000 vs. 8086 ( was Algol68 vs. C at Bell Labs) Clem Cole
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=57757a21.LPn+mSLKqXszpxKR%schily@schily.net \
--to=schily@schily.net \
/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).