From: "Zephaniah E\. Hull" <warp@babylon.d2dc.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] Problem with mousedev.c
Date: Wed, 30 Oct 2002 11:21:51 -0500 [thread overview]
Message-ID: <20021030162151.GB27563@babylon.d2dc.net> (raw)
In-Reply-To: <20021030171117.A12597@ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
On Wed, Oct 30, 2002 at 05:11:17PM +0100, Vojtech Pavlik wrote:
> The patch is quite OK, it should not report BTN_BACK to userspace,
> though, and also it should not depend on the hid-input.c assigning
> BTN_BACK to the button which specifies the wheel.
Hrm, it does not report BTN_BACK events, but it is present in the bit
mask, however we could refuse to set the bit if the quirk is present.
As far as not depending on the BTN_BACK being assigned as such, I'm not
quite sure how to tell the event handler which one to use without
an additional field somewhere.
That said, I have not gotten my head around the entirety of the HID
layer, so I could very easily be missing something obvious.
--
1024D/E65A7801 Zephaniah E. Hull <warp@babylon.d2dc.net>
92ED 94E4 B1E6 3624 226D 5727 4453 008B E65A 7801
CCs of replies from mailing lists are requested.
<Mercury> Knghtbrd: Eww, find a better name, the movie sucked.. <G>
<Knghtbrd> Mercury: The engine is better than the movie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-10-30 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-27 1:05 Zephaniah E. Hull
2002-10-28 13:27 ` Petr Vandrovec
2002-10-28 17:00 ` Zephaniah E. Hull
2002-10-28 17:40 ` Vojtech Pavlik
2002-10-30 15:32 ` Zephaniah E. Hull
2002-10-30 15:59 ` Vojtech Pavlik
2002-10-30 16:04 ` Zephaniah E. Hull
2002-10-30 16:11 ` Vojtech Pavlik
2002-10-30 16:21 ` Zephaniah E. Hull [this message]
2002-10-30 16:46 Petr Vandrovec
2002-10-30 18:37 ` Zephaniah E. Hull
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=20021030162151.GB27563@babylon.d2dc.net \
--to=warp@babylon.d2dc.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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®