From: Daniel Barkalow <barkalow@iabervon.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
linux-kernel@vger.kernel.org,
Christopher Desjardins <cddesjardins@gmail.com>
Subject: Re: Lenovo 3000 N100 i8042 problems
Date: Tue, 2 Sep 2008 12:16:15 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.1.00.0809021200470.19665@iabervon.org> (raw)
In-Reply-To: <20080902083940.ZZRA012@mailhub.coreip.homeip.net>
On Tue, 2 Sep 2008, Dmitry Torokhov wrote:
> On Tue, Sep 02, 2008 at 11:23:25AM +0200, Jiri Kosina wrote:
> >
> > so the product name both of System and Base Board are different, and
> > apparently the systems differ. Dmitry, what fields would you propose to be
> > put in the DMI matching here? I will do the patch then.
> >
>
> I guess we could use System's product name to differentiate between
> Cristopher's and Daniel's boards. Although I must admit it is the very
> first time when I see a box that behaves better with active mux. DOes
> Vista use active mux nowadays? Because if it is not then I bet there
> is (or shortly will be) a BIOS update fixing legacy mode on Daniel's
> box.
Mine's actually old (came with XP). It's still got the original BIOS
(because I haven't found a way to upgrade the BIOS without reformatting my
hard drive to include Windows), and I remember there being an upgrade
available, but I don't think it had anything to do with keyboard/trackpad
stuff.
In what way does active mux usually behave badly? It's possible that
legacy mode only has a bug that doesn't matter to Windows, and active mux
may have some of the usual problems but nothing I particularly noticed.
I noticed that, when my i8042 would stop working, it would generally have
just delivered one mouse interrupt to CPU1 after never previously doing
so. Perhaps there's some sort of deadlock in the Linux i8042 driver when
both cores are unexpectedly getting interrupts from the two devices at
once? I could understand there being a Linux bug only triggered by quirky
hardware that only applies to legacy mode, which was just uncovered by
this patch.
-Daniel
*This .sig left intentionally blank*
next prev parent reply other threads:[~2008-09-02 16:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 21:46 Daniel Barkalow
2008-09-01 23:29 ` Jiri Kosina
2008-09-02 0:23 ` Daniel Barkalow
2008-09-02 9:23 ` Jiri Kosina
2008-09-02 12:43 ` Henrique de Moraes Holschuh
2008-09-02 12:51 ` Dmitry Torokhov
2008-09-02 12:43 ` Dmitry Torokhov
2008-09-02 16:16 ` Daniel Barkalow [this message]
2008-09-03 14:26 ` Dmitry Torokhov
2008-09-03 17:16 ` Daniel Barkalow
2008-09-03 19:06 ` Dmitry Torokhov
2008-09-03 20:03 ` Jiri Kosina
2008-09-05 0:05 ` Daniel Barkalow
2008-09-05 0:46 ` Dmitry Torokhov
2008-09-05 3:27 ` Daniel Barkalow
2008-09-03 11:50 ` Jiri Kosina
2008-09-03 14:20 ` Dmitry Torokhov
2008-09-03 17:18 ` Daniel Barkalow
2008-09-03 19:07 ` Dmitry Torokhov
2008-09-04 23:57 ` Daniel Barkalow
2008-09-03 21:32 ` Henrique de Moraes Holschuh
2008-09-03 21:36 ` Jiri Kosina
2008-09-03 22:03 ` Daniel Barkalow
2008-09-08 19:41 ` Renato S. Yamane
2008-09-08 19:55 ` Daniel Barkalow
2008-09-09 3:35 ` Renato S. Yamane
2008-09-09 3:42 ` Henrique de Moraes Holschuh
2008-09-09 13:37 ` Renato S. Yamane
2008-09-08 20:24 ` Henrique de Moraes Holschuh
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=alpine.LNX.1.00.0809021200470.19665@iabervon.org \
--to=barkalow@iabervon.org \
--cc=cddesjardins@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®