From: Vojtech Pavlik <vojtech@suse.cz>
To: Matheus Izvekov <mizvekov@gmail.com>
Cc: linux-kernel@vger.kernel.org, dtor_core@ameritech.net
Subject: Re: usbkbd not reporting unknown keys
Date: Sat, 22 Apr 2006 23:53:56 +0200 [thread overview]
Message-ID: <20060422215356.GA11798@suse.cz> (raw)
In-Reply-To: <305c16960604221401k4e6493b6xa9c898a92c6b028d@mail.gmail.com>
On Sat, Apr 22, 2006 at 06:01:27PM -0300, Matheus Izvekov wrote:
> On 4/22/06, Vojtech Pavlik <vojtech@suse.cz> wrote:
> > Just point me to the HID debug logs. (I need DEBUG enabled in both
> > hid-core.c and hid-input.c.) Make sure you're running an uptodate
> > kernel. I'll see what is needed to fix the mappings for that keyboard.
> >
> > > Maybe the thread subject should be changed to something more
> > > apropriate, do so if it pleases you.
>
> Here it is, hope i got everything right.
It seems to be missing something at the top, also the whitespace
formatting seems to be discarded - everything is aligned to the first
column, making it rather hard to read. Please retry using 'dmesg -s 131072'.
--
Vojtech Pavlik
Director SuSE Labs
next prev parent reply other threads:[~2006-04-22 21:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 19:30 usbkbd not reporting unknown keys Matheus Izvekov
2006-03-08 20:25 ` Matheus Izvekov
2006-03-08 20:47 ` Dmitry Torokhov
2006-03-08 21:34 ` Matheus Izvekov
2006-03-09 13:43 ` Dmitry Torokhov
2006-03-09 20:30 ` Matheus Izvekov
[not found] ` <305c16960603141510g72def22bmd0043d5f71d9ef6@mail.gmail.com>
2006-03-14 23:23 ` Matheus Izvekov
2006-04-22 18:11 ` Matheus Izvekov
2006-04-22 18:54 ` Vojtech Pavlik
2006-04-22 19:59 ` Matheus Izvekov
2006-04-22 20:04 ` Vojtech Pavlik
2006-04-22 21:01 ` Matheus Izvekov
2006-04-22 21:53 ` Vojtech Pavlik [this message]
2006-04-22 22:28 ` Matheus Izvekov
2006-04-23 6:58 ` Vojtech Pavlik
2006-04-23 14:00 ` Matheus Izvekov
2006-04-23 14:16 ` 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=20060422215356.GA11798@suse.cz \
--to=vojtech@suse.cz \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mizvekov@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.