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: Wed, 17 Jul 2002 17:22:35 +0200 [thread overview]
Message-ID: <20020717172235.A20474@ucw.cz> (raw)
In-Reply-To: <20020717145523.GJ14581@tahoe.alcove-fr>; from stelian.pop@fr.alcove.com on Wed, Jul 17, 2002 at 04:55:23PM +0200
On Wed, Jul 17, 2002 at 04:55:23PM +0200, Stelian Pop wrote:
> On Wed, Jul 17, 2002 at 04:29:04PM +0200, Vojtech Pavlik wrote:
>
> > > I should enhance however that it works with the old pc_keyb driver.
> >
> > Yes, I know. That's why I suggested skipping the detection, as the
> > pc_keyb driver doesn't do that.
> >
> > Try this:
> >
> > --- i8042.c.old Wed Jul 17 16:05:57 2002
> > +++ i8042.c Wed Jul 17 16:27:54 2002
> > @@ -571,6 +571,8 @@
> >
> > i8042_flush();
> >
> > +#if 0
> [...]
>
> Argh, with this patch, the mouse still doesn't work but I also
> lose the keyboard (but keyboard press/release events are
> however present in the logs...)!
>
> [...]
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> hda: 23579136 sectors w/512KiB Cache, CHS=23392/16/63, UDMA(33)
> hda: [PTBL] [1467/255/63] hda1 hda2 hda3 < hda5 hda6 >
> mice: PS/2 mouse device common for all mice
> i8042.c: fa <- i8042 (flush, kbd) [0]
> i8042.c: 20 -> i8042 (command) [0]
> i8042.c: 47 <- i8042 (return) [0]
> i8042.c: 60 -> i8042 (command) [1]
> i8042.c: 56 -> i8042 (parameter) [1]
> i8042.c: a8 -> i8042 (command) [1]
> i8042.c: 60 -> i8042 (command) [1]
> i8042.c: 56 -> i8042 (parameter) [1]
> serio: i8042 AUX port at 0x60,0x64 irq 12
> i8042.c: 60 -> i8042 (command) [1]
> i8042.c: 46 -> i8042 (parameter) [1]
> serio: i8042 KBD port at 0x60,0x64 irq 1
> NET4: Linux TCP/IP 1.0 for NET4.0
> [...]
> i8042.c: 39 <- i8042 (interrupt, kbd, 0) [96160]
> i8042.c: b9 <- i8042 (interrupt, kbd, 0) [96260]
> i8042.c: 39 <- i8042 (interrupt, kbd, 0) [97310]
> i8042.c: b9 <- i8042 (interrupt, kbd, 0) [97410]
> i8042.c: 39 <- i8042 (interrupt, kbd, 0) [102010]
> i8042.c: b9 <- i8042 (interrupt, kbd, 0) [102110]
Are you sure you didn't change the config? Because this really looks
like if noone is actually even trying to probe. Which is quite
impossible, unless CONFIG_KEYBOARD_ATKBD and CONFIG_MOUSE_PS2 are
disabled.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-07-17 15:19 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 [this message]
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
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=20020717172235.A20474@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