From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] EVT_CONN_COMPLETE not received on HCI socket when RFComm connected
Date: Fri, 29 Jul 2005 01:13:46 +0200 [thread overview]
Message-ID: <1122592426.5814.1.camel@notepaq> (raw)
In-Reply-To: <42E8F1F8.10700@palmsource.com>
Hi Fred,
> I am writing a daemon that watches over bluetooth states (up, down,
> connected, disconnected, ...) to display this information to user.
> I use HCI_FILTER (set to all events) to do this, but when a program make
> a connection using RFComm I do not receive the EVT_CONN_COMPLETE event
> (I use BlueZ 2.17 libs and utils).
> Is it normal ? Is there a way to watch for connection/disconnection for
> all protocols ?
you can only watch ACL and SCO connect complete events with it. With the
new bluetoothd and the new event mechanism from the kernel we can add
something like this. In general it is not possible to what RFCOMM events
for connection and disconnection.
Regards
Marcel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-07-28 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 14:55 [Bluez-devel] EVT_CONN_COMPLETE not received on HCI socket when RFComm connected Frederic Danis
2005-07-28 23:13 ` Marcel Holtmann [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=1122592426.5814.1.camel@notepaq \
--to=marcel@holtmann.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