From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH][RFC] input: remove bios I8042_CTR_XLATE check to make keyboard usable
Date: Wed, 28 Oct 2009 20:26:33 -0700 [thread overview]
Message-ID: <20091029032633.GA7959@core.coreip.homeip.net> (raw)
In-Reply-To: <20091029003325.GA2739@darkstar.vlan7>
On Thu, Oct 29, 2009 at 08:33:26AM +0800, Dave Young wrote:
> On Wed, Oct 28, 2009 at 06:42:12PM +0800, Dave Young wrote:
> > On Wed, Oct 28, 2009 at 11:03:18AM +0100, Vojtech Pavlik wrote:
> > > On Tue, Oct 27, 2009 at 10:43:10PM -0700, Dmitry Torokhov wrote:
> > > > Hi Dave,
> > > >
> > > > On Tue, Oct 27, 2009 at 01:34:04PM +0800, Dave Young wrote:
> > > > >
> > > > > Pressing somekey at early booting phase cause keyboard to be not usable
> > > > > (The hardware is DELL latitude e5400):
> > >
> > > Does early booting mean while the BIOS is coming up? Does the keyboard
> > > work in GRUB then? Or is it during the early init of the Linux kernel?
> >
> > Keyboard work under lilo.
> > For the early booting I means the early init of the linux kernel
> >
> > >
> > > > > atkbd.c: Unknown key pressed (raw set 2, code 0xd3 on isa0060/serio0).
> > > > > atkbd.c: Use 'setkeycodes e053 <keycode>' to make it known.
> > > > > atkbd.c: Unknown key pressed (raw set 2, code 0x1d3 on isa0060/serio0).
> > > > > atkbd.c: Use 'setkeycodes e053 <keycode>' to make it known.
> > > > >
> > > > > i8042.c set i8042_direct to true when the controller init. But the result
> > > > > is keyboard not usable, The only option is press the power button to shutdown.
> > > > >
> > > > > So here remove the bios check to fix it.
> > >
> > > My question would be: Why this happens? Could it be that the probe is
> > > confused by the keypress and reads the CTR incorrectly? Or is it just
> > > that the keyboard controller is in fact in translating mode, yet the CTR
> > > indicates otherwise?
> > >
> > > A i8042.debug=1 log of the bad init would be good.
> >
> > Here it is (retrieve from syslog):
>
> Syslog redirect the debug info to another log file, sorry, post again:
>
Any chance of reconfiguring syslog so debug is captured in the same
file? It is easier to see what is happening with the rest of context
present...
--
Dmitry
next prev parent reply other threads:[~2009-10-29 3:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 5:34 [PATCH][RFC] input: remove bios I8042_CTR_XLATE check to make keyboard usable Dave Young
2009-10-28 5:43 ` Dmitry Torokhov
2009-10-28 10:03 ` Vojtech Pavlik
2009-10-28 10:42 ` Dave Young
2009-10-29 0:33 ` Dave Young
2009-10-29 3:26 ` Dmitry Torokhov [this message]
2009-10-29 7:15 ` Dave Young
2009-11-01 8:33 ` Dave Young
2009-11-02 7:47 ` Dmitry Torokhov
2009-11-02 10:49 ` Dave Young
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=20091029032633.GA7959@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=hidave.darkstar@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).