From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jul 10 08:40:24 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 3350710656BE for ; Thu, 10 Jul 2008 08:40:24 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smtp02.one2one.net (smtp02.one2one.net [149.254.192.174]) by mx1.freebsd.org (Postfix) with ESMTP id C4DE18FC14 for ; Thu, 10 Jul 2008 08:40:23 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from [127.0.0.1] (helo=localhost) by localhost.localdomain with esmtp (Exim 4.50) id 1KGrhL-0003uV-FX; Thu, 10 Jul 2008 09:40:19 +0100 Received: from localhost.localdomain ([127.0.0.1]) by localhost (smtpbeckt01 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14921-06; Thu, 10 Jul 2008 09:40:19 +0100 (BST) Received: from [10.33.156.64] (helo=rya-online.net) by localhost.localdomain with smtp (Exim 4.50) id 1KGrhH-0003tz-Ry; Thu, 10 Jul 2008 09:40:18 +0100 Received: (nullmailer pid 1203 invoked by uid 1000); Thu, 10 Jul 2008 08:39:46 -0000 Date: Thu, 10 Jul 2008 09:39:46 +0100 (BST) To: Maksim Yevmenkin In-Reply-To: References: <48751292.7080902@lissyara.su> <48753475.5040402@lissyara.su> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1215679186.775945.722.nullmailer@galant.ukfsn.org> From: Iain Hibbert X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at example.com X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: plunky@rya-online.net X-SA-Exim-Scanned: No (on localhost.localdomain); SAEximRunCond expanded to false Cc: freebsd-bluetooth@freebsd.org 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: Thu, 10 Jul 2008 08:40:24 -0000 On Wed, 9 Jul 2008, Maksim Yevmenkin wrote: > furthermore, i want to go on the record here and say that if netgraph > (due to its complexity, etc.) is a big problem here, and, prevents > people from working on bluetooth in freebsd, i'm prepared to seriously > consider netbt stack as alternative. netgraph I considered too much work to look at and was no interest to have it in NetBSD or OpenBSD. Then I think after some years nobody had stepped up to make it work in DragonflyBSD so they have imported the netbt stack also. personally, I think that diversity is always good. The vast majority of applications use L2CAP or RFCOMM and the API for these are almost exactly similar across the whole range of open OS's (BlueZ included). I think even that there are some things in NetBSD that are still wrong (I think that using a raw socket for HCI is not correct, we should address devices directly -- but that is not going to change) or incomplete (SCO support is not great though it does work on some platforms) and nobody else picked up on libprop(3) so that has meant some rewriting down the line (there are bthcid/btkey implementations in OpenBSD without libprop) The way that the OS handles devices is always going to be different and that will make more rewriting, so I would think that FreeBSD importing the netbt stack "to gain SCO support" would not in the end necessarily make anything simpler. iain