The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: downing.nick@gmail.com (Nick Downing)
Subject: [TUHS] System III - TCP/IP
Date: Mon, 9 Nov 2015 11:31:43 +1100	[thread overview]
Message-ID: <CAH1jEza76_XTKXQPjjDuXS9t=bNVZCZzMAWddMcy0gRkQF9DkQ@mail.gmail.com> (raw)
In-Reply-To: <20151108143817.Horde.tlWgdF0OWmzmg-kXXO-AxUO@avocado.salatschuessel.net>

By the way, there's no reason you can't use your existing Zilog
toolchain. You can just modify the makefiles that come with 2.11BSD to
run the Zilog tools. Or another option might be to write a compiler
driver that acts like "cc" and invokes the Zilog tools as
subprocesses, you have the source for 2.11BSD "cc" so this shouldn't
be too hard to do. Whatever naming convention the Zilog compiler uses,
you could rename the object files to ".o" and the 2.11BSD build system
would work largely unchanged. The most tricky part will be creating
the a.out executables, which are in the simplest case a header of
maybe 18 bytes (depends slightly on the magic number of the executable
since there were a few different compatible versions) followed by the
code and data segments followed by relocation records. To do this, I
am pretty sure I created my own linker, or modified the unix linker
(cannot remember exactly) in order to read the object files from the
IAR Z180 assembler (and I think these were in S-record format that you
mentioned) and create the a.out executables, I also had an extended
a.out format for the large multi-segment executables (including the
kernel), in which I arranged the code into 4 kbyte segments using a
first-fit algorithm. Again I'm happy to give you whatever I have on
this.
Nick


On Mon, Nov 9, 2015 at 12:38 AM, Oliver Lehmann <lehmann at ans-netz.de> wrote:
>
> Nick Downing <downing.nick at gmail.com> wrote:
>
>> I think you might get better mileage by just trying to port 2.11BSD over
>> to
>> your Z8001 device, since it is a self contained system, no interface
>> hacking will be needed, just porting.
>
>
> By the way - why do you think 2.11 BSD would be better to port instead of
> the
> original 4.3 BSD? The system has no 64KB addressing limitation. It can
> adress
> up to 128 64KB segments (=8MB). I mean, on a first look, it looks like
> 2.11BSD
> contains a lot more Assembler Code I would need to move to Z8001 ASM
> mnemonics
> as 4.3 does?!
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs



  parent reply	other threads:[~2015-11-09  0:31 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
2015-11-09  9:40                     ` Oliver Lehmann
2015-11-09 22:36                       ` Nick Downing
2015-11-09  0:31             ` Nick Downing [this message]
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='CAH1jEza76_XTKXQPjjDuXS9t=bNVZCZzMAWddMcy0gRkQF9DkQ@mail.gmail.com' \
    --to=downing.nick@gmail.com \
    /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).