From: "Olivier Le Pogam" <olepogam@free.fr>
To: "BlueZ-Dev" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Bluez libs 3.22 & hci_read_remote_name
Date: Wed, 7 Nov 2007 16:01:49 +0100 [thread overview]
Message-ID: <00ef01c8214f$1f9cc580$0200a8c0@jester> (raw)
In-Reply-To: 000001c8212f$58c2cc80$0a486580$@savary@kerlink.fr
Hello,
I have big problems making "hci_read_remote_name" work using libs 3.22, it
is very long or blocking.
I had to roll back to 3.20 which is working fine.
I have 4 dongles on my computer, maybe has there been a change on
multi-devices in 3.22 ?
If you need me to investigate further just ask me what to do and I'll
provide you with more details.
Regards,
Oli
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-11-07 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 11:14 [Bluez-devel] Bluez utils and libs 3.22 Pierre Savary
2007-11-07 15:01 ` Olivier Le Pogam [this message]
2007-11-07 18:26 ` [Bluez-devel] Bluez libs 3.22 & hci_read_remote_name Manuel Naranjo
2007-11-07 18:28 ` Marcel Holtmann
2007-11-07 18:27 ` [Bluez-users] [Bluez-devel] Bluez utils and libs 3.22 Marcel Holtmann
2007-11-08 7:49 ` [Bluez-devel] [Bluez-users] " Pierre Savary
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='00ef01c8214f$1f9cc580$0200a8c0@jester' \
--to=olepogam@free.fr \
--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 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.