From: "rick.liu" <dovi@eyou.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: kermit:How to disable the flow control signals?
Date: 17 May 2003 18:45:49 +0800 [thread overview]
Message-ID: <20030517184549.35030.qmail@eyou.com> (raw)
Dear Wolfgang,
thank you for ur reply,in your message,
======= 2003-05-17 09:29:00 you wrote:=======
>> 1.why the flow control signals are still "on"?
>
>Because this is what you serial driver reports about the current
>state of these pins?
i donnot think so,for example,my NO.7 pin(RTS) and NO.9 pin(RI) both connect
to nothing,if your conclusion is correct,RTS and RI should be the same
state.But we
saw they are not the same.
>To verify, type "show comm" at the kermit prompt:
here is my info:
kermit>show comm
Communications Parameters:
Line: /dev/ttyS0, speed: 115200, mode: local, modem: none
Parity: none, stop-bits: (default) (8N1)
Duplex: full, flow: none, handshake: none
Carrier-watch: off, close-on-disconnect: off
Lockfile: /var/lock/LCK..ttyS0
Terminal bytesize: 8, escape character: 28 (^\)
Carrier Detect (CD): On
Dataset Ready (DSR): On
Clear To Send (CTS): On
Ring Indicator (RI): Off
Data Terminal Ready (DTR): On
Request To Send (RTS): On
Type SHOW DIAL to see DIAL-related items.
Type SHOW MODEM to see modem-related items.
Now we can still see the RTS/CTS/DSR/CD/DTR are still on,why?
it my kermit version's problem?
Best regards,
Rick
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-05-17 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-17 10:45 rick.liu [this message]
2003-05-17 17:07 ` kermit:How to disable the flow control signals? Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2003-05-18 4:59 rick.liu
2003-05-18 10:21 ` Wolfgang Denk
2003-05-17 5:18 rick.liu
2003-05-17 7:29 ` Wolfgang Denk
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=20030517184549.35030.qmail@eyou.com \
--to=dovi@eyou.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).