All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Timo Teräs" <ext-timo.teras@nokia.com>
To: linux-ppp@vger.kernel.org
Subject: Re: Detecting end of GSM datacall
Date: Wed, 20 Apr 2005 11:11:33 +0000	[thread overview]
Message-ID: <426638E5.3070902@nokia.com> (raw)
In-Reply-To: <426384B8.6050809@nokia.com>

ext James Carlson wrote:
> Timo Teräs writes:
>>I tracked down the reason: since the PPP link is between PC and remote 
>>computer, the mobile phone does not send any PPP packets that the link 
>>is dead. Instead it just sends '\r\nNO CARRIER\r\n'. And leaves the 
>>Bluetooth connection in AT command mode. Thus PPP stays happily up.
> 
> Why doesn't it de-assert DCD (Data Carrier Detect) and thus cause pppd
> to receive SIGHUP as expected?
> 
> In my opinion, we shouldn't really go too far out of our way to make
> fatally compromised interfaces work "right."

Actually this is a very good question. I now finally solved this bug. It 
appears that BlueZ correctly translates/transports the carrier detect 
signal from my mobile. However it does not call tty_hangup() when the 
carrier detect is de-asserted. I managed to get this working perfectly 
well by adding one if () and tty_hangup() call to 
net/bluetooth/rfcomm/tty.c.

So this is actually a BlueZ emulation bug. I'll post bug report / simple 
patch to appropriate list asap.

Thanks,
   Timo

      parent reply	other threads:[~2005-04-20 11:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-18  9:58 Detecting end of GSM datacall Timo Teräs
2005-04-18 13:25 ` Steve Drew
2005-04-18 13:34 ` Timo Teräs
2005-04-18 14:38 ` Jar
2005-04-18 21:19 ` Clifford Kite
2005-04-18 21:40 ` Herbert Xu
2005-04-19 14:37 ` Clifford Kite
2005-04-20  0:28 ` Paul Mackerras
2005-04-20 11:11 ` Timo Teräs [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=426638E5.3070902@nokia.com \
    --to=ext-timo.teras@nokia.com \
    --cc=linux-ppp@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.