All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carmine Pirro <carrip@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Fwd: [Bluez-devel] callback for L2CAP disconnection
Date: Wed, 28 Jul 2004 16:08:18 +0200	[thread overview]
Message-ID: <17ca747604072807081342839b@mail.gmail.com> (raw)
In-Reply-To: <1091021474.3673.29.camel@notepaq>

The following is what i have to do:
a device A is connected to a device B.
When device A disconnects, a process on device B has to print the
device A bluetooth address on the screen with a appropriate message.

Thank you, Carmine.

---------- Forwarded message ----------
From: Marcel Holtmann <marcel@holtmann.org>
Date: Wed, 28 Jul 2004 15:31:14 +0200
Subject: Re: [Bluez-devel] callback for L2CAP disconnection
To: Carmine Pirro <carrip@gmail.com>
Cc: bluez-devel@lists.sourceforge.net

Hi Carmine,

> Does BlueZ stack provides a callback mechanism for L2CAP
> connections/disconnections?

what do you mean by callback? The BlueZ L2CAP implementation provides a
full sequential packet socket interface.

Regards

Marcel


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-07-28 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28 13:08 [Bluez-devel] callback for L2CAP disconnection Carmine Pirro
2004-07-28 13:31 ` Marcel Holtmann
2004-07-28 14:08   ` Carmine Pirro [this message]
2004-07-28 15:15     ` Marcel Holtmann
2004-07-28 14:21 ` Xavier GARREAU

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=17ca747604072807081342839b@mail.gmail.com \
    --to=carrip@gmail.com \
    --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.