From owner-freebsd-current@FreeBSD.ORG  Fri May  9 09:10:26 2003
Return-Path: <owner-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 9D82037B40F
	for <freebsd-current@freebsd.org>;
	Fri,  9 May 2003 09:10:26 -0700 (PDT)
Received: from mail48.fg.online.no (mail48-s.fg.online.no [148.122.161.48])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 394AA43FAF
	for <freebsd-current@freebsd.org>;
	Fri,  9 May 2003 09:10:25 -0700 (PDT)
	(envelope-from sigsegv@leakingmemory.org)
Received: from radiotube.homeunix.org (ti531210a080-0419.bb.online.no
	[80.213.105.163])
	by mail48.fg.online.no (8.9.3p2/8.9.3) with ESMTP id SAA06864
	for <freebsd-current@freebsd.org>;
	Fri, 9 May 2003 18:10:22 +0200 (MEST)
From: Jan-Espen Pettersen <sigsegv@leakingmemory.org>
To: freebsd-current@freebsd.org
Date: Fri, 9 May 2003 18:10:21 +0200
User-Agent: KMail/1.5
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305091810.21687.sigsegv@leakingmemory.org>
Subject: Labtec 4D+ mouse wont work with moused
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: sigsegv@leakingmemory.org
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 09 May 2003 16:10:27 -0000

Well, this mouse sends out 0x00 instead of 0xFF when a negative X-Axis
movement is performed. And does also report 0x00 instead of 0xFF when a
positive Y-Axis movement does occur.

A normal PS/2 mouse is using the range 0xFF to 0x80 or 0x00 (?) to report
negative X-Axis movements. But the Labtec 4D+ mouse uses the oposite range:
0x00 to 0xFF (where (X-Axis) 0x00 means a movement of -1, and 0x01 means -2,
...). The values are also reversed on positive Y-Axis movement.

Labtec 4D+ PS/2 mouse:
X-Axis positive: 0x00 to 0xFF or 0x7F (?) (0x00 = +1 or 0, not sure)
X-Axis negative:0x00 to 0xFF (?) (0x00 = -1)
Y-Axis positive: 0x00 to 0xFF (?) (0x00 = +1 or 0)
Y-Axis negative: 0x00 to 0xFF (?) (0x00 = -1)

A normal PS/2 mouse:
X-Axis positive: 0x00 to 0xFF (?) (0x00 = +1 or 0)
X-Axis negative: 0xFF to 0x00 or 0x80 (?) (0xFF = -1)
Y-Axis positive: 0xFF to 0x00 (?) (0xFF = +1)
Y-Axis negative: 0x00 to 0xFF (?) (0x00 = +1)

Well, that was what I was able to read out of the debugging output from
moused. As you can see, I'm not completely sure about all the max and minimum
values.

The Labtec mouse worked after applying this patch:

http://www.leakingmemory.org/moused_05_08_2003/moused.c.patch

and starting moused manually:

# moused -t ps/2