Linux Input/HID development
 help / color / mirror / Atom feed
From: Przemo Firszt <przemo@firszt.eu>
To: Ping Cheng <pinglinux@gmail.com>
Cc: jkosina@suse.cz, linux-input@vger.kernel.org,
	linuxwacom-devel <linuxwacom-devel@lists.sourceforge.net>
Subject: Re: [PATCH] HID: wacom: Remove raport header check.
Date: Tue, 15 May 2012 19:30:07 +0100	[thread overview]
Message-ID: <1337106607.22228.7.camel@pldmachine> (raw)
In-Reply-To: <CAF8JNhJozNYzTbEHXHbr2mkOBH-RqxzeFqFWNbTXBLo6oYQppg@mail.gmail.com>

Dnia 2012-05-14, pon o godzinie 13:21 -0700, Ping Cheng pisze:
> On Mon, May 14, 2012 at 9:13 AM, Przemo Firszt <przemo@firszt.eu> wrote:
> > That check was valid when hid-wacom was only supporting Wacom Graphire, as the
> > device raports always start with 0x03. Intuos4 WL high-speed raports
> > begin with 0x04, so the check would be filtering out valid reports.
> 
> I assume the if-statement was added on purpose. It was most likely
> used to filter noises for Graphire.
> 
> Should we change to
> 
> if (data[0] != 0x03 || (data[0] != 0x04 &&
>     hdev->product == USB_DEVICE_ID_WACOM_INTUOS4_BLUETOOTH)) {
> 
>         hid_err(hdev, "Unknown report: %d,%d size:%d\n",
> 					data[0], data[1], size);
>         return 0;
> }
> 
> and remove default case for I4?
> 
> Or, remove the if-statement as you suggested and add a default case
> for Graphire to post hid_err and exit when data[0] != 3.
> 
> Either way works for me.
Hi Ping,
Thanks for the comment. I'll go with the second option and I hope we
won't be generating too much noise in the logs :-)

Patches (there are 2 more for speed setting through sysfs for I4 WL) on
the way...
-- 
Regards,
Przemo Firszt <przemo@firszt.eu>


      reply	other threads:[~2012-05-15 18:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 16:13 [PATCH] HID: wacom: Remove raport header check Przemo Firszt
2012-05-14 20:21 ` Ping Cheng
2012-05-15 18:30   ` Przemo Firszt [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=1337106607.22228.7.camel@pldmachine \
    --to=przemo@firszt.eu \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linuxwacom-devel@lists.sourceforge.net \
    --cc=pinglinux@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