To: linux-kernel@vger.kernel.org
Path: not-for-mail
From: Matthias Urlichs <smurf@smurf.noris.de>
Newsgroups: smurf.list.linux.kernel
Subject: Re: Raw I/O Problems with inb()
Date: Fri, 16 Jan 2004 18:41:25 +0100
Organization: {M:U} IT Consulting
Message-ID: <pan.2004.01.16.17.41.22.932043@smurf.noris.de>
References: <20040115215243.39fcb0fd.aftli@optonline.net> <pan.2004.01.16.11.27.43.359172@smurf.noris.de> <6.0.1.1.0.20040116094624.00acea40@optonline.net>
NNTP-Posting-Host: linux.smurf.noris.de
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
NNTP-Posting-Date: Fri, 16 Jan 2004 17:41:29 +0000 (UTC)
User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1012
Lines: 21

Hi, Brett Gmoser wrote:

> The question is not one of "how" to accomplish all of this, it is how to 
> get inb(0x64) to state that it is indeed mouse movement, and not keyboard 
> data, on an AMD Athlon XP system with PS/2 mouse.

Well, as I said, I would solve the "how" problem with a kernel module
which monitors mouse movement or keyboard events. This happens to be a
whole lot more reliable, and it will also eat no CPU time when nothing's
happening.

Plus, it will work on any mouse or keyboard. People actually _use_ USB
critters these days, you know ...

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
Sign my PETITION.
		-- Zippy the Pinhead

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/