From owner-freebsd-bluetooth@FreeBSD.ORG Thu Mar 9 18:40:05 2006 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 4CABA16A420 for ; Thu, 9 Mar 2006 18:40:05 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAB3543D4C for ; Thu, 9 Mar 2006 18:40:04 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id k29IdsM31577; Thu, 9 Mar 2006 13:39:55 -0500 Message-ID: <44107678.1080206@savvis.net> Date: Thu, 09 Mar 2006 10:39:52 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Iain Hibbert References: <1141918855.418446.1437.nullmailer@galant.ukfsn.org> In-Reply-To: <1141918855.418446.1437.nullmailer@galant.ukfsn.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: config files 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, 09 Mar 2006 18:40:05 -0000 Iain, > I have been playing with bthidd and bthidcontrol today, both are > compiled on NetBSD (all keyboard/mouse interpretation is removed) good > And, I've been playing with my mouse trying to see it working so I know > what to do, but gosh was having a terrible time of it. I worked out what > my problem was (I thought it used no pin, when it should have been "0000" > - the Apple documentation doesnt seem to mention this :) so I'm on track > again I think. yes. most (all?) mice/headsets and other devices with limited user interface have "fixed pin". it is usually "0000". > I was wondering though, if it would be more admin friendly to have a > single "bluetooth.conf" file with a single parser (maybe in libbluetooth)? > Each different program would never see the keywords that it didnt > understand.. i do not like this idea. having one huge config file for every possible bluetooth application seems like a bad thing to me. i agree, parser code can be moved in libbluetooth (or whatever), but config files should stay separate. thanks, max