public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Richard Zidlicky 
	<Richard.Zidlicky@stud.informatik.uni-erlangen.de>,
	linux-m68k@lists.linux-m68k.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Q40 input api support.
Date: Fri, 1 Feb 2002 16:57:03 +0100	[thread overview]
Message-ID: <20020201165703.B17286@suse.cz> (raw)
In-Reply-To: <20020201011543.A476@linux-m68k.org> <Pine.LNX.4.10.10201311631100.6830-100000@www.transvirtual.com>
In-Reply-To: <Pine.LNX.4.10.10201311631100.6830-100000@www.transvirtual.com>; from jsimmons@transvirtual.com on Thu, Jan 31, 2002 at 04:39:11PM -0800

On Thu, Jan 31, 2002 at 04:39:11PM -0800, James Simmons wrote:

> > > This patch ports q40 PS/2 controller support over to the input api. Please
> > > try it out. It is against the latest dave jones tree.
> > 
> > thanks, I will look at this over the weekend. Where do I get the DJ
> > tree?
> 
> ftp://ftp.kernel.org/pub/linux/kernel/people/davej/patches/2.5
> 
> 
> > > +static inline void q40kbd_write(unsigned char val)
> > > +{
> > > +	/* FIXME! We need a way how to write to the keyboard! */
> > > +}
> > 
> > absolutely no way to write to the keyboard.
> 
> That solves that.

It doesn't. atkbd.c won't detect the keyboard if it can't talk to it.

> > > +	if (IRQ_KEYB_MASK & master_inb(INTERRUPT_REG))
> > > +		if (q40kbd_port.dev)
> > > +                         q40kbd_port.dev->interrupt(&q40kbd_port, master_inb(KEYCODE_REG), 0);
> >                                              ^^^^^^^^^
> > where is this defined?
> 
> The way it works with the new input code is that it modularized the
> keyboard/mice from the controller chipsets. This file, q40kbd.c is the 
> file to sets up the controller chip. For the Q40 we have this as for the
> ix86 we have i8042.c. As for the mouse and keyboard driver themselves you
> pick PS/2 mouse support and AT keyboard support. These drivers are the
> same ones as the ix86 drivers for the mice and keyboard. In theory they
> should work on both platforms. Note the check for dev. This field is
> filled in when we register the keyboard if it is present.
> 
> > > +	/* allocate the IRQ */
> > > +	request_irq(Q40_IRQ_KEYBOARD, keyboard_interrupt, 0, "q40kbd", NULL);
> > 				      ^^^^^^^^^^^^^^^^^^
> > should that be q40kbd_interrupt ?
> 
> Yes. Fixed. 

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-02-01 15:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-31 18:19 [PATCH] Q40 input api support James Simmons
2002-01-31 18:47 ` Info on dn_keyb.c James Simmons
2002-01-31 20:57 ` [PATCH] Q40 input api support Geert Uytterhoeven
2002-01-31 23:12   ` James Simmons
2002-01-31 23:48     ` [PATCH] amiga keyboard input II James Simmons
2002-02-01  9:13       ` Geert Uytterhoeven
2002-01-31 23:14   ` Atari keyboard? James Simmons
2002-02-01  7:15     ` Vojtech Pavlik
2002-02-01 11:50     ` Michael Schmitz
2002-02-01  0:15 ` [PATCH] Q40 input api support Richard Zidlicky
2002-02-01  0:39   ` James Simmons
2002-02-01 15:57     ` Vojtech Pavlik [this message]
2002-02-01 15:55   ` Vojtech Pavlik
2002-02-01 19:43     ` Richard Zidlicky
2002-02-01 19:45       ` Vojtech Pavlik
2002-02-01 20:23         ` Richard Zidlicky

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=20020201165703.B17286@suse.cz \
    --to=vojtech@suse.cz \
    --cc=Richard.Zidlicky@stud.informatik.uni-erlangen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox