All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Cole <tim.cole@canonical.com>
To: Stefan Bader <stefan.bader@canonical.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
	Sergey Kolesnikov <rockingdemon@gmail.com>,
	linux-input@vger.kernel.org,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: linux kernel HID problem with Saitek X52 Pro Flight System
Date: Fri, 11 Dec 2009 18:02:09 -0500	[thread overview]
Message-ID: <1260572529.3656.12.camel@bede> (raw)
In-Reply-To: <4B225601.3080002@canonical.com>

[-- Attachment #1: Type: text/plain, Size: 903 bytes --]

On Fri, 2009-12-11 at 15:24 +0100, Stefan Bader wrote:
> The problem moved though. For the older kernels it was the tablets that
> were incorrectly detected as joysticks. But that patch of you went upstream
> and now it is the one joystick model that does not work.
> In our tree we reverted the patch in Jaunty, but with Karmic we have the other
> behavior. So in essence, someone is always complaining. :-P

I know what you mean, but well -- ideally we want to converge on the
correct behavior.  Otherwise we'll just keep spinning and things stay
broken.

To my view, blacklisting a joystick which (wrongly) reports itself as a
digitizer tablet is an improvement over creating broken joystick devices
for anything that reports itself as a tablet.  From that position we can
fix the problem with the single device reporting the wrong device type
and then everyone can be happy.

-Tim

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-12-11 23:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bfb1bb1f0909061357m4006a61co1c1b4dfa483b947b@mail.gmail.com>
     [not found] ` <alpine.LNX.2.00.0909071731120.23856@wotan.suse.de>
     [not found]   ` <bfb1bb1f0909071047h1a4cbc3dx175f89ecedc3555d@mail.gmail.com>
2009-09-08 17:42     ` linux kernel HID problem with Saitek X52 Pro Flight System Jiri Kosina
2009-09-08 17:58       ` Dmitry Torokhov
2009-09-08 18:02         ` Jiri Kosina
     [not found]       ` <bfb1bb1f0909081304y708b037bw1c82288d6457c254@mail.gmail.com>
2009-09-08 20:49         ` Dmitry Torokhov
2009-09-08 22:43         ` Jiri Kosina
2009-12-10 17:31           ` Stefan Bader
2009-12-11 14:18             ` Tim Cole
2009-12-11 14:24               ` Stefan Bader
2009-12-11 23:02                 ` Tim Cole [this message]
2009-12-12  2:00                   ` Anssi Hannula
2009-12-12  4:44                     ` Dmitry Torokhov
2009-12-14 10:31                       ` Stefan Bader
2009-12-14 17:36                         ` Dmitry Torokhov
2009-12-15 12:58                           ` Jiri Kosina
2009-12-15 13:17                             ` Stefan Bader
2009-12-17  1:29                               ` Jiri Kosina
2009-12-17  1:38                                 ` Dmitry Torokhov
2009-12-18 15:10                                   ` Jiri Kosina
2009-12-18 17:49                                     ` Dmitry Torokhov
2009-12-22 13:31                                       ` Jiri Kosina
2009-12-23 18:55                                         ` Dmitry Torokhov
2010-01-04 11:17                                           ` 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=1260572529.3656.12.camel@bede \
    --to=tim.cole@canonical.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=rockingdemon@gmail.com \
    --cc=stefan.bader@canonical.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.