From owner-freebsd-bluetooth@FreeBSD.ORG Mon May 8 18:03:25 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 EA2D916A400 for ; Mon, 8 May 2006 18:03:24 +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 73E8643D45 for ; Mon, 8 May 2006 18:03:24 +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 095A93BE38; Mon, 8 May 2006 13:03:24 -0500 (CDT) 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 29020-01-10; Mon, 8 May 2006 13:03:23 -0500 (CDT) Received: from [10.254.186.111] (sntc04ep01.savvis.net [64.14.1.106]) by mailgate1b.savvis.net (Postfix) with ESMTP id 88A5E3BE26; Mon, 8 May 2006 13:03:23 -0500 (CDT) Message-ID: <445F87EA.7090609@savvis.net> Date: Mon, 08 May 2006 11:03:22 -0700 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: <4423D096.2010205@udc.es> <44248823.3040907@savvis.net> <1145275616.851775.858.nullmailer@galant.ukfsn.org> <4445206D.4030109@savvis.net> <1146945718.380438.1055.nullmailer@galant.ukfsn.org> In-Reply-To: <1146945718.380438.1055.nullmailer@galant.ukfsn.org> 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: USB isoc xfers 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: Mon, 08 May 2006 18:03:25 -0000 Iain, sorry for the delay. i'm completely swamped at the moment. >>this is a work in progress code that i used to receive sco data from the >>headset. this is NOT complete, its for the reference purposes. i have not >>tried to send sco data. > > Hi Max, did you do any further work on this? I have been stuck for a week > but I think I found now what has been causing me trouble, which was that > sending data proceeds for a bit, then the dongle locks up. Any bulk > transfers bomb out with IOERROR and the control pipe only returns STALLED > (trying to clear the stall does nothing). Even the flashing light goes > out! sounds bad > This seems to be caused by sending partial frames. Everything proceeds > well if I arrange the SCO packets to fill the frames exactly. eg using > config #2 (one 16-bit voice channel), with 17 byte frame lengths and 48 > (+3 hdr) byte packets then what I have works fine with 3 frames per > packet. what sco packets are you using hv1, hv2 or hv3? also i do not think it is good idea to send partial frames. sco was designed to carry 8 khz encoded (8-bit a/u-law or 13/16-bit linear) 64 kbit/sec audio stream. since over the air encoding is usually cvsd the hardware has to convert host encoding to over-the-air encoding and vice versa. > It would seem a little clunky to me to work out optimum SCO packet lengths > unless I went with one packet per frame, but the overhead could become > significant in that case. sco packet size is pretty much defined by the packet type, imo, i.e. hv1, hv2 or hv3. i'm not very clear on relation between usb packet size and sco packet size. i'm not sure if usb interface configuration needs to be switched to match sco packet selected. from my point of view hv3 packets are the best, because they consume the least amount of available slots/"bandwidth" on bluetooth link, i.e. hv3 has 30 bytes of payload, 30 bytes / 64 kbit/sec = 3.72 msec of audio. one slot is 0.625 msec, so 3.72 msec / 0.625 msec = 6. this means that to maintain half duplex 8 khz encoded 64 kbit/sec audio link with one hv3 packet has to be sent every 6th slot. to maintain full duplex link - one hv3 packet has to be sent every 3rd slot. that leaves 2 extra slots to send other acl or sco data. > I'm not sure exactly why this has been causing trouble, because the usb > hardware/driver does feel free to provide partial incoming frames > sometimes. I glanced at the uhci spec and see nothing obviously forbidding > it there, and the uhci driver similarly. It would be interesting to see if > FreeBSD gives the same results, since the usb drivers are the same. perhaps you need to allow "short transfers"? thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Mon May 8 19:44:39 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 A44F916A40A for ; Mon, 8 May 2006 19:44:39 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from mail06.svc.cra.dublin.eircom.net (mail06.svc.cra.dublin.eircom.net [159.134.118.22]) by mx1.FreeBSD.org (Postfix) with SMTP id 942EF43D70 for ; Mon, 8 May 2006 19:44:35 +0000 (GMT) (envelope-from plunky@rya-online.net) Received: (qmail 32600 messnum 2891978 invoked from network[83.70.176.191/unknown]); 8 May 2006 19:44:33 -0000 Received: from unknown (HELO rya-online.net) (83.70.176.191) by mail06.svc.cra.dublin.eircom.net (qp 32600) with SMTP; 8 May 2006 19:44:33 -0000 Received: (nullmailer pid 6432 invoked by uid 1000); Mon, 08 May 2006 19:41:59 -0000 Date: Mon, 8 May 2006 20:41:59 +0100 (BST) To: Maksim Yevmenkin In-Reply-To: <445F87EA.7090609@savvis.net> References: <4423D096.2010205@udc.es> <44248823.3040907@savvis.net> <1145275616.851775.858.nullmailer@galant.ukfsn.org> <4445206D.4030109@savvis.net> <1146945718.380438.1055.nullmailer@galant.ukfsn.org> <445F87EA.7090609@savvis.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1147117319.452701.5839.nullmailer@galant.ukfsn.org> From: Iain Hibbert Cc: freebsd-bluetooth@freebsd.org Subject: Re: USB isoc xfers 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: Mon, 08 May 2006 19:44:39 -0000 On Mon, 8 May 2006, Maksim Yevmenkin wrote: > what sco packets are you using hv1, hv2 or hv3? I allow any or all types, I can't really think of a good reason to tweak that and I'm sure it says somewhere in the HCI docs that enabling everything is probably better unless you have a good reason. > also i do not think it is good idea to send partial frames. sco was > designed to carry 8 khz encoded (8-bit a/u-law or 13/16-bit linear) 64 > kbit/sec audio stream. since over the air encoding is usually cvsd the > hardware has to convert host encoding to over-the-air encoding and vice > versa. I havent tried different voice settings than the default as yet > sco packet size is pretty much defined by the packet type, imo, i.e. > hv1, hv2 or hv3. Well, I'm thinking the 'on air' packet type is mostly irrelevant here because the controller is taking the data and encoding it differently, and the SCO packets only exist between the Host and Controller. So, if I send 24 words of linear I'm not sure how that translates to cvsd anyway, but sure the dongle must be doing some per channel buffering. > i'm not very clear on relation between usb packet size and sco packet > size. i'm not sure if usb interface configuration needs to be switched to > match sco packet selected. Yeah, I think it might be - I have dodged around that issue by providing a sysctl knob "hw.ubt0.config" to select the configuration and leave it up to the sysadmin to set what they need, but so far I can only support one voice channel properly anyway because I need to think about a fair queuing mechanism, so I think config #2 is probably the best. Actually, I'm fairly unclear on the usb isoc transfers - it seems to say in the book that each frame takes 1ms, so I think if I set config #5 with 49 byte frames, there will be overruns. In any case, using config #2 (17 byte frames) and 48 byte SCO packets (==3 frames exactly) seems to work ok for 3 minutes of audio. (I should sample a longer track maybe, I am getting bored with that one :) > perhaps you need to allow "short transfers"? Well, I'm willing to try anything - lack of documentation is great :) I think most of the problems I am seeing are really problems in the isoc part of the USB stack, which is not well used. I emailed this Hans Petter Selasky guy from FreeBSD that is rewriting the USB stack and he says the current one does have some problems with isoc, but I didnt try his version as yet. iain From owner-freebsd-bluetooth@FreeBSD.ORG Thu May 11 21:57:21 2006 Return-Path: X-Original-To: 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 0A7E816A501 for ; Thu, 11 May 2006 21:57:21 +0000 (UTC) (envelope-from sean@mcneil.com) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7FCD43D5A for ; Thu, 11 May 2006 21:57:20 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 3FE8DF2854 for ; Thu, 11 May 2006 14:57:20 -0700 (PDT) X-Virus-Scanned: by amavisd-new at mcneil.com Received: from mail.mcneil.com ([127.0.0.1]) by localhost (triton.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nHQ9zP2BammJ for ; Thu, 11 May 2006 14:57:19 -0700 (PDT) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 045E3F22AE for ; Thu, 11 May 2006 14:57:19 -0700 (PDT) From: Sean McNeil To: bluetooth@freebsd.org Content-Type: text/plain Date: Thu, 11 May 2006 14:57:18 -0700 Message-Id: <1147384638.88133.4.camel@triton.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: Re: Setting up a bluetooth mouse on FreeBSD 6 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, 11 May 2006 21:57:24 -0000 >From previous emails, I found: Eric Anderson's blog at http://destari.blogspot.com/2006/01/setting-up-bluetooth-mouse-on-freebsd.html I did this and my mouse works, but unfortunately the middle and right mouse buttons are reversed. This is a bluetooth mouse I got with my Acer Ferrari lapop. Movement isn't quite as smooth as a USB mouse either, but it isn't that bad. Another odd thing here is that bluetooth is enabled in the standard build of -CURRENT, but bthidd and bthidcontrol are not. Will these be added in anytime soon? Cheers, Sean From owner-freebsd-bluetooth@FreeBSD.ORG Fri May 12 01:57:47 2006 Return-Path: X-Original-To: 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 38ACF16A408 for ; Fri, 12 May 2006 01:57:47 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E4A543D49 for ; Fri, 12 May 2006 01:57:46 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.21] (andersonbox1.centtech.com [192.168.42.21]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k4C1vjA1075199; Thu, 11 May 2006 20:57:45 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4463EB9B.8070304@centtech.com> Date: Thu, 11 May 2006 20:57:47 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.2 (X11/20060506) MIME-Version: 1.0 To: Sean McNeil References: <1147384638.88133.4.camel@triton.mcneil.com> In-Reply-To: <1147384638.88133.4.camel@triton.mcneil.com> Content-Type: multipart/mixed; boundary="------------090207040400060100090102" X-Virus-Scanned: ClamAV 0.87.1/1459/Thu May 11 15:46:49 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: bluetooth@freebsd.org Subject: Re: Setting up a bluetooth mouse on FreeBSD 6 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: Fri, 12 May 2006 01:57:47 -0000 This is a multi-part message in MIME format. --------------090207040400060100090102 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sean McNeil wrote: >>From previous emails, I found: > > Eric Anderson's blog at > http://destari.blogspot.com/2006/01/setting-up-bluetooth-mouse-on-freebsd.html > > I did this and my mouse works, but unfortunately the middle and right > mouse buttons are reversed. This is a bluetooth mouse I got with my > Acer Ferrari lapop. Movement isn't quite as smooth as a USB mouse > either, but it isn't that bad. > > Another odd thing here is that bluetooth is enabled in the standard > build of -CURRENT, but bthidd and bthidcontrol are not. Will these be > added in anytime soon? There is a patch to bthidd (check gnats, but I've attached the one I found) to fix that. I'm not sure what Max's plans are to commit or not, but it's a needed patch for sure. I think (but I'm nobody) that bthidd and bthidcontrol should be enabled on current for greater exposure, and then enabled on -STABLE. I've been using it for quite some time, and it's been very solid. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ --------------090207040400060100090102 Content-Type: text/x-patch; name="bthidd.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="bthidd.patch" Index: hid.c =================================================================== RCS file: /alt/ncvs/src/usr.sbin/bluetooth/bthidd/hid.c,v retrieving revision 1.2 diff -u -u -r1.2 hid.c --- hid.c 18 Nov 2004 18:05:15 -0000 1.2 +++ hid.c 5 May 2006 18:55:52 -0000 @@ -130,6 +130,8 @@ mouse_x, mouse_y, mouse_z, mouse_butt, mevents, kevents; +#define HID_BUT(i) ((i) < 3 ? (((i) ^ 3) % 3) : (i)) + assert(s != NULL); assert(s->srv != NULL); assert(data != NULL); @@ -216,7 +218,7 @@ break; case HUP_BUTTON: - mouse_butt |= (val << (usage - 1)); + mouse_butt |= (val << HID_BUT(usage - 1)); mevents ++; break; --------------090207040400060100090102-- From owner-freebsd-bluetooth@FreeBSD.ORG Fri May 12 03:36:04 2006 Return-Path: X-Original-To: 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 7E5D216A433 for ; Fri, 12 May 2006 03:36:04 +0000 (UTC) (envelope-from sean@mcneil.com) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFBD343D49 for ; Fri, 12 May 2006 03:36:03 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 4FDB9F280D; Thu, 11 May 2006 20:36:03 -0700 (PDT) X-Virus-Scanned: by amavisd-new at mcneil.com Received: from mail.mcneil.com ([127.0.0.1]) by localhost (triton.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JlKI8sx7DZHT; Thu, 11 May 2006 20:36:02 -0700 (PDT) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id C26C0F280B; Thu, 11 May 2006 20:36:02 -0700 (PDT) From: Sean McNeil To: Eric Anderson In-Reply-To: <4463EB9B.8070304@centtech.com> References: <1147384638.88133.4.camel@triton.mcneil.com> <4463EB9B.8070304@centtech.com> Content-Type: text/plain Date: Thu, 11 May 2006 20:36:01 -0700 Message-Id: <1147404961.34394.0.camel@triton.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: bluetooth@freebsd.org Subject: Re: Setting up a bluetooth mouse on FreeBSD 6 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: Fri, 12 May 2006 03:36:04 -0000 On Thu, 2006-05-11 at 20:57 -0500, Eric Anderson wrote: > Sean McNeil wrote: > >>From previous emails, I found: > > > > Eric Anderson's blog at > > http://destari.blogspot.com/2006/01/setting-up-bluetooth-mouse-on-freebsd.html > > > > I did this and my mouse works, but unfortunately the middle and right > > mouse buttons are reversed. This is a bluetooth mouse I got with my > > Acer Ferrari lapop. Movement isn't quite as smooth as a USB mouse > > either, but it isn't that bad. > > > > Another odd thing here is that bluetooth is enabled in the standard > > build of -CURRENT, but bthidd and bthidcontrol are not. Will these be > > added in anytime soon? > > There is a patch to bthidd (check gnats, but I've attached the one I > found) to fix that. I'm not sure what Max's plans are to commit or not, > but it's a needed patch for sure. > > I think (but I'm nobody) that bthidd and bthidcontrol should be enabled > on current for greater exposure, and then enabled on -STABLE. I've been > using it for quite some time, and it's been very solid. Yes, this patch fixed my problem. Thanks. Sean From owner-freebsd-bluetooth@FreeBSD.ORG Fri May 12 21:14:00 2006 Return-Path: X-Original-To: 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 446C216AF5F for ; Fri, 12 May 2006 21:14:00 +0000 (UTC) (envelope-from sean@mcneil.com) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id E054D43D58 for ; Fri, 12 May 2006 21:13:54 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 5AFD7F2814 for ; Fri, 12 May 2006 14:13:54 -0700 (PDT) X-Virus-Scanned: by amavisd-new at mcneil.com Received: from mail.mcneil.com ([127.0.0.1]) by localhost (triton.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DctLHBoM0hwu for ; Fri, 12 May 2006 14:13:53 -0700 (PDT) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 484E4F280B for ; Fri, 12 May 2006 14:13:53 -0700 (PDT) From: Sean McNeil To: bluetooth@freebsd.org Content-Type: text/plain Date: Fri, 12 May 2006 14:13:53 -0700 Message-Id: <1147468433.92729.0.camel@triton.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: hcsecd: Received unexpected HCI event 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: Fri, 12 May 2006 21:14:05 -0000 I get a ton of these. How can I fix it? hcsecd[846]: Received unexpected HCI event, event=0xff From owner-freebsd-bluetooth@FreeBSD.ORG Fri May 12 22:33:10 2006 Return-Path: X-Original-To: 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 964B316A573 for ; Fri, 12 May 2006 22:33:10 +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 4208D43D46 for ; Fri, 12 May 2006 22:33:10 +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 4E6693BE39; Fri, 12 May 2006 17:33:09 -0500 (CDT) 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 20631-01-27; Fri, 12 May 2006 17:33:09 -0500 (CDT) Received: from [10.254.186.111] (sntc04ep01.savvis.net [64.14.1.106]) by mailgate1b.savvis.net (Postfix) with ESMTP id A59303BE2A; Fri, 12 May 2006 17:33:08 -0500 (CDT) Message-ID: <44650D23.9030507@savvis.net> Date: Fri, 12 May 2006 15:33:07 -0700 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sean McNeil References: <1147468433.92729.0.camel@triton.mcneil.com> In-Reply-To: <1147468433.92729.0.camel@triton.mcneil.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at savvis.net Cc: bluetooth@freebsd.org Subject: Re: hcsecd: Received unexpected HCI event 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: Fri, 12 May 2006 22:33:11 -0000 Sean McNeil wrote: > I get a ton of these. How can I fix it? > > hcsecd[846]: Received unexpected HCI event, event=0xff please provide more information, i.e. 'uname -a', bluetooth device information and what are you trying to do. in theory, you should never get any of these, because hcsecd sets filter to only look for few events (and 0xff, i.e. vendor event is not included in the filter) max