From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Jiri Kosina <jkosina@suse.cz>,
linux-kernel@vger.kernel.org,
Christopher Desjardins <cddesjardins@gmail.com>
Subject: Re: Lenovo 3000 N100 i8042 problems
Date: Wed, 3 Sep 2008 15:07:50 -0400 [thread overview]
Message-ID: <20080903150649.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <alpine.LNX.1.00.0809031317080.19665@iabervon.org>
On Wed, Sep 03, 2008 at 01:18:23PM -0400, Daniel Barkalow wrote:
> On Wed, 3 Sep 2008, Dmitry Torokhov wrote:
>
> > On Wed, Sep 03, 2008 at 01:50:35PM +0200, Jiri Kosina wrote:
> > > On Tue, 2 Sep 2008, Dmitry Torokhov wrote:
> > >
> > > > 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.
> > >
> > > I guess so, yes.
> > >
> > > On the other hand, this might also be viewed as regression (we made
> > > Daniel's hardware behave worse with recent kernel than it did before), so
> > > I think we still would like to have this fixed. What about the patch
> > > below, adding the match on System's product name, as you suggested?
> > > Thanks.
> > >
> >
> > I agree. Daniel, could you please try the patch to make sure it
> > restores the previous behavior for you and I will push it through.
> >
> > Thanks!
>
> I'll test that Thursday as well; is there some quick way to determine
> whether you're using active mux or not?
Do "dmesg | grep serio".. If you see 4 AUX ports being created then
KBC is in active multiplexing mode.
--
Dmitry
next prev parent reply other threads:[~2008-09-03 19:08 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
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 [this message]
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=20080903150649.ZZRA012@mailhub.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=barkalow@iabervon.org \
--cc=cddesjardins@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®