From owner-freebsd-bluetooth@FreeBSD.ORG Thu Feb 5 18:01:04 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 ED7CD106566C for ; Thu, 5 Feb 2009 18:01:04 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id 95DF48FC18 for ; Thu, 5 Feb 2009 18:01:04 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so169714ywe.13 for ; Thu, 05 Feb 2009 10:01:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=XABnpb0LLM4YNxL/814SuPgad/7wOTyUZuWEtlT9dlo=; b=Cq0m5LXY9/lasZwY48vfniAntmc0WKU+zFJkYLSy1OMoCOY0gPRDlhmSxIeXsUCCul f9tenFD/s13TrcbHN0SYSi/Q21eP6OGUcP/Az8uts2UAtDRFZPww3+qu90KDNIQcm2wU 8RZRC9AHjrBQDuz/nP4/WcMl97rmEL//JTnjU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=veFlbFKvjQV0AJALt1Inx/3JXDx12tlektKntP6gVrmM3oPHSbJuc4XtdHQcqwnjCt HyXr9/qqzaXCoqOeN8/k4A2Gxg/1aRfgm1tsxoFExZ1A7BE/K75eS5q93rlzzX4TFDFk taeZ4w7eOTwksqD4/1Y6jViLj7FaYu3LEQA+o= MIME-Version: 1.0 Received: by 10.150.137.14 with SMTP id k14mr270075ybd.173.1233856863967; Thu, 05 Feb 2009 10:01:03 -0800 (PST) In-Reply-To: <1233845167.798942.24919.nullmailer@galant.ukfsn.org> References: <1233365217.00068654.1233354838@10.7.7.3> <4988DCCC.80201@mavhome.dp.ua> <4988EBAC.3080202@mavhome.dp.ua> <1233758519.360141.162.nullmailer@galant.ukfsn.org> <1233845167.798942.24919.nullmailer@galant.ukfsn.org> Date: Thu, 5 Feb 2009 10:01:03 -0800 Message-ID: From: Maksim Yevmenkin To: Iain Hibbert Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-bluetooth@freebsd.org" Subject: Re: libhci 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, 05 Feb 2009 18:01:05 -0000 On Thu, Feb 5, 2009 at 6:46 AM, Iain Hibbert wrote: > On Wed, 4 Feb 2009, Maksim Yevmenkin wrote: > >> int hci_inquiry(...) >> >> and all the way down to the end of the file :) basically map dev_id to >> unit numbers, i.e. dev_id 0 is "ubt0" node, etc. > > Well, I really dislike that dev_id method to start with. But anyway, I > think they are working on a new API that is somewhat higher level and more > related to the dbus access. of course they are :) its linux :) they always working on something new and improved :) anyway, what would you suggest to use instead of dev_id? device name (i.e. ubt0)? anything else? cant use bd_addr because (in freebsd at least) device has to be "initialized" before bd_addr is known. > Also, I think that looking at that code, it was written in the beginning > and is full of 'good ideas' that somebody might want to use, but in > reality much of it has no need to be in a shared library. > > hci_inquiry() is perhaps the only function that really needs to have a > generic cross platform API and it would be nice if it was oriented towards > application level rather than tied to a lower layer implementation. I do > not know what kind of API the Microsoft (Widcom?) or Apple stacks expose > to applications for this, but I suspect they would be a better place to > start. i will take a look at ms api. but surely we have ability to send and receive hci commands/events and enumerate all radios in the system in addition to inquiry, dont you think? thanks, max