linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Anssi Hannula <anssi.hannula@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: multi-input quirk and skip output reports quirk
Date: Tue, 1 Apr 2008 16:12:16 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0804011610450.5541@jikos.suse.cz> (raw)
In-Reply-To: <47F21BA7.8030306@gmail.com>

On Tue, 1 Apr 2008, Anssi Hannula wrote:

> I've encountered another multi-input device that needs the skip output
> reports quirk (as it contains force feedback output reports), 0925:8866.
> However, maybe we should use another approach, dropping
> HID_QUIRK_SKIP_OUTPUT_REPORTS. Why not just *not* register the input
> device for that report in case the report didn't contain anything that
> was mapped by hidinput_configure_usage(), in hidinput_connect()?

Hi Anssi,

as long as we still have the possibility to see the coming data in debug 
mode, I don't have objection to that.

Are you going to make that patch?

Thanks,

-- 
Jiri Kosina

  reply	other threads:[~2008-04-01 14:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 11:25 multi-input quirk and skip output reports quirk Anssi Hannula
2008-04-01 14:12 ` Jiri Kosina [this message]
2008-04-01 14:15   ` Anssi Hannula
2008-04-04 14:37     ` Jiri Kosina
2008-04-04 14:40       ` Anssi Hannula
2008-04-04 14:51         ` Jiri Kosina
2008-04-06  8:06 ` Jiri Kosina
2008-04-06 14:12   ` Anssi Hannula
  -- strict thread matches above, loose matches on Subject: below --
2008-04-05  6:01 Sam Liddicott
2008-04-05  6:01 ` Jiri Kosina
2008-04-05  6:16 Sam Liddicott

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.0804011610450.5541@jikos.suse.cz \
    --to=jkosina@suse.cz \
    --cc=anssi.hannula@gmail.com \
    --cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).