public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Stelian Pop <stelian.pop@fr.alcove.com>,
	Vojtech Pavlik <vojtech@suse.cz>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: input subsystem config ?
Date: Thu, 18 Jul 2002 17:31:32 +0200	[thread overview]
Message-ID: <20020718173132.A30621@ucw.cz> (raw)
In-Reply-To: <20020718152829.GD2326@tahoe.alcove-fr>; from stelian.pop@fr.alcove.com on Thu, Jul 18, 2002 at 05:28:29PM +0200

On Thu, Jul 18, 2002 at 05:28:29PM +0200, Stelian Pop wrote:
> On Thu, Jul 18, 2002 at 05:15:31PM +0200, Vojtech Pavlik wrote:
> 
> > > If I do not disable the 'return -1', the mouse will not be found at
> > > all, and moving it will get no messages in the logs...
> > 
> > Ok, that's what I wanted to know - I was wondering whether the mouse
> > would simply ignore all control commands. And it doesn't not. It needs
> > the commands, 
> 
> I'm not sure about that. It will not work if I do not disable the
> 'return -1' because the irq will get freed, so the driver will have
> no chance to get any mouse event.

Actually, no. It also polls the chip repeatedly without needing an irq,
so it can receive bytes even when no irq happens.

> > but doesn't send any replies.
> 
> Maybe I should put some debug statements in the pc_keyb.c interrupt
> handler and see if the mouse does answer the control commands ?

That's a good idea, yes.

> > Can you check what happens if you use an external mouse together with
> > the internal one?
> >
> > I suspect both will work OK.
> 
> External like in 'external PS/2' mouse ? Bad luck, this laptop 
> has no PS/2 (or serial) port. :-(

Ok.

> I can plug in a USB mouse, but I doubt it will show any useful
> information...

No, it won't.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-07-18 15:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-16 14:34 input subsystem config ? Stelian Pop
2002-07-17  9:56 ` Stelian Pop
2002-07-17 10:01   ` Vojtech Pavlik
2002-07-17 10:10     ` Stelian Pop
2002-07-17 12:08       ` Vojtech Pavlik
2002-07-17 13:24         ` Stelian Pop
2002-07-17 13:44           ` Vojtech Pavlik
2002-07-17 13:58             ` Stelian Pop
2002-07-17 14:29               ` Vojtech Pavlik
2002-07-17 14:55                 ` Stelian Pop
2002-07-17 15:22                   ` Vojtech Pavlik
2002-07-17 15:33                     ` Stelian Pop
2002-07-18 14:41                       ` Stelian Pop
2002-07-18 14:45                         ` Vojtech Pavlik
2002-07-18 14:48                           ` Stelian Pop
2002-07-18 15:15                             ` Vojtech Pavlik
2002-07-18 15:28                               ` Stelian Pop
2002-07-18 15:31                                 ` Vojtech Pavlik [this message]
2002-07-18 16:02                                   ` Stelian Pop
2002-07-19 14:36                                   ` Stelian Pop
2002-07-19 19:32                                     ` Vojtech Pavlik

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=20020718173132.A30621@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stelian.pop@fr.alcove.com \
    /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