From: Dan Malek <dan@embeddededge.com>
To: THEDREAM@chollian.net
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: implement modem control for the 860 SMC
Date: Fri, 16 Nov 2001 00:57:17 -0500 [thread overview]
Message-ID: <3BF4AABD.8050808@embeddededge.com> (raw)
In-Reply-To: 200111160538.OAA03649@ldap.dacom.co.kr
THEDREAM@chollian.net wrote:
> Hi, everybody ~~!!!
>
> I want to implement modem control using 860 SMC. (NOT SCC)
What kind of modem control? If you want to do flow control based
upon the hardware signals, I wouldn't even attempt it. It would
have to be implemented in software, you would have to respond to
interrupts generated by signal changes, and you couldn't use any
of the CPM buffering capability. I don't think you could respond
fast enough to the RTS/CTS changes.
If all you want are things like carrier and DTR sensing, just connect
some GPIO pins and have a good time :-).
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-11-16 5:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 5:41 implement modem control for the 860 SMC THEDREAM
2001-11-16 5:57 ` Dan Malek [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=3BF4AABD.8050808@embeddededge.com \
--to=dan@embeddededge.com \
--cc=THEDREAM@chollian.net \
--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).