public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
* [Bluez-devel] EVT_CONN_COMPLETE not received on HCI socket when RFComm connected
@ 2005-07-28 14:55 Frederic Danis
  2005-07-28 23:13 ` Marcel Holtmann
  0 siblings, 1 reply; 2+ messages in thread
From: Frederic Danis @ 2005-07-28 14:55 UTC (permalink / raw)
  To: bluez-devel

Hello,

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 ?

Regards

Fred

-- 
-----------------------------------------------
It is not by improving the oil lamp that one invents the electric bulb!
-----------------------------------------------
Danis Frederic            PalmSource Europe
Software engineer
Mail : mailto:frederic.danis@palmsource.com
-----------------------------------------------



-------------------------------------------------------
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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-07-28 23:13 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox