From: "Denilson Figueiredo de Sá" <denilsonsa@gmail.com>
To: Chris Friesen <chris.friesen@genband.com>
Cc: linux-kernel@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Linux USB HID should ignore values outside Logical Minimum/Maximum range
Date: Tue, 25 Oct 2011 02:03:50 -0200 [thread overview]
Message-ID: <op.v3v2wozfdsdv5o@localhost> (raw)
In-Reply-To: <CACGt9ymGUAzjkZJCePnO+7cyKsi8-rtpno9ebjKtoCXj-tCALg@mail.gmail.com>
On Mon, 24 Oct 2011 14:39:31 -0200, Denilson Figueiredo de Sá wrote:
> On Mon, Oct 24, 2011 at 14:24, Chris Friesen wrote:
>> On 10/22/2011 05:42 AM, Denilson Figueiredo de Sá wrote:
>>
>>> It may even happen to send an out-of-range value for one axis, but a
>>> valid value for another axis. The code should be prepared for that
>>> (ignore one, but keep the other).
>>
>> In this case what should be used for the "invalid" axis value? The
>> previous value?
> I haven't tested that on Windows (yet), so I don't know how it
> behaves. If I test it, I'll post my results here.
I've modified the firmware of my device to do some more tests. I've
modified it to send invalid values in X axis, but keep Y axis with valid
values.
In Linux, the pointer moved to the right-most position of the screen
(which is consistent with the behavior I previously described), not
ignoring the out-of-range value.
In Windows, the pointer moved to the left-most position of the screen. It
means Windows can't send a movement of only one axis, and fills the other
axis with zero when receiving an invalid value. This behavior doesn't seem
very helpful.
If anyone cares, this was the firmware modification for this test:
https://bitbucket.org/denilsonsa/atmega8-magnetometer-usb-mouse/changeset/31027323fa0b
--
Denilson Figueiredo de Sá
Rio de Janeiro - Brasil
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-10-25 4:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-22 11:42 Linux USB HID should ignore values outside Logical Minimum/Maximum range Denilson Figueiredo de Sá
2011-10-24 16:24 ` Chris Friesen
2011-10-24 16:39 ` Denilson Figueiredo de Sá
2011-10-24 20:35 ` Dmitry Torokhov
2011-10-25 4:03 ` Denilson Figueiredo de Sá [this message]
2011-10-24 17:09 ` Christoph Fritz
2011-10-24 17:04 ` Denilson Figueiredo de Sá
2011-10-24 20:32 ` Dmitry Torokhov
2011-10-28 16:23 ` Jiri Kosina
2011-10-28 19:27 ` Christoph Fritz
2011-10-28 20:40 ` Denilson Figueiredo de Sá
2011-10-31 15:24 ` Jiri Kosina
2011-11-02 23:39 ` Denilson Figueiredo de Sá
2011-11-16 14:01 ` Jiri Kosina
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=op.v3v2wozfdsdv5o@localhost \
--to=denilsonsa@gmail.com \
--cc=chris.friesen@genband.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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).