All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: James Simmons <jsimmons@transvirtual.com>,
	Vojtech Pavlik <vojtech@ucw.cz>,
	Linux/m68k <linux-m68k@lists.linux-m68k.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] amiga input api drivers
Date: Fri, 1 Feb 2002 08:14:42 +0100	[thread overview]
Message-ID: <20020201081442.G15571@suse.cz> (raw)
In-Reply-To: <Pine.LNX.4.10.10201310712130.20956-100000@www.transvirtual.com> <Pine.GSO.4.21.0201312153250.24581-100000@vervain.sonytel.be>
In-Reply-To: <Pine.GSO.4.21.0201312153250.24581-100000@vervain.sonytel.be>; from geert@linux-m68k.org on Thu, Jan 31, 2002 at 09:54:51PM +0100

On Thu, Jan 31, 2002 at 09:54:51PM +0100, Geert Uytterhoeven wrote:
> On Thu, 31 Jan 2002, James Simmons wrote:
> >   The amiga mouse and amiga joystick have been already ported over to the
> > input api. Now for the keyboard. This patch is the input api amiga
> > keyboard. I wanted people to try it out before I send it off to be
> > included in the DJ tree. Have fun!!!
> 
> > diff -urN -X /home/jsimmons/dontdiff linux-2.5.2-dj7/drivers/input/keyboard/amikbd.c linux/drivers/input/keyboard/amikbd.c
> > --- linux-2.5.2-dj7/drivers/input/keyboard/amikbd.c	Wed Dec 31 16:00:00 1969
> > +++ linux/drivers/input/keyboard/amikbd.c	Thu Jan 31 07:44:05 2002
> 
> > +static char *amikbd_messages[] = {
> > +	KERN_ALERT "amikbd: Ctrl-Amiga-Amiga reset warning!!\n",
> > +	KERN_WARNING "amikbd: keyboard lost sync\n",
> > +	KERN_WARNING "amikbd: keyboard buffer overflow\n",
> > +	KERN_WARNING "amikbd: keyboard controller failure\n",
> > +	KERN_ERR "amikbd: keyboard selftest failure\n",
> > +	KERN_INFO "amikbd: initiate power-up key stream\n",
> > +	KERN_INFO "amikbd: terminate power-up key stream\n",
> > +	KERN_WARNING "amikbd: keyboard interrupt\n"
> > +};
> 
> > +	if (scancode < 0x78) {		/* scancodes < 0x78 are keys */
> 
>   [...]
> 
> > +	}
> > +
> > +	printk(amikbd_messages[scancode]);	/* scancodes >= 0x78 are error codes */
> 
> Oops, amikbd_messages[scancode-0x78]?

Thanks. And thanks to James for fixing this in the CVS as well.
Does it work otherwise?

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-02-01  7:15 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 [this message]
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
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=20020201081442.G15571@suse.cz \
    --to=vojtech@suse.cz \
    --cc=geert@linux-m68k.org \
    --cc=jsimmons@transvirtual.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=vojtech@ucw.cz \
    /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.