From owner-freebsd-bluetooth@FreeBSD.ORG Sat Apr 12 18:26:38 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 67E66106566C for ; Sat, 12 Apr 2008 18:26:38 +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 E4ADD8FC18 for ; Sat, 12 Apr 2008 18:26:37 +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 1JkkQq-0002Zv-RW; Sat, 12 Apr 2008 19:26:32 +0100 Received: from localhost.localdomain ([127.0.0.1]) by localhost (smtpbeckt01 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09764-05; Sat, 12 Apr 2008 19:26:32 +0100 (BST) Received: from [10.32.78.154] (helo=rya-online.net) by localhost.localdomain with smtp (Exim 4.50) id 1JkkQo-0002Zo-0u; Sat, 12 Apr 2008 19:26:32 +0100 Received: (nullmailer pid 1072 invoked by uid 1000); Sat, 12 Apr 2008 18:26:13 -0000 Date: Sat, 12 Apr 2008 19:26:12 +0100 (BST) To: Maksim Yevmenkin In-Reply-To: References: <20080410230521.027b3b78.saamii@gmail.com> <20080412022834.4b36e8c0.saamii@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1208024773.051889.1001.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 application 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: Sat, 12 Apr 2008 18:26:38 -0000 On Sat, 12 Apr 2008, Maksim Yevmenkin wrote: > what is not "easy" about obexapp? are there any particular features > that you are missing? One thing that I have been meaning to add but haven't found the time, is that when obexapp runs in server mode, it would be good to run different services (OPUSH/FTRN) on different channels as currently they run on the same channel. The reason I want this is so I can require authorisation for FTRN but allow OPUSH to anybody. The context methodology that obexapp uses should be fairly easily extendable for this, though I found the openobex API to be complex and it might be simpler to make each service run as a separate instance. If you are planning to work on bluetooth infrastructure (what, child grown up already!? :) then even though I don't use FreeBSD, I suggest: + "Link Mode" enable AUTH and ENCRYPT flags for individual L2CAP or RFCOMM channels (eg for above). I also did SECURE (ENCRYPT plus refresh link key) and worked on MASTER but had limited success so thats on hold for now. + removal of ng_ and NG_ prefixes from public API (HCI and L2CAP IIRC) will make porting programs much easier.. I would recommend that you can take the hci.h and l2cap.h defs from NetBSD files so that the spelling is constant throughout the BSD family at least. (also, I added HCI 2.1 already) + commit the SCO code you mentioned the other day you said you didn't know how it could be used, but until it is public then of course nobody else can work on that :) regards, iain