From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] B Source Code
Date: Fri, 15 Sep 2017 11:21:02 -0400 (EDT) [thread overview]
Message-ID: <20170915152102.3B83018C0A3@mercury.lcs.mit.edu> (raw)
> From: Dave Horsfall
> Did anyone actually use the WCS?
Well, the uassembler was a product for a while, so they must have..
> I had visions of implementing CSAV and CRET on our -60, but never did
> get around to it.
I recently had the idea of programming them into an M792 ROM card (100nsec
access time); user programs couldn't have used it without burning a segment
(to map in the appropriate part of the I/O space), but it might have sped up
the kernel some (and it would have been trivial to add, once the card was
programmed - with a soldering iron - BTDT, BITD :-).
Haven't gotten to it yet - still looking for an M792 (I don't want to trash
any of my pre-programmed M792-xx's :-).
> From: Clem Cole <clemc at ccc.com>
> A big issue, again IIRC, was the microcode compiler/tools for the WSC
> ran on RSX so it meant UNIX was not running, which was not popular.
Why not just write a Unix-native one? They aren't that much work - I created a
uassembler overnight (literally!) for the QSIC project Dave Bridgham and I
have been working on.
It's been improved a lot since the first version (e.g. the entire uengine
description is now read in from a config file, instead of being compiled in),
but that first version did work fine...
Or was the output format not documented?
Noel
next reply other threads:[~2017-09-15 15:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 15:21 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-14 13:39 Noel Chiappa
2017-09-14 14:24 ` Dan Cross
2017-09-14 19:46 ` Derek Fawcus
2017-09-15 3:59 ` Dave Horsfall
2017-09-15 11:43 ` William Pechter
2017-09-19 1:20 ` Dave Horsfall
2017-09-15 12:44 ` Clem Cole
2017-09-15 13:03 ` Clem Cole
2017-09-14 3:48 Doug McIlroy
2017-09-14 4:49 ` Larry McVoy
2017-09-14 5:06 ` Lars Brinkhoff
2017-09-14 12:53 ` Ronald Natalie
2017-09-14 5:33 ` Alec Muffett
2017-09-14 5:44 ` Warner Losh
2017-09-12 18:03 Robert Swierczek
2017-09-12 18:14 ` Clem Cole
2017-09-12 19:24 ` Clem Cole
2017-09-12 19:43 ` Steve Johnson
2017-09-18 21:45 ` Angelo Papenhoff
2017-09-19 17:01 ` Thorsten Sideboard
2017-09-12 19:36 ` Charles Anthony
2017-09-12 20:39 ` Robert Swierczek
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=20170915152102.3B83018C0A3@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
/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).