public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: M.Fehr@brunel.de
Cc: sid@sources.redhat.com
Subject: Re: [newbie] Input to SID
Date: Wed, 22 Oct 2003 17:21:00 -0000	[thread overview]
Message-ID: <20031022172137.GC7332@redhat.com> (raw)
In-Reply-To: <OF5E845AF7.BC42A10A-ONC1256DC7.005AECBF@brunel.de>

[-- Attachment #1: Type: text/plain, Size: 1377 bytes --]

Hi -

On Wed, Oct 22, 2003 at 06:33:08PM +0200, M.Fehr@brunel.de wrote:
> [...]
> -how do you get input into the running application, from a parallel or
> serial port for example. 

If you are referring to the host hardware parallel or serial port,
to some extent this can be accomplished by something like the
sid-io-fileio or sid-io-stdio components.  One would tie the simulated
target UART to an instance of one of these host-side interfaces, and
configure the latter to talk to the host's /dev/ttyS1, or something
like that.  There are a few glitches like the new sid-io-fileio only
being capable of output at the moment (oops), but gazing over
sid/component/consoles, one sees that filling these gaps is not that
big a deal.


> I investigated the "system monitor" (tksm) and
> didn't manage to manipulate any value. 

You need to open a per-component view.  In that list, you'll see
all the avilable attributes.  The value fields are as editable
as the subject components let them.  Most pins are exposed as
attributes for purposes of just such interaction.

> Is it possible to write some user-interface in tcl/tk that somehow
> invokes commands on sid-components and simulates signals?

Absolutely.  See the hw-visual-tty for a two-way interactive one;
see hw-visual-clock, hw-visual-probe-pin (aka "fuzzy dice") components.


- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-10-22 17:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-22 16:30 M.Fehr
2003-10-22 17:21 ` Frank Ch. Eigler [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=20031022172137.GC7332@redhat.com \
    --to=fche@redhat.com \
    --cc=M.Fehr@brunel.de \
    --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).