From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jul 9 21:58:28 2008 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 B322F106564A for ; Wed, 9 Jul 2008 21:58:28 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from hosting.lissyara.su (hosting.lissyara.su [77.221.149.162]) by mx1.freebsd.org (Postfix) with ESMTP id 631EC8FC1D for ; Wed, 9 Jul 2008 21:58:28 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from [89.178.161.98] (port=10744 helo=acer.lissyara.int.otradno.ru) by hosting.lissyara.su with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KGhfx-000A5p-PV for freebsd-bluetooth@freebsd.org; Thu, 10 Jul 2008 01:58:13 +0400 Message-ID: <48753475.5040402@lissyara.su> Date: Thu, 10 Jul 2008 01:58:13 +0400 From: Alex Keda User-Agent: Thunderbird 2.0.0.14 (X11/20080609) MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org References: <48751292.7080902@lissyara.su> In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-Descriptions: powered by www.lissyara.su X-Bounce-ID: hosting.lissyara.su Subject: Re: bluetooth stack ported from NetBSD 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: Wed, 09 Jul 2008 21:58:28 -0000 >i took very quick look - good effort :) there are however, few locking >issues, and, some utilities are missing. hmm, what issues ? >also, original thread seems to be about some bluetooth gps device. the thread about ported netbt stack to freebsd not gps ;) why netbt ? becouse native stack freebsd not support SCO audio rfcomm_sppd i's first step >bluetooth gps should work just fine with freebsd. i have one myself >and it works without any problems. most (all?) blueooth gps devices >simply use serial port profile, so rfcomm_sppd will work just fine for >this.