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: Sun, 23 Apr 2006 08:58:18 +0200 [thread overview]
Message-ID: <20060423065818.GA12611@suse.cz> (raw)
In-Reply-To: <305c16960604221528i2407e2d5nb8aa97c011246e71@mail.gmail.com>
On Sat, Apr 22, 2006 at 07:28:39PM -0300, Matheus Izvekov wrote:
> > 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'.
> Ok, fixed it, using dmesg now (had to increase the printk shift so it
> wouldnt throw things out)
Yes, this one looks much better.
The keyboard part of the device is OK, but the multimedia/mouse part is
totally FUBAR. Adding support for any keys that are not making it
through should be trivial, but making it not appear as a crazy joystick
is not realistically possible: The device insists on that it IS a device
from hell with almost all possible valuators defined in the HID spec.
--
Vojtech Pavlik
Director SuSE Labs
next prev parent reply other threads:[~2006-04-23 6:58 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
2006-04-22 22:28 ` Matheus Izvekov
2006-04-23 6:58 ` Vojtech Pavlik [this message]
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=20060423065818.GA12611@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.