From: Bastien Nocera <hadess@hadess.net>
To: Roderick Colenbrander <thunderbird2k@gmail.com>,
Martyn Welch <martyn@welchs.me.uk>
Cc: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-input <linux-input@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Conn O'Griofa <connogriofa@gmail.com>,
"Colenbrander, Roelof" <roderick.colenbrander@sony.com>
Subject: Re: [PATCH] HID: Sony: Add support for Gasia controllers
Date: Thu, 06 Feb 2020 10:14:17 +0100 [thread overview]
Message-ID: <6ed9447de70d49289ded71751e57923d0c4ab3b4.camel@hadess.net> (raw)
In-Reply-To: <CAEc3jaB9ubRLJJG9eWL8-QnEU1s-6cOYsY-PKd57e_K9BiPkSA@mail.gmail.com>
On Tue, 2020-01-28 at 22:22 -0800, Roderick Colenbrander wrote:
> As you can see this creates an awkward situation. I'm sure there
> other
> such devices as well e.g. counterfeit Logitech keyboards, USB serial
> adapters and other periperhals with similar challenges. In an ideal
> world the support would live in another driver, but since in case of
> this "fake" PS3 controller it "share" our product / vendor ids it is
> tricky. At this point there is not a strong enough case yet to
> augment
> the "hid-quirks" to do so, but perhaps if it became a serious issue
> (e.g. for newer controllers) maybe we need to think of something.
I'm pretty certain that the only reason why those use "fake" VID/PID
combinations is because that's the only thing the consoles will
accept.
That's par for the course when you try to close off your ecosystem that
those that try to enter it will use the means at their disposal to do
that.
prev parent reply other threads:[~2020-02-06 9:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-26 19:45 [PATCH] HID: Sony: Add support for Gasia controllers Martyn Welch
2020-01-27 22:07 ` Roderick Colenbrander
2020-01-28 10:11 ` Jiri Kosina
2020-01-29 6:08 ` Roderick Colenbrander
2020-01-28 18:47 ` Martyn Welch
2020-01-29 6:22 ` Roderick Colenbrander
2020-02-03 10:02 ` Jiri Kosina
2020-02-03 10:48 ` Benjamin Tissoires
2020-02-03 11:22 ` Jiri Kosina
2020-02-06 8:09 ` Benjamin Tissoires
2020-02-06 9:34 ` Bastien Nocera
2020-02-09 5:04 ` Roderick Colenbrander
2020-02-06 15:30 ` Roderick Colenbrander
2020-02-06 17:45 ` Benjamin Tissoires
2020-02-06 9:14 ` Bastien Nocera [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=6ed9447de70d49289ded71751e57923d0c4ab3b4.camel@hadess.net \
--to=hadess@hadess.net \
--cc=benjamin.tissoires@redhat.com \
--cc=connogriofa@gmail.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martyn@welchs.me.uk \
--cc=roderick.colenbrander@sony.com \
--cc=thunderbird2k@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;
as well as URLs for NNTP newsgroup(s).