From owner-freebsd-bluetooth@FreeBSD.ORG Sat Mar 25 00:01:13 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 3349816A423 for ; Sat, 25 Mar 2006 00:00:55 +0000 (UTC) (envelope-from maksim.yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id A838643D48 for ; Sat, 25 Mar 2006 00:00:36 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id 4FE373BF39; Fri, 24 Mar 2006 18:00:36 -0600 (CST) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 16695-01-12; Fri, 24 Mar 2006 18:00:36 -0600 (CST) Received: from [10.254.186.111] (sntc04ep01.savvis.net [64.14.1.106]) by mailgate1b.savvis.net (Postfix) with ESMTP id DFE063BE2D; Fri, 24 Mar 2006 18:00:35 -0600 (CST) Message-ID: <44248823.3040907@savvis.net> Date: Fri, 24 Mar 2006 16:00:35 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Carlos_Fern=E1ndez_Herranz?= References: <4423D096.2010205@udc.es> In-Reply-To: <4423D096.2010205@udc.es> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at savvis.net Cc: freebsd-bluetooth@freebsd.org Subject: Re: About Inquiry_with_RSSI 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, 25 Mar 2006 00:01:13 -0000 [...] > > I would like to know if it could be possible upgrade the Bluetooth stack > so the command Inquiry_with_RSSI could be supported and the way I could strictly speaking it should be already supported. all you need to do is to create proper hci command packet and send it via hci raw socket. you also might need to adjust filter settings on the hci raw socket to allow command to be sent. whats missing is the definition of new bluetooth v1.2 hci commands and events, but nothing prevents you from defining those locally and creating valid hci command packet. of course, the device itself must support bluetooth v1.2 hci commands/events. > do it. Can I follow the BlueZ stack to adapt the FreeBSD one? i'm not sure what are you asking here. thanks, max