From: Andrey Vihrov <andrey.vihrov@gmail.com>
To: Gianluca Anzolin <gianluca@sottospazio.it>
Cc: peter@hurleysoftware.com, marcel@holtmann.org,
gregkh@linuxfoundation.org, jslaby@suse.cz,
linux-bluetooth@vger.kernel.org
Subject: Re: A problem with "rfcomm bind" and wvdial
Date: Mon, 06 Jan 2014 18:06:45 +0200 [thread overview]
Message-ID: <1389024405.2739.2.camel@tenshi> (raw)
In-Reply-To: <20140106113353.GA21381@sottospazio.it>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
Hello,
Thanks for the update. I applied the patch to the bluetooth-next
kernel and it seems to work as expected. I ran wvdial several times in a
row, and it was able to connect every time.
> On Sun, Jan 05, 2014 at 04:49:42PM +0100, Gianluca Anzolin wrote:
> > Hello,
> >
> > I looked at your problem this afternoon and I think I know what's happening:
> > wvdial is opening the port with the flag O_NONBLOCK. As expected the rfcomm
> > code returns immediately instead of waiting for the BT connection to come
> > up. Then wvdial sends the AT commands and the writes fail.
>
> Hi,
>
> could you please test the attached patch?
>
> If it works and people are ok with it I'll submit it along with the other fixes
> I already sent to the list.
>
> Thank you,
> Gianluca
--
Andrey Vihrov <andrey.vihrov@gmail.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-01-06 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 15:49 A problem with "rfcomm bind" and wvdial Gianluca Anzolin
2014-01-06 11:33 ` Gianluca Anzolin
2014-01-06 16:06 ` Andrey Vihrov [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-03 18:24 Andrey Vihrov
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=1389024405.2739.2.camel@tenshi \
--to=andrey.vihrov@gmail.com \
--cc=gianluca@sottospazio.it \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=peter@hurleysoftware.com \
/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