Return-Path: Subject: Re: [Bluez-devel] bluetoothd D-Bus interface proposals(draft 00.05) From: Marcel Holtmann To: bluez-devel@lists.sourceforge.net In-Reply-To: References: <9307f5f2050816154545b6f046@mail.gmail.com> <9307f5f2050818135877575293@mail.gmail.com> <8c9e090508191027e4646f1@mail.gmail.com> <1124709468.23599.27.camel@pegasus> <8c9e090508220504100c127e@mail.gmail.com> Content-Type: text/plain Message-Id: <1124720878.23599.47.camel@pegasus> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 22 Aug 2005 16:27:58 +0200 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