All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Simon Richter <Simon.Richter@phobos.fachschaften.tu-muenchen.de>,
	linux-m68k@lists.linux-m68k.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] amiga input api drivers
Date: Fri, 01 Feb 2002 01:09:40 +0100	[thread overview]
Message-ID: <3C59DCC4.EA3848E@linux-m68k.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10201311542370.5906-100000@www.transvirtual.com>

Hi,

James Simmons wrote:

> > > +   scancode = scancode >> 1;       /* lowest bit is release bit */
> > > +   down = scancode & 1;
> >
> > Shouldn't that be the other way 'round?
> 
> I don't know. Anyone?

He's correct, the up/down event is received in the lsb bit, the other 7
bits are the keycode.

bye, Roman

  parent reply	other threads:[~2002-02-01  0:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-31 15:14 [PATCH] amiga input api drivers James Simmons
2002-01-31 20:54 ` Geert Uytterhoeven
2002-02-01  7:14   ` Vojtech Pavlik
2002-02-01  9:11     ` Geert Uytterhoeven
2002-01-31 21:18 ` Simon Richter
2002-01-31 23:44   ` James Simmons
2002-01-31 23:56     ` Simon Richter
2002-02-01  0:09     ` Roman Zippel [this message]
2002-02-01  0:12       ` James Simmons
2002-02-01  0:22       ` [PATCH] amiga input api drivers III James Simmons
2002-02-01  9:18         ` Geert Uytterhoeven
2002-02-01  0:46       ` [PATCH] amiga input api drivers Simon Richter
2002-02-01  9:10         ` Geert Uytterhoeven
2002-02-13 18:01           ` James Simmons
2002-02-13 18:10             ` Simon Richter
2002-02-13 19:25               ` James Simmons
2002-02-14  6:53                 ` Horst von Brand
2002-02-14 20:29                   ` James Simmons
2002-02-13 18:14             ` Geert Uytterhoeven
2002-01-31 21:50 ` Roman Zippel
2002-01-31 23:05   ` James Simmons

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C59DCC4.EA3848E@linux-m68k.org \
    --to=zippel@linux-m68k.org \
    --cc=Simon.Richter@phobos.fachschaften.tu-muenchen.de \
    --cc=jsimmons@transvirtual.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.