linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-input@vger.kernel.org
Subject: Re: Patch to add NOGET for DMI/Acomdata
Date: Thu, 20 Mar 2008 09:58:23 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0803200955500.30831@jikos.suse.cz> (raw)
In-Reply-To: <20080319165132.f831c344.zaitcev@redhat.com>

On Wed, 19 Mar 2008, Pete Zaitcev wrote:

> To tell you the truth, I just now noticed that the button does not
> work. Kernel prints this:
> hiddev96hidraw0: USB HID v1.10 Device [DMI      WD5000AAKB-00UKA] on usb-0000:00:13.5-3
> But then the events do not get delivered. This is what happens
> with DEBUG enabled in hid-core.c:
> usb 2-3.2: new high speed USB device using address 3
>   INPUT[INPUT]
>     Field(0)
>       Usage(2)
>         ffa0.00a6
>         ffa0.00a7
>       Logical Minimum(-128)
>       Logical Maximum(127)
>       Report Size(8)
>       Report Count(2)
>       Report Offset(0)
>       Flags( Variable Absolute )

Hi Pete,

yes, so the device doesn't provide any application we handle in HID <-> 
input mapping, it contains only vendor-speicific usages from 0xffa0 page.

hiddev/hidraw device surely is created for this device (as it is not 
handled by hid-input), so a userspace driver can be written easily to 
handle this button.

So your patch makes sense, I will apply it to my tree, thanks.

-- 
Jiri Kosina
SUSE Labs

      reply	other threads:[~2008-03-20  8:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 22:43 Patch to add NOGET for DMI/Acomdata Pete Zaitcev
2008-03-19 23:11 ` Jiri Kosina
2008-03-19 23:51   ` Pete Zaitcev
2008-03-20  8:58     ` Jiri Kosina [this message]

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=Pine.LNX.4.64.0803200955500.30831@jikos.suse.cz \
    --to=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=zaitcev@redhat.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;
as well as URLs for NNTP newsgroup(s).