From owner-freebsd-current@FreeBSD.ORG Sat Mar 14 23:38:58 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23D8D106566C for ; Sat, 14 Mar 2009 23:38:58 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe13.tele2.se [212.247.155.129]) by mx1.freebsd.org (Postfix) with ESMTP id B0D788FC26 for ; Sat, 14 Mar 2009 23:38:57 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=LBigvjnqffgA:10 a=kRQOYpJDzpgA:10 a=BexJqdt_jRo_e7eSpNcA:9 a=ID1KkkBQ8TnndFWgRkkcsvtGYX8A:4 a=LY0hPdMaydYA:10 Received: from [193.217.167.198] (account mc467741@c2i.net HELO [10.0.0.188]) by mailfe13.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 820352792; Sun, 15 Mar 2009 00:23:55 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Sun, 15 Mar 2009 00:26:26 +0100 User-Agent: KMail/1.9.7 References: <200903141506.59058.hselasky@c2i.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200903150026.26912.hselasky@c2i.net> Cc: Ian FREISLICH Subject: Re: Apple touchpad no longer works with usb2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2009 23:38:58 -0000 On Saturday 14 March 2009, Ian FREISLICH wrote: > Hans Petter Selasky wrote: > > On Saturday 14 March 2009, Ian FREISLICH wrote: Hi, The X-axis byte is being decoded like the Y-axis byte, so the data buffer is shifted down by one byte. What are the location numbers printed when you have hw.usb2.ums.debug set to 15 right after attach? Can you gzip your /sys/dev/usb ? I suspect you have some sources out of sync, because according to my test parsing of the HID descriptor the coordiates are at the correct place in the USB packet, but your ums driver is doing it wrong. Are you sure you did a clean build? > ums_intr_callback:191: data = 02 00 01 03 00 00 00 00 > ums_intr_callback:264: x:0 y:-1 z:0 t:0 w:0 buttons:0x00000001 My test parsing with latest -current code. 0x00010030,8,8,1 8,8,1 rid=2 flags=0x00000006 0x00010031,16,8,1 16,8,1 rid=2 flags=0x00000006 --HPS