From: Steve Tell <tell@telltronics.org>
To: lewisbrown@acm.org
Cc: linux-serial@vger.kernel.org
Subject: RE: Best way to detect received call on dumb modem ...
Date: Tue, 4 Nov 2003 01:17:31 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.56.0311040106360.15984@ariel> (raw)
In-Reply-To: <000801c3a0f7$fbd98a10$0200000a@francois>
On Sat, 1 Nov 2003, Lewis Brown wrote:
> Sorry for not being more specific.
>
> I thought a 'dumb' modem was one that had been taken out of command mode
> and thus does not respond to AT commands; at least that's what I meant.
(That's what I thought too... or else a modem that never had an AT or any
other fancy command set to begin with)
Configure the modem to auto-answer when DTR is asserted and when when
phone rings, and to only assert CD (carrier detect) when it really has a
carrier.
Then call open(2) on the tty without O_NONBLOCK/O_NDELAY. DTR will get
asserted to enable the modem, and then the open(2) will block until the
modem answers and establishes a connection with the calling modem.
This is how modems and getty(8) worked on unixes 20+ years ago...
(well, except that the 1200bps modems modems were the fast ones)
Steve
> I should say that this is an old problem that I haven't worked on in
> over 9 months, so I've forgotten some of the details of my problem. I
> think that in dumb state, the modem can't send RING, CONNECT, etc., so
> one must detect DSR, DTR, RNG, etc. At least that's what I want to do.
>
> When I wrote this program the first time, it worked great and was really
> fast. Then I moved it to the real hardware, a DIGI RAS box, which
> didn't have all the standard IOCTLs. The program now requires the
> modems to be in command mode; I have to parse the stream for RING,
> CONNECT, OK, etc; and it is slow and very prone to error. Seems the
> modems are always going haywire this way. I want to go back to dumb
> mode and work as close as possible to the hardware. I need speed and
> reliability.
>
> Any suggestions are much appreciated.
> lb
>
> -----Original Message-----
> From: linux-serial-owner@vger.kernel.org
> [mailto:linux-serial-owner@vger.kernel.org] On Behalf Of Jan-Benedict
> Glaw
> Sent: Saturday, November 01, 2003 2:14 PM
> To: linux-serial@vger.kernel.org
> Subject: Re: Best way to detect received call on dumb modem ...
>
>
> On Sat, 2003-11-01 13:43:23 -0700, Lewis Brown <lewisb@denveronline.com>
> wrote in message <000001c3a0b8$ce82efa0$0200000a@francois>:
> > Hello,
> >
> > I'm trying to detect incoming calls on a dumb modem but dealing with a
> > driver that doesn't implement TIOCMIWAIT or TIOCGICOUNT. I'm puzzled
> how
> > best to go forward in an efficient way.
>
> select() on the fd and wait until you receive "RING"? However, what's a
> "dumb" modem?
>
> MfG, JBG
>
>
prev parent reply other threads:[~2003-11-04 6:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 20:54 [PATCH] Make the Startech UART detection 'more correct' Tom Rini
2003-09-09 16:18 ` Russell King
2003-09-09 19:12 ` Stuart MacDonald
2003-09-09 19:23 ` Tom Rini
2003-09-09 23:51 ` Tom Rini
2003-09-24 22:40 ` Kumar Gala
2003-11-01 20:43 ` Best way to detect received call on dumb modem Lewis Brown
2003-11-01 21:14 ` Jan-Benedict Glaw
2003-11-02 4:15 ` Lewis Brown
2003-11-02 8:28 ` David Lawyer
2003-11-04 6:17 ` Steve Tell [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=Pine.LNX.4.56.0311040106360.15984@ariel \
--to=tell@telltronics.org \
--cc=lewisbrown@acm.org \
--cc=linux-serial@vger.kernel.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