From owner-freebsd-usb@FreeBSD.ORG Wed Jan 30 22:26:45 2013 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 01485AE1 for ; Wed, 30 Jan 2013 22:26:45 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id DF18DA77 for ; Wed, 30 Jan 2013 22:26:44 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id r0UMQc9o027772; Wed, 30 Jan 2013 14:26:39 -0800 (PST) (envelope-from yuri@rawbw.com) Message-ID: <51099E1E.1010107@rawbw.com> Date: Wed, 30 Jan 2013 14:26:38 -0800 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130129 Thunderbird/17.0.2 MIME-Version: 1.0 To: Hans Petter Selasky Subject: Re: Why my USB keyboard doesn't generate scancodes? References: <5104974C.803@rawbw.com> <201301301025.20211.hselasky@c2i.net> <5108E788.6010401@rawbw.com> <201301301040.54478.hselasky@c2i.net> In-Reply-To: <201301301040.54478.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-usb@freebsd.org X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 22:26:45 -0000 On 01/30/2013 01:40, Hans Petter Selasky wrote: > Work for you: > > RID=22 (0x16) is the one you are receiving. This is a microsoft specific extension to the HID class. > I don't have time to look at this right now, but if you can get documentation for this HID usage, then > we could map it to a mouse button at least. Else press all the buttons on your mouse while recording USB > trace information. Then reverse engineer the values, make a nice table and I can implement it for you in > the ums driver. So the keyboard signal comes to the mouse endpoint. One possible solution is to have a quirk in ums driver that would post the event to the corresponding ukbd instance. Since these are really the keyboard signals. Microsoft makes some of the best mice today (IMO, based on the research of what's available from all vendors). That's why I want FreeBSD to support their mice better. I will do some research, also will try to partially reverse-engineer the protocol. It might be something in their protocol that makes keyboard signals be piped into the mouse pipe. Yuri