From owner-freebsd-bluetooth@FreeBSD.ORG Tue Jan 9 21:07:10 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6669816A403 for ; Tue, 9 Jan 2007 21:07:10 +0000 (UTC) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out001a.email.savvis.net (out001.apptix.savvis.net [216.91.32.44]) by mx1.freebsd.org (Postfix) with ESMTP id 3312F13C458 for ; Tue, 9 Jan 2007 21:07:09 +0000 (UTC) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from s228130hz1ew171.apptix-01.savvis.net ([10.146.4.29]) by out001a.email.savvis.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 9 Jan 2007 15:07:09 -0600 Received: from [127.0.0.1] ([75.82.168.166]) by s228130hz1ew171.apptix-01.savvis.net over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Tue, 9 Jan 2007 15:07:08 -0600 Message-ID: <45A403FC.7050106@savvis.net> Date: Tue, 09 Jan 2007 13:07:08 -0800 From: maksim yevmenkin User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Marcel Holtmann References: <45A3BAAB.4040903@zk.informjust.ua> <45A3D66C.2050605@savvis.net> <49327.91.124.7.194.1168371717.squirrel@webmail.ic.uz.ua> <45A3F31D.2060709@savvis.net> <1168375720.32577.6.camel@violet> In-Reply-To: <1168375720.32577.6.camel@violet> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 09 Jan 2007 21:07:08.0938 (UTC) FILETIME=[1FC546A0:01C73432] Cc: freebsd-bluetooth@freebsd.org Subject: Re: is bluetooth 2.0 speeds supported on freebsd? 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: Tue, 09 Jan 2007 21:07:10 -0000 Marcel, >>>>> Does freebsd implementation of bluetooth stack support data rates of >>>>> bluetooth 2.0? >>>> no, freebsd bluetooth stack is v1.1 and does not support bluetooth 2.0 >>>> edr as of now. >>> AS OF NOW sounds better than NEVER will :o) but may I ask you do you make >>> some steps towards edr support? is it realy hard to include edr support? >> the main problem is time. basically i have to >> >> 1) go to a store/online and pick up a couple of bluetooth 2.0+edr >> adapters. those are in $20 us range now (i.e cheap); >> >> 2) read and understand bluetooth 2.0 spec; >> >> 3) make changes to the existing code; >> >> i do not think it would be very hard to add edr support. i suspect that >> all needed to be done is to properly detect and configure edr device. >> >>> can I help with something? I'm wery base-level programmer, but if you >>> point me to some docs or specs etc or may be just give me some part of >>> whole job I can help? AFAIK BlueZ do not support edr too... is it so >>> difficult to implement edr on 1.1 base? >> like i said, it should not be very hard to add 2.0+edr support. btw, >> bluez does support 2.0+edr, so it could save me some time. >> >> you could do a simple task of updating ng_hci.h headers to include all >> the 2.0+edr hci commands and events. i think someone already might have >> done a port of it. you are more then welcome to send patches to the list. > > actually you don't have to do anything to support EDR. The way EDR is > specified is that it is on by default if both sides support EDR. The > link manager will automatically detect it and then use it. Only when you > wanna disable EDR you have to set the bits in packet mask. thanks for the comment. that is what i meant by "properly detect and configure edr device". basically look at the supported features for the local device and set packet type mask depending on this. as it stands right now freebsd bluetooth stack will only use DM/H1, DM/H3 and DM/H5 packets (last two only used if the device supports them). thanks, max