Linux bluetooth development
 help / color / mirror / Atom feed
From: Claudio Takahasi <cktakahasi@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] [DBUS-PATCH] new signals(DeviceAdded and DeviceRemoved)
Date: Mon, 17 Oct 2005 19:37:01 -0200	[thread overview]
Message-ID: <e1effdeb0510171437w1a668500kf963ae3acb55eb2f@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 759 bytes --]

Hi folks,

This patch add two new signals: DeviceAdded and DeviceRemoved.
These signals are sent in the path /org/bluez/Manager/Controller

I am accepting suggestions to change the path if someone think it can be
changed.
The signal "DeviceAdded" can't related to a device specific path (eg:
/org/bluez/Manager/hci0/Controller )
and put the "DeviceRemoved" signal in a different path is not a good idea.

If you notice a conflict with the lastest Johan's patch let me know that I
can create the patch again.

The handle_inq_req reply was fixed too, the return was wrong.

Regards,
Claudio.
--
---------------------------------------------------------
Claudio Takahasi
Nokia's Institute of Technology - INdT
claudio.takahasi@indt.org.br

[-- Attachment #2: Type: text/html, Size: 900 bytes --]

             reply	other threads:[~2005-10-17 21:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-17 21:37 Claudio Takahasi [this message]
     [not found] ` <20051018071545.GA7228@localhost.localdomain>
2005-10-18 11:13   ` [Bluez-devel] [DBUS-PATCH] new signals(DeviceAdded and DeviceRemoved) Claudio Takahasi
2005-10-18 17:35     ` Marcel Holtmann
     [not found]       ` <e1effdeb0510181213x77832121t236cf91e83a6befa@mail.gmail.com>
     [not found]         ` <1129718124.5362.0.camel@localhost.localdomain>
2005-10-19 11:03           ` Claudio Takahasi

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=e1effdeb0510171437w1a668500kf963ae3acb55eb2f@mail.gmail.com \
    --to=cktakahasi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox