From: "Donnie Smith" <cwiid@abstrakraft.org>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Error connecting after inquiry
Date: Wed, 11 Apr 2007 23:05:40 -0400 [thread overview]
Message-ID: <1d49725d0704112005q6b90105dtc9e2e6affc647f63@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1505 bytes --]
Hello,
I am developing an application that connects to the Nintendo Wii remote,
which is a bluetooth device, using BlueZ. The API allows a bdaddr to be
supplied, or not. If it is not supplied, the API invokes a search function
that does an hci_inquiry to get all available devices, hci_open_dev to get a
device connection, then traverses the array, calling hci_remote_name and
checking the class for each item returned from hci_inquiry until a Wiimote
is found, closes the hci device, and returns the bdaddr of the Wiimote. The
calling function then opens a couple of L2CAP sockets and proceeds to
communicate with the device.
Here's my problem: many users receive errors on the L2CAP socket open only
when a bdaddr is not supplied, but it works fine when the bdaddr is provided
(thus skipping the search procedure described above). I've verified that
the bdaddr returned by the search function is, in fact, identical to that
supplied, so the parameters to the socket open call are identical. It
happens every time on some machines, and never on others - to my knowledge,
there are no intermittently failing machines. Any ideas?
The calling function is cwiid_connect, listed in
http://abstrakraft.org/cwiid/browser/trunk/libcwiid/connect.c
The search function is cwiid_find_wiimote, which calls
cwiid_get_bdinfo_array, both listed in
http://abstrakraft.org/cwiid/browser/trunk/libcwiid/bluetooth.c
Thanks for any help you can provide,
L. Donnie Smith
CWiid Developer
http://abstrakraft.org/cwiid
[-- Attachment #1.2: Type: text/html, Size: 1781 bytes --]
[-- Attachment #2: Type: text/plain, Size: 345 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2007-04-12 3:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 3:05 Donnie Smith [this message]
2007-04-12 7:46 ` [Bluez-devel] Error connecting after inquiry Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2007-04-12 19:42 Donnie Smith
2007-04-12 20:13 ` Marcel Holtmann
2007-04-14 16:01 Donnie Smith
2007-04-18 23:49 ` Marcel Holtmann
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=1d49725d0704112005q6b90105dtc9e2e6affc647f63@mail.gmail.com \
--to=cwiid@abstrakraft.org \
--cc=bluez-devel@lists.sourceforge.net \
/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