From mboxrd@z Thu Jan 1 00:00:00 1970 From: lehmann@ans-netz.de (Oliver Lehmann) Date: Mon, 09 Nov 2015 09:15:51 +0100 Subject: [TUHS] System III - TCP/IP In-Reply-To: References: <20151107200358.Horde.M1lYZZyTC4t0Qb8KrygKzhy@avocado.salatschuessel.net> <20151107192043.GA11895@mcvoy.com> <20151107231338.Horde.d8EIgIMMf9VYCExfovc2K_M@avocado.salatschuessel.net> <20151108051028.GA32246@cowbell.employees.org> <20151108143817.Horde.tlWgdF0OWmzmg-kXXO-AxUO@avocado.salatschuessel.net> Message-ID: <20151109091551.Horde.vyfPFb7gspsxIQB3WGNcE_A@avocado.salatschuessel.net> Nick Downing 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