From owner-freebsd-bluetooth@FreeBSD.ORG Sun Dec 4 07:39:38 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D81D016A41F for ; Sun, 4 Dec 2005 07:39:38 +0000 (GMT) (envelope-from marcel@holtmann.org) Received: from mail.holtmann.net (coyote.holtmann.net [217.160.111.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0F6A43D62 for ; Sun, 4 Dec 2005 07:39:37 +0000 (GMT) (envelope-from marcel@holtmann.org) Received: from blade (p5487EA2A.dip.t-dialin.net [84.135.234.42]) by mail.holtmann.net (8.13.4/8.13.4/Debian-3) with ESMTP id jB47dob9017891 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 4 Dec 2005 08:39:51 +0100 From: Marcel Holtmann To: "P. Durante" In-Reply-To: <9307f5f20512031333x61e9d141u85ea578711740712@mail.gmail.com> References: <9307f5f20512030807x6eadc73cq9d9acc9dd5503a5b@mail.gmail.com> <4391E320.2090006@savvis.net> <9307f5f20512031333x61e9d141u85ea578711740712@mail.gmail.com> Content-Type: text/plain; charset=utf-8 Date: Sun, 04 Dec 2005 08:39:58 +0100 Message-Id: <1133681998.4427.7.camel@blade> Mime-Version: 1.0 X-Mailer: Evolution 2.5.2 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=1.2 required=5.0 tests=BAYES_00, DATE_IN_FUTURE_12_24 autolearn=no version=3.0.3 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on coyote.holtmann.net X-Virus-Scanned: ClamAV 0.84/1202/Sun Dec 4 04:41:04 2005 on coyote.holtmann.net X-Virus-Status: Clean Cc: freebsd-bluetooth@freebsd.org Subject: Re: Automatic bluetooth device initialization X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 07:39:39 -0000 Hi Paul, > To solve such (not uncommon) problems, the dbus system[ยน] is being > developed, dbus is getting very popular (maybe too much) and it > provides a simple and secure messaging system to let different > programs talk to one another, in our example, let one program be the > bluetooth daemon, it provides a well-known interface and hides > platform-specific implementation details, on the other side we have > the other programs, which are just frontends (with a Qt/Gtk/textual > interface, it doesn't matter) and can run on every operating system > where the aforementioned interface is available, I think something > like this wouldn't hurt to any "desktop-unix" operating system. start looking at the D-Bus effort of BlueZ. We are moving into that direction and one of the main goals is to not even abstract from the operating system details, we also wanna abstract from the HCI specific details of Bluetooth. Feel free to join-in and help defining the new D-Bus interface for Bluetooth. Regards Marcel