All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-serial@vger.kernel.org
Subject: Re: Best way to detect received call on dumb modem ...
Date: Sat, 1 Nov 2003 22:14:03 +0100	[thread overview]
Message-ID: <20031101211402.GV31376@lug-owl.de> (raw)
In-Reply-To: <000001c3a0b8$ce82efa0$0200000a@francois>

[-- Attachment #1: Type: text/plain, Size: 753 bytes --]

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

-- 
   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 --]

  reply	other threads:[~2003-11-01 21:14 UTC|newest]

Thread overview: 13+ 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: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-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 [this message]
2003-11-02  4:15         ` Lewis Brown
2003-11-02  8:28           ` David Lawyer
2003-11-04  6:17           ` Steve Tell

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=20031101211402.GV31376@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.