mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Jiri Kosina" <jikos@jikos.cz>
Cc: "Islam Amer" <pharon@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: USB remote control missing keycodes
Date: Wed, 13 Jun 2007 11:17:30 -0400	[thread overview]
Message-ID: <d120d5000706130817v5b9291d4h8653ade63882d2bc@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706131654180.23280@twin.jikos.cz>

On 6/13/07, Jiri Kosina <jikos@jikos.cz> wrote:
> On Wed, 13 Jun 2007, Islam Amer wrote:
>
> > back ( not working )
> > [  829.897373] drivers/hid/hid-core.c: report (size 5) (numbered)
> > [  829.897380] drivers/hid/hid-core.c: report 4 (size 4) =  fa 00 00 00
> > [  829.897389] hid-debug: input Consumer.0000 = 0
> [...]
> > txt ( not working )
> > [  900.156751] drivers/hid/hid-core.c: report (size 5) (numbered)
> > [  900.156762] drivers/hid/hid-core.c: report 5 (size 4) =  5a 00 00 00
> > [  900.156771] hid-debug: input ffbc.0000 = 0
> > [  900.156781] hid-debug: input ffbc.005a = 1
>
> Oh my, another 'creative' vendor :( We really desperately need the
> hidbus, so that we could handle those misbehaving vendors in cleaner
> way, I am constantly moving that up in my todo :)
>

Actually this one does not need hidbus and can be easily handled from
userspace now that we have setkeycodes support for HID.

-- 
Dmitry

  reply	other threads:[~2007-06-13 15:17 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 10:13 ext2 on flash memory DervishD
2007-06-11 11:11 ` Eduard-Gabriel Munteanu
2007-06-11 11:57   ` USB remote control missing keycodes Islam Amer
2007-06-11 15:02     ` Jiri Kosina
2007-06-13 14:08       ` Islam Amer
2007-06-13 14:58         ` Jiri Kosina
2007-06-13 15:17           ` Dmitry Torokhov [this message]
2007-06-13 15:44             ` Jiri Kosina
2007-06-13 15:58               ` Islam Amer
2007-06-13 16:17                 ` Jiri Kosina
2007-06-14 12:19                   ` Islam Amer
2007-06-14 12:30                     ` Jiri Kosina
2007-06-15 10:15                       ` Jiri Kosina
2007-06-15 10:51                         ` Jiri Kosina
2007-06-17 10:57                           ` Islam Amer
2007-06-18 11:42                             ` Jiri Kosina
2007-06-15 17:55     ` Phillip Susi
2007-06-11 17:36   ` ext2 on flash memory DervishD
2007-06-13 13:16     ` Ph. Marek
2007-06-13 23:02       ` DervishD
2007-06-14  5:16         ` Ph. Marek
2007-06-11 14:58 ` alan
2007-06-11 17:42   ` DervishD
2007-06-11 19:27     ` Juergen Beisert
2007-06-13 13:48       ` DervishD
2007-06-14 19:36         ` Jan Knutar
2007-06-14 20:07           ` DervishD
2007-06-11 23:53 ` Kevin K
2007-06-12  0:35   ` Kevin Bowling
2007-06-12  1:18     ` Bernd Eckenfels
2007-06-13 13:44       ` DervishD
2007-06-12  7:53     ` Juergen Beisert
2007-06-12 13:29       ` Eduard-Gabriel Munteanu
2007-06-12 16:46       ` Eduard-Gabriel Munteanu
2007-06-13 13:43   ` DervishD
2007-06-12 21:09 ` Jason Lunz
2007-06-13  6:49   ` Juergen Beisert
2007-06-14 17:45 ` Jörn Engel
2007-06-14 18:22   ` Jörn Engel
2007-06-14 20:20     ` DervishD
2007-06-14 20:43       ` Jörn Engel
2007-06-15 16:20         ` DervishD
2007-06-15 16:27           ` Jörn Engel
2007-06-14 20:17   ` DervishD
2007-06-14 20:38     ` Jörn Engel
2007-06-15 16:16       ` DervishD
2007-06-15 16:36         ` Jörn Engel

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=d120d5000706130817v5b9291d4h8653ade63882d2bc@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=jikos@jikos.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pharon@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 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®