From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 23:23:49 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 517EC16A420 for ; Tue, 3 Jan 2006 23:23:49 +0000 (GMT) (envelope-from psionic@csh.rit.edu) Received: from blacksheep.csh.rit.edu (blacksheep.csh.rit.edu [129.21.60.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3321343D91 for ; Tue, 3 Jan 2006 23:23:23 +0000 (GMT) (envelope-from psionic@csh.rit.edu) Received: from localhost (localhost [127.0.0.1]) by blacksheep.csh.rit.edu (Postfix) with ESMTP id 775A6254F for ; Tue, 3 Jan 2006 18:23:20 -0500 (EST) Received: from blacksheep.csh.rit.edu ([127.0.0.1]) by localhost (blacksheep.csh.rit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 486196-08 for ; Tue, 3 Jan 2006 18:23:20 -0500 (EST) Received: from fury.csh.rit.edu (fury.csh.rit.edu [IPv6:2001:470:1f00:135:a00:20ff:fe8d:5399]) by blacksheep.csh.rit.edu (Postfix) with ESMTP id 2F96726C9 for ; Tue, 3 Jan 2006 18:23:20 -0500 (EST) Received: from fury.csh.rit.edu (localhost [127.0.0.1]) by fury.csh.rit.edu (Postfix) with ESMTP id E097D1560 for ; Tue, 3 Jan 2006 18:23:19 -0500 (EST) From: Jordan Sissel To: freebsd-current@freebsd.org Date: Tue, 03 Jan 2006 18:23:19 -0500 Sender: psionic@csh.rit.edu Message-Id: <20060103232319.E097D1560@fury.csh.rit.edu> X-Virus-Scanned: amavisd-new at csh.rit.edu Subject: usb mouse support update plans 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: Tue, 03 Jan 2006 23:23:49 -0000 On my grande circuit of trying to make mouse support better for FreeBSD, I've finally come about to working on usb mice. I've done a bit of research about usb hid, and I need some feedback on where I should take usb mouse support. In case you didn't read my previous post about a new moused and psm driver: The reengineered psm(4) exists to provide moused with a userland interface for talking to the mouse. Thusly, all functionality (specific mouse support) is provided through userland drivers. Back to usb mice... I've been playing some with usbhidctl(1) and usbhidaction(1) aswell as perusing the ums(4) sourcecode. It looks like ums(4) just talks uhid (looking up hid usage pages, etc). Turns out you can do this from the userland aswell. The immediate question is should I follow my psm work by turning usb mouse support into a userland driver for moused? That is, ums(4) would go away and usb mouse support would be provided by moused alone. Alternatively, instead of tossing out ums, I could work on fixing it so known-broken mice work properly with it. USB HID seems to be a very set standard, though some manufs decide to provide nonstandard data in hid usage pages. Moral of this story is that I want to make known-broken mice work with FreeBSD. This includes *several* Microsoft USB models, many ps/2 mice (including usb->ps2 adapted mice), and probably others. I'm willing to do either option for ums - turn it into a userland driver for moused or just fix what's broken with it as is. Either way, I need to know what mice don't work properly. Ideally going for a more unified mouse driver structure (userland moused drivers, for example) would be best in my opinion. How can you help? If you are having issues with mouse support in FreeBSD I need to know the following: - Mouse model and brand (as specific as possible would help) - Symptoms of strange behavior - Environment (moused+ums? plain ums in X? plain psm in X? moused with serial mice?) Thanks, -Jordan