From: "Seth Morabito" <web@loomcom.com>
To: "UNIX Heritage Society" <tuhs@tuhs.org>
Subject: [TUHS] Re: SVR3 or SVR4 kernel sources for 3B2/700
Date: Sat, 30 Sep 2023 06:41:40 -0700 [thread overview]
Message-ID: <afe68221-1672-42b7-9cff-9ef097d97a5a@app.fastmail.com> (raw)
In-Reply-To: <CALQ0xCA7B47XMPcshio44C5ki0xaumw+r2xYjKTQBTg1eAVRxQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
On Fri, Sep 29, 2023, at 11:35 PM, Marc Donner wrote:
> I infer from your inquiry that there is no formal statement of the ISA for the machine. Is that correct?
The CPU itself is a standard off the shelf WE32200, which is thankfully very well documented, so the ISA is not really an issue. The real thorny question is how everything else is all hooked together. The interrupt controller, the IO buses, the DRAM controller, and so on, are partly documented in the technical reference manual, but only at a very high level, and with at least a few major inaccuracies. Detailed behavior like bus timeouts, error conditions, and so on, are very poorly documented. I was only able to infer how everything was connected on the 3B2/400 by reading the kernel source code to understand what the various drivers expected to see, but the 3B2/700 has a very different memory map and the kernel source code is missing. I have the system board schematics, but there an awful lot of PALs, and no PAL truth tables.
-Seth
--
Seth Morabito * Poulsbo, WA * https://loomcom.com/
[-- Attachment #2: Type: text/html, Size: 1720 bytes --]
prev parent reply other threads:[~2023-09-30 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 23:57 [TUHS] " Seth Morabito
2023-09-30 5:38 ` [TUHS] " Ben Huntsman
2023-09-30 6:35 ` Marc Donner
2023-09-30 13:41 ` Seth Morabito [this message]
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=afe68221-1672-42b7-9cff-9ef097d97a5a@app.fastmail.com \
--to=web@loomcom.com \
--cc=tuhs@tuhs.org \
/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).