From: lehmann@ans-netz.de (Oliver Lehmann)
Subject: [TUHS] System III - TCP/IP
Date: Mon, 09 Nov 2015 10:40:00 +0100 [thread overview]
Message-ID: <20151109104000.Horde.mZW7kq6nXQAQyqwKfyBtDlp@avocado.salatschuessel.net> (raw)
In-Reply-To: <20151109091646.Horde.WJOBgOU20u5J3ItIHNJDwO9@avocado.salatschuessel.net>
This is for example the ureg.c which shows the Segmentation Code for the
current SysIII Kernel I redid from original SysIII Sources + Disassembled
object-File analysis of the current SysIII Kernel running on the system:
http://cvs.laladev.org/index.html/P8000/WEGA/src/uts/sys/ureg.c?rev=1.1&content-type=text/x-cvsweb-markup
Oliver Lehmann <lehmann at ans-netz.de> wrote:
> I hit the send button to fast :(
>
> Oliver Lehmann <lehmann at ans-netz.de> wrote:
>
>> Nick Downing <downing.nick at gmail.com> wrote:
>>
>>> You can most likely implement a split I/D architecture by having code
>>> execute out of a different segment than data, although I haven't
>>> checked the datasheet so I don't know for sure if this is possible.
>>
>> I have 3 different MMUs available. Stack, Code and Data it is called in
>> the Circuit diagram. I probably have to lookup the references but I still
>> don't get why the kernel can only work with 64k of RAM as it is right now
>> compiled as a segmented programm and uses more memory already with SysIII.
>> Only the boot0-loader is compiled unsegmented and also some small
>> utilities. Every other portion of the system uses the segmentation features
>> of the Z8001 and is not limited to 64k adressable space.
>>
>> The system has right now MB of
>
> The system has right now around 6 MB of RAM but can be upgraded to 16MB
> minus 64KB (Due to a firmware bug) of RAM.
next prev parent reply other threads:[~2015-11-09 9:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 19:03 Oliver Lehmann
2015-11-07 19:20 ` Larry McVoy
2015-11-07 20:27 ` Cory Smelosky
2015-11-08 7:11 ` Larry McVoy
2015-11-08 7:22 ` John Cowan
2015-11-08 8:20 ` Cory Smelosky
2015-11-08 14:45 ` Dave Horsfall
2015-11-08 17:04 ` Steve Nickolas
2015-11-09 4:34 ` Larry McVoy
2015-11-07 21:28 ` Clem Cole
2015-11-07 22:07 ` Cory Smelosky
2015-11-07 22:13 ` Oliver Lehmann
2015-11-08 5:10 ` Derek Fawcus
2015-11-08 5:39 ` Nick Downing
2015-11-08 9:40 ` Oliver Lehmann
2015-11-08 13:38 ` Oliver Lehmann
2015-11-09 0:21 ` Nick Downing
2015-11-09 8:15 ` Oliver Lehmann
2015-11-09 8:16 ` Oliver Lehmann
2015-11-09 9:40 ` Oliver Lehmann [this message]
2015-11-09 9:40 ` Oliver Lehmann
2015-11-09 22:36 ` Nick Downing
2015-11-09 0:31 ` Nick Downing
2015-11-11 1:54 ` Cornelius Keck
2015-11-11 6:46 ` Oliver Lehmann
2015-11-08 15:52 Noel Chiappa
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=20151109104000.Horde.mZW7kq6nXQAQyqwKfyBtDlp@avocado.salatschuessel.net \
--to=lehmann@ans-netz.de \
/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).