public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Richard Zidlicky  <Richard.Zidlicky@stud.informatik.uni-erlangen.de>
Cc: James Simmons <jsimmons@transvirtual.com>,
	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:55:38 +0100	[thread overview]
Message-ID: <20020201165538.A17286@suse.cz> (raw)
In-Reply-To: <Pine.LNX.4.10.10201311009140.23385-100000@www.transvirtual.com> <20020201011543.A476@linux-m68k.org>
In-Reply-To: <20020201011543.A476@linux-m68k.org>; from Richard.Zidlicky@stud.informatik.uni-erlangen.de on Fri, Feb 01, 2002 at 01:15:43AM +0100

On Fri, Feb 01, 2002 at 01:15:43AM +0100, Richard Zidlicky wrote:
> On Thu, Jan 31, 2002 at 10:19:46AM -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?
> 
> > +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.

Really? Too bad. So no way to set LEDs, no way to detect the keyboard,
no way to set it to "Scancode Set 3"?

We'll need to modify the atkbd driver then ... 

> > +static void q40kbd_interrupt(int irq, void *dev_id, struct pt_regs *regs)
> > +{
> > +	unsigned long flags;
> > +
> > +	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?

include/linux/serio.h: struct serio_dev

> > +void __init q40kbd_init(void)
> > +{
> > +	int maxread = 100;
> > +
> > +	/* Get the keyboard controller registers (incomplete decode) */
> > +	request_region(0x60, 16, "q40kbd");
> > +
> > +	/* allocate the IRQ */
> > +	request_irq(Q40_IRQ_KEYBOARD, keyboard_interrupt, 0, "q40kbd", NULL);
> 				      ^^^^^^^^^^^^^^^^^^
> should that be q40kbd_interrupt ?

Yes, it should.

-- 
Vojtech Pavlik
SuSE Labs

  parent reply	other threads:[~2002-02-01 15:56 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
2002-02-01 15:55   ` Vojtech Pavlik [this message]
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=20020201165538.A17286@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