Date: Thu, 21 Aug 2003 14:26:25 +0200
From: Vojtech Pavlik <vojtech@suse.cz>
To: John Bradford <john@grabjohn.com>
Cc: aebr@win.tue.nl, macro@ds2.pg.gda.pl, jamie@shareable.org,
       linux-kernel@vger.kernel.org, neilb@cse.unsw.edu.au, vojtech@suse.cz
Subject: Re: Input issues - key down with no key up
Message-ID: <20030821122625.GB20748@ucw.cz>
References: <200308211211.h7LCBrdf000281@81-2-122-30.bradfords.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200308211211.h7LCBrdf000281@81-2-122-30.bradfords.org.uk>
User-Agent: Mutt/1.5.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1095
Lines: 27

On Thu, Aug 21, 2003 at 01:11:53PM +0100, John Bradford wrote:

> >  Note the translation is done outside the keyboard -- the onboard 8042
> > controller is responsible for it.
> 
> How do we currently handle devices connected via bit-banging on the
> parallel port,(as we have no onboard 8042 in that case)?

You write a 'serio' driver for those keyboards - a driver which will do
the bit-banging on the parallel port and send bytes from and to the
device. See the parkbd.c module for that.

The keyboard/mouse driver always sees the bytes that are on the wire,
regardless whether there is an 8042 inbetween - in that case the 8042
driver tries to undo the damage caused by translation.

This way we can have a single atkbd.c driver for any at-style keyboard
attached over whatever interface is in the machine.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR
-
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/