From: "Frank Ch. Eigler" <fche@redhat.com>
To: Tarun Siripurapu <starunj@gmail.com>
Cc: sid@sources.redhat.com
Subject: Re: hw-visual-tty
Date: Sun, 14 Nov 2004 18:00:00 -0000 [thread overview]
Message-ID: <20041114180018.GJ26215@redhat.com> (raw)
In-Reply-To: <c36e089004111409183a4ff1a5@mail.gmail.com>
Hi -
On Sun, Nov 14, 2004 at 12:18:30PM -0500, Tarun Siripurapu wrote:
> [...]
> To run SID and show the 'hw-uart-ns16550 uart1' tty window, this is
> what I'm currently doing:
> $ arm-elf-sid --board=pid7t-normalmap --gdb=2000 -EL --tksm &
> [...]
Sounds good.
> Is there a way to do it with out having to open the System Monitor and
> click these every time?
Certainly. In the sid framework, a gui frontend component can be
configured into the simulation just as easily as any hardware
model - even easier perhaps. The GUI component convention consists
of only a few additional bits of sid configuration:
# ... other configuration
new hw-uart-ns16550 uart
# ...
new hw-visual-tk widget
relate widget "hw-uart-ns16550 uart" uart
The key of course is the last "relate" command. For GUI connections,
the "relationship name" is a two-part string, the first of which
identifies the component type of the target hardware model. (This
way the GUI can adapt itself to several virtual hardware variants.)
The second component appears to be just some identifying text used
in the title bar of the GUI component, in order to tell the user
which hardware module is being observed.
So all you need to do is to append those two lines of configuration
to your sid run, perhaps using two "-e '......'" options, or else
generating and editing a configuration file.
- FChE
next prev parent reply other threads:[~2004-11-14 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-14 17:18 hw-visual-tty Tarun Siripurapu
2004-11-14 18:00 ` Frank Ch. Eigler [this message]
[not found] ` <c36e089004111417255552f041@mail.gmail.com>
2004-11-15 1:31 ` hw-visual-tty Frank Ch. Eigler
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=20041114180018.GJ26215@redhat.com \
--to=fche@redhat.com \
--cc=sid@sources.redhat.com \
--cc=starunj@gmail.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).