public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] bluetoothd D-Bus interface proposals(draft 00.05)
Date: Mon, 22 Aug 2005 16:27:58 +0200	[thread overview]
Message-ID: <1124720878.23599.47.camel@pegasus> (raw)
In-Reply-To: <e1effdeb0508220527500878ab@mail.gmail.com>

Hi Claudio,

> It's possible register multiple D-Bus object paths. My suggestion 
> for handle multiple adapters is register a default path and paths
> based on the device address. 
> eg: suppose two adapters(11:22:33:44:55:66, 77:88:99:00:11:22)
> 
> The possible paths are:
> 
> /org/bluez/bluetoothd/hci (default path - first adapter)
> /org/bluez/bluetoothd/112233445566/hci (first adapter)
> /org/bluez/bluetoothd/778899001122/hci (second adapter)
> 
> /org/bluez/bluetoothd/pan (default path - first adapter)
> /org/bluez/bluetoothd/112233445566/pan (first adapter)
> /org/bluez/bluetoothd/778899001122/pan (second adapter)
> ...
> 
> The service to list the adapter must be moved to the main path
> (/org/bluez/bluetoothd) or to a new one /org/bluez/bluetoothd/devices.
> 
> The message handle function will become more complex, but I don't
> see other solution.

the main problem is that I would like to do identification of the host
adapter by id (hci0), by address (11:22:33:44:55:66) and maybe by an
alias (bluecore-dongle) or by its name ("BlueZ dongle"). The only fully
unique identification across reboots/enumerations is the address. For
the kernel it is only the current id and this means bluetoothd has to
translate between them. If you look at the default adapter by the
address identification it is 00:00:00:00:00:00 (BDADDR_ANY) and I will
leave it this way.

When choosing a default adapter without any further configuration we
must do this unique and for this means this decision can only be done by
the kernel. This means that the kernel need to know about a change and
must also tell bluetoothd what it thinks is the default adapter.

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

  parent reply	other threads:[~2005-08-22 14:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 21:15 [Bluez-devel] bluetoothd D-Bus interface proposals(draft 00.05) Claudio Takahasi
2005-08-16 22:45 ` P. Durante
2005-08-18 12:05   ` Claudio Takahasi
2005-08-18 20:58     ` P. Durante
2005-08-19 17:27       ` Elvis Pfützenreuter
2005-08-22 11:17         ` Marcel Holtmann
2005-08-22 12:04           ` Elvis Pfützenreuter
2005-08-22 12:27             ` Claudio Takahasi
2005-08-22 12:37               ` Peter Robinson
2005-08-22 12:51                 ` Claudio Takahasi
2005-08-22 14:26                   ` P. Durante
2005-08-22 14:34                     ` Marcel Holtmann
2005-08-22 17:39                       ` Claudio Takahasi
2005-08-22 17:50                         ` Marcel Holtmann
2005-08-22 19:47                           ` Claudio Takahasi
2005-08-29 21:13                             ` Claudio Takahasi
2005-08-29 21:46                               ` Marcel Holtmann
2005-08-30 10:07                                 ` Paul Hedderly
2005-08-30 13:14                                 ` Claudio Takahasi
2005-08-30 18:16                                   ` Claudio Takahasi
2005-09-01  9:57                                     ` Marcel Holtmann
2005-08-22 14:29                 ` Marcel Holtmann
2005-08-22 14:27               ` Marcel Holtmann [this message]
2005-08-22 14:21             ` Marcel Holtmann

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=1124720878.23599.47.camel@pegasus \
    --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