From: johnh@psych.usyd.edu.au (John Holden)
Subject: [pups] thrust meter?
Date: Wed, 11 Oct 2006 08:20:04 +1000 [thread overview]
Message-ID: <47CD212B-FA24-40F9-85D3-0CF325462CC8@psych.usyd.edu.au> (raw)
In-Reply-To: <Pine.BSI.4.61.0610102057430.8153@dave.horsfall.org>
On 10/10/2006, at 9:00 PM, Dave Horsfall wrote:
> On Tue, 10 Oct 2006, Johnny Billquist wrote:
>
>> Hmm, but yeah. Since the bus might be idle even though the CPU is
>> running, you might not get a very good reading by looking at the
>> unibus.
>> But I think there are other signals that would be better to integrate
>> over. Such as the MASTER lamp (or is it the CPU lamp perhaps?) of the
>> front panel.
>
The MASTER lamp signifies that the CPU has the unibus, hence a
similar problem
to using BUS BUSY. You could use KERNEL/SUPERVISOR/USER signals as an
indication
of context switches. My favourite is a light chaser using the data
display from
the idle loop. Only works on an 11/45/50/55/60/70 (a bit boring on a
11/60 as
it had a 7 segment display).
> Which reminds me; try holding the light-pen of a GT40 against its own
> console lights :-)
>
Got one in my office. The lightpen latches the current x/y
coordinates from
the d/a converters. Aim it at something that will trigger it and you
get random
hits all over the screen
next prev parent reply other threads:[~2006-10-10 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 4:17 Brian Knittel
2006-10-05 12:15 ` Dave Horsfall
2006-10-09 23:02 ` John Holden
2006-10-10 9:05 ` Johnny Billquist
2006-10-10 11:00 ` Dave Horsfall
2006-10-10 22:20 ` John Holden [this message]
2006-10-10 10:55 ` Dave Horsfall
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=47CD212B-FA24-40F9-85D3-0CF325462CC8@psych.usyd.edu.au \
--to=johnh@psych.usyd.edu.au \
/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).