From: Valdis.Kletnieks@vt.edu
To: Jiri Kosina <jkosina@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
Dmitry Torokhov <dtor@mail.ru>
Subject: Re: 2.6.28-rc4-mmotm1110 shift-lock oddness
Date: Mon, 17 Nov 2008 21:36:11 -0500 [thread overview]
Message-ID: <18584.1226975771@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 18 Nov 2008 01:26:51 +0100." <alpine.LRH.1.10.0811180125150.3104@twin.jikos.cz>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
On Tue, 18 Nov 2008 01:26:51 +0100, Jiri Kosina said:
> First, we'd need a little bit more information about the hardware in
> question, I guess.
Dell Latitude D820 laptop, with a USB-connected Microsoft Natural keyboard. I
don't think it's the USB subsystem going *completely* bonkers, as the
USB-connected trackball mouse functions just fine when this happens...
> What laptop is that, please? Is the keyboard PS/2-connected or
> USB-connected? Could you obtain evtest output from the buggy cases please?
Hmm.. Got a pointer to a usable copy? The best I could find googling for
'linux evtest' was:
https://svn.openwrt.org/openwrt/packages/utils/event_test/src/evtest.c
which wants a /dev/inputN - all I have is /dev/input/ and entries under that
for the laptop's onboard mousepad and the trackball mouse, no keyboard entry.
Hmm part two:
% zgrep EVDEV /proc/config.gz
# CONFIG_INPUT_EVDEV is not set
Should I be looking at rebuilding the kernel with this =m?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2008-11-18 2:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5397.1226959015@turing-police.cc.vt.edu>
2008-11-18 0:23 ` 2.6.28-rc4-mmotm1110 shift-lock oddness Andrew Morton
2008-11-18 0:26 ` Jiri Kosina
2008-11-18 2:36 ` Valdis.Kletnieks [this message]
2008-11-18 9:37 ` Jiri Kosina
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=18584.1226975771@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=dtor@mail.ru \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--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