From: Henry Gomersall <whg21@cam.ac.uk>
To: linux-bluetooth@vger.kernel.org
Subject: Re: bluetooth SPP link to Nokia phone
Date: Wed, 22 Jul 2009 12:14:57 +0100 [thread overview]
Message-ID: <1248261297.5156.23.camel@whg21-laptop> (raw)
In-Reply-To: <1248177100.5156.14.camel@whg21-laptop>
On Tue, 2009-07-21 at 12:51 +0100, Henry Gomersall wrote:
> I've tried doing the same thing using the rfcomm program. This allows
> me
> to set up a stable connection using:
> rfcomm connect /dev/rfcomm0 'XX:XX:XX:XX:XX:XX'
I've done a little more investigation.
(please correct me if I am wrong) The rfcomm app speaks directly to the
kernel bluetooth interface. It works fine.
The sample test-serial program works through the dbus interface to the
bluetooth daemon and has exactly the same problem as my test program -
namely the serial link is dropped as soon as I attempt to write data to
it.
The problem I have is the large overhead to understanding the source
tree, with the wiki being pretty out of date. I'm keen to sort this
problem.
Cheers,
Henry
prev parent reply other threads:[~2009-07-22 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 9:45 bluetooth SPP link to Nokia phone Henry Gomersall
2009-07-21 10:02 ` Johan Hedberg
2009-07-21 11:51 ` Henry Gomersall
2009-07-22 11:14 ` Henry Gomersall [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=1248261297.5156.23.camel@whg21-laptop \
--to=whg21@cam.ac.uk \
--cc=heng@cantab.net \
--cc=linux-bluetooth@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