Date: Fri, 16 Jan 2004 21:12:52 -0500
From: Brett Gmoser <aftli@optonline.net>
Subject: Re: [linuxkernel] Re: Raw I/O Problems with inb()
In-reply-to: <pan.2004.01.16.17.41.22.932043@smurf.noris.de>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: linux-kernel@vger.kernel.org
Message-id: <20040116211252.6581fb0f.aftli@optonline.net>
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
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>
 <pan.2004.01.16.17.41.22.932043@smurf.noris.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1117
Lines: 26

Thanks very much for your insight.  I do appreciate it.

I do agree that the next step will be to write a kernel module.  However, I would like to see if it is feasible to do this with inb(), since I see no very easy way around the fact that I do not want the program to work remotely.

Really, the question boils down to this: Is the keyboard status port on AMD systems 0x64, or is it something else?  If so, what is it?

Thank you!

Brett

On Fri, 16 Jan 2004 18:41:25 +0100
Matthias Urlichs <smurf@smurf.noris.de> wrote:

> 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 ...
> 
-
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/