From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-mips@linux-mips.org
Subject: Re: questions about making a script file for YAMON command
Date: Thu, 12 Feb 2004 15:08:21 +0100 [thread overview]
Message-ID: <20040212140821.GT2725@lug-owl.de> (raw)
In-Reply-To: <8EAC52A94CD8D411A01000805FBB377606563AE8@gbrwgcms02.wgc.gbr.xerox.com>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
On Thu, 2004-02-12 13:45:25 -0000, Ren, Manling <Manling.Ren@gbr.xerox.com>
wrote in message <8EAC52A94CD8D411A01000805FBB377606563AE8@gbrwgcms02.wgc.gbr.xerox.com>:
> Dear the technical support team,
No technical support team here, just a number of hackers...
> I am running YAMON on pb1100 board in Linux. At the YAMON prompt, I need to
> change some registers by using the command "edit -32 0x########" several
> times. I wonder if I can put all these "edit" commands into a script file
Personally, I don't know yamon since nobody offered a board using it to
me, but if it uses serial console, just prepare a text file containing
all the lines you need to type. Then, cut'n'paste the commands to
minicom or whatever you use...
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-12 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 13:45 questions about making a script file for YAMON command Ren, Manling
2004-02-12 14:08 ` Jan-Benedict Glaw [this message]
2004-02-12 14:20 ` Wolfgang Denk
2004-02-12 17:21 ` Goswin von Brederlow
-- strict thread matches above, loose matches on Subject: below --
2004-02-12 14:40 Berg, Christian
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=20040212140821.GT2725@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-mips@linux-mips.org \
/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