From owner-freebsd-bluetooth@FreeBSD.ORG Tue Jan 20 17:58:39 2009 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDDA9106566B; Tue, 20 Jan 2009 17:58:39 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 7C47D8FC17; Tue, 20 Jan 2009 17:58:39 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 5AC73232822; Tue, 20 Jan 2009 12:55:00 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 20 Jan 2009 12:55:00 -0500 X-Sasl-enc: DG75W6mcer7BWAZpfTsmKmKSPCEHxRC7z1/2QyjmLb+d 1232474099 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 1F20E20866; Tue, 20 Jan 2009 12:54:57 -0500 (EST) Message-ID: <49760FF0.7000400@incunabulum.net> Date: Tue, 20 Jan 2009 17:54:56 +0000 From: Bruce M Simpson User-Agent: Thunderbird 2.0.0.19 (X11/20090116) MIME-Version: 1.0 To: Alfred Perlstein References: <200901152225.19150.hselasky@c2i.net> <200901161012.24544.hselasky@c2i.net> <4975CFD0.1000002@incunabulum.net> <20090120155028.GU60686@elvis.mu.org> In-Reply-To: <20090120155028.GU60686@elvis.mu.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-bluetooth@freebsd.org" , Hans Petter Selasky Subject: Re: Ongoing Bluetooth work; Linux-like APIs? 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: Tue, 20 Jan 2009 17:58:40 -0000 Alfred Perlstein wrote: > ... >> I wonder though if anyone has considered implementing the Linux APIs ? >> ... >> > > That would be good. Please ping about it if you don't see it within > a few weeks. > If folk have cycles to look at that, and are interested in following up, that is excellent news... Meanwhile, a good set of pointers would be: http://org.csail.mit.edu/pybluez/ http://lightblue.sourceforge.net/ http://people.csail.mit.edu/albert/bluez-intro/c404.html http://code.google.com/p/bluecove/ Broadly there's a surface of interfaces to underlying system services (e.g. RFCOMM sockets, OBEX libraries, HCI sockets and/or layer access, and SDP in particular) which needs to be considered. The APIs above themselves have limitations with things like working with multiple interfaces, etc. I had a very brief crack at trying to get BlueCove to work with the FreeBSD stack, but I couldn't justify the time involved to get it up and running, given we'd already started building a solution on Linux. The differences between the Linux and FreeBSD stacks are small but subtle enough to render generic code incompatible... sigh. thanks, BMS