From: "Frank Ch. Eigler" <fche@redhat.com>
To: sid@sources.redhat.com
Subject: new component: hw-visual-probe-pin
Date: Wed, 17 Jan 2001 10:18:00 -0000 [thread overview]
Message-ID: <20010117131817.C19160@redhat.com> (raw)
Hi -
A few hours' hacking resulted in another demonstration widget that aims
to show off the kinds of monitoring components that may be easily inserted
into a sid simulation. It's written in tcl/tk, and has a single input pin
on which it receives stimulus. One could configure it something like
this; though any old output pin that spits out a range of values might
be interesting.
new hw-visual-probe-pin boingo
connect-pin boingo stimulus <- cpu step-cycles
The component displays a window filled with roving icons. Each icon
represents a stimulus value (sid::pin::driven() argument) that has been
received. The icons move around the screen in relationship to how
frequently/intensely each particular value is received. It's sort of
a qualitative monitor, like lavaps and Mark Weiser's "Dangling String".
The top few icons (the ones moving fastest since they have been occurring
most frequently) are decorated with 100% genuine fuzzy dice.
By the way, this may make sid the first simulator in the world with
built-in fuzzy dice support. I attach a screenshot as proof.
- FChE
reply other threads:[~2001-01-17 10:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010117131817.C19160@redhat.com \
--to=fche@redhat.com \
--cc=sid@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).