From owner-freebsd-bluetooth@FreeBSD.ORG Wed May 3 02:27:45 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 47D3216A409 for ; Wed, 3 May 2006 02:27:45 +0000 (UTC) (envelope-from Alex.Kovalenko@verizon.net) Received: from vms044pub.verizon.net (vms044pub.verizon.net [206.46.252.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0391243D45 for ; Wed, 3 May 2006 02:27:45 +0000 (GMT) (envelope-from Alex.Kovalenko@verizon.net) Received: from RabbitsDen ([70.21.164.5]) by vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IYO0061T45XQUO9@vms044.mailsrvcs.net> for bluetooth@freebsd.org; Tue, 02 May 2006 21:27:43 -0500 (CDT) Date: Tue, 02 May 2006 22:27:22 -0400 From: "Alexandre \"Sunny\" Kovalenko" To: bluetooth@freebsd.org Message-id: <1146623242.877.12.camel@RabbitsDen> MIME-version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port Content-type: text/plain; charset=iso-8859-5 Content-transfer-encoding: 8BIT Cc: Subject: Apple bluetooth keyboard -- quote key does not generate character 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: Wed, 03 May 2006 02:27:45 -0000 Here is hcidump output for two neigbouring keys (colon/semicolon works and single quote/double quote does not) -- one of them produces character that propagates all the way to the consumer and one does not. I have tested this keyboard with iBook and both keys work perfectly. > ACL data: handle 0x002a flags 0x02 dlen 15 L2CAP(d): cid 0x41 len 11 [psm 0] A1 01 00 00 33 00 00 00 00 00 00 ;> ACL data: handle 0x002a flags 0x02 dlen 15 L2CAP(d): cid 0x41 len 11 [psm 0] A1 01 00 00 00 00 00 00 00 00 00 > ACL data: handle 0x002a flags 0x02 dlen 15 L2CAP(d): cid 0x41 len 11 [psm 0] A1 01 00 00 34 00 00 00 00 00 00 > ACL data: handle 0x002a flags 0x02 dlen 15 L2CAP(d): cid 0x41 len 11 [psm 0] A1 01 00 00 00 00 00 00 00 00 00 Any suggestions would be greatly appreciated. --- Alexandre Kovalenko (Олександр Коваленко). From owner-freebsd-bluetooth@FreeBSD.ORG Wed May 3 02:33:54 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 637FF16A402 for ; Wed, 3 May 2006 02:33:54 +0000 (UTC) (envelope-from Alex.Kovalenko@verizon.net) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E96F43D4C for ; Wed, 3 May 2006 02:33:54 +0000 (GMT) (envelope-from Alex.Kovalenko@verizon.net) Received: from RabbitsDen ([70.21.164.5]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IYO00GA04GHVAQH@vms046.mailsrvcs.net> for bluetooth@freebsd.org; Tue, 02 May 2006 21:33:53 -0500 (CDT) Date: Tue, 02 May 2006 22:33:41 -0400 From: "Alexandre \"Sunny\" Kovalenko" In-reply-to: <1146623242.877.12.camel@RabbitsDen> To: bluetooth@freebsd.org Message-id: <1146623621.877.15.camel@RabbitsDen> MIME-version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port Content-type: text/plain; charset=iso-8859-5 Content-transfer-encoding: 8BIT References: <1146623242.877.12.camel@RabbitsDen> Cc: Subject: Re: Apple bluetooth keyboard -- quote key does not generate character 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: Wed, 03 May 2006 02:33:54 -0000 On Tue, 2006-05-02 at 22:27 -0400, Alexandre "Sunny" Kovalenko wrote: > Here is hcidump output for two neigbouring keys (colon/semicolon works > and single quote/double quote does not) -- one of them produces > character that propagates all the way to the consumer and one does not. > I have tested this keyboard with iBook and both keys work perfectly. > > > ACL data: handle 0x002a flags 0x02 dlen 15 > L2CAP(d): cid 0x41 len 11 [psm 0] > A1 01 00 00 33 00 00 00 00 00 00 > ;> ACL data: handle 0x002a flags 0x02 dlen 15 > L2CAP(d): cid 0x41 len 11 [psm 0] > A1 01 00 00 00 00 00 00 00 00 00 > > ACL data: handle 0x002a flags 0x02 dlen 15 > L2CAP(d): cid 0x41 len 11 [psm 0] > A1 01 00 00 34 00 00 00 00 00 00 > > ACL data: handle 0x002a flags 0x02 dlen 15 > L2CAP(d): cid 0x41 len 11 [psm 0] > A1 01 00 00 00 00 00 00 00 00 00 > > Any suggestions would be greatly appreciated. > > --- > Alexandre Kovalenko (Олександр Коваленко). > > _______________________________________________ > freebsd-bluetooth@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth > To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@freebsd.org" My apology to the list -- system in question is current as of about 00:30 EST on the May 2. I have been using it without external keyboard for a while, but I am pretty much sure that it has been working as of beginning of April. -- Alexandre Kovalenko (Олександр Коваленко) From owner-freebsd-bluetooth@FreeBSD.ORG Sat May 6 20:04:30 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 3C80E16A402 for ; Sat, 6 May 2006 20:04:30 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from mail03.svc.cra.dublin.eircom.net (mail03.svc.cra.dublin.eircom.net [159.134.118.19]) by mx1.FreeBSD.org (Postfix) with SMTP id A541043D46 for ; Sat, 6 May 2006 20:04:28 +0000 (GMT) (envelope-from plunky@rya-online.net) Received: (qmail 92030 messnum 272636 invoked from network[83.70.176.191/unknown]); 6 May 2006 20:04:27 -0000 Received: from unknown (HELO rya-online.net) (83.70.176.191) by mail03.svc.cra.dublin.eircom.net (qp 92030) with SMTP; 6 May 2006 20:04:27 -0000 Received: (nullmailer pid 740 invoked by uid 1000); Sat, 06 May 2006 20:01:58 -0000 Date: Sat, 6 May 2006 21:01:58 +0100 (BST) To: Maksim Yevmenkin In-Reply-To: <4445206D.4030109@savvis.net> References: <4423D096.2010205@udc.es> <44248823.3040907@savvis.net> <1145275616.851775.858.nullmailer@galant.ukfsn.org> <4445206D.4030109@savvis.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1146945718.380438.1055.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: Sat, 06 May 2006 20:04:30 -0000 On Tue, 18 Apr 2006, Maksim Yevmenkin wrote: > 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! 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. 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. 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. iain