All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Dollinger <dollinger.florian@gmx.de>
To: Bastien Nocera <hadess@hadess.net>, andrew.smirnov@gmail.com
Cc: linux-kernel@vger.kernel.org,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	linux-input@vger.kernel.org
Subject: Re: hid: microsoft: Add rumble support for Xbox One S controller
Date: Thu, 27 Sep 2018 00:50:04 +0200	[thread overview]
Message-ID: <895230e5-05a8-68f4-5794-28e3d3068e81@gmx.de> (raw)
In-Reply-To: <75590dbdffee5870537a344209af185cdda5de30.camel@hadess.net>

> Sure it is, but:
> - it's not an "XBox One S controller", it's a variant of the "XBox One
> controller" shipped with the XBox One S.
> - we discussed this on the linux-bluetooth mailing-list in August 2016:
>    https://www.spinics.net/lists/linux-bluetooth/msg68102.html
>    revived the thread in 2017:
>    https://www.spinics.net/lists/linux-bluetooth/msg72750.html
>    and discussed the force feedback in particular in August this year:
>    https://www.spinics.net/lists/linux-input/msg57744.html
> - why would we look for a "driver" when there's already one in the
> kernel that supports all the xbox controllers except this one? :)
> 
> Really, as much as it's nice to find working code for this device, it's
> surprising you didn't contact any kernel developer before, rather than
> us having to find you.

Fair enough :)

> Yes, but that's not the way the drivers are usually arranged. They're
> arranged by vendors, so this driver would need to be merged into the
> "hid-microsoft.c" driver.

That's probably the main reason for not getting in touch earlier, I 
really don't like the idea of putting everything into the same driver 
just because it is the same vendor - or at leas the same name (even if 
Microsoft Xbox has nearly nothing to do with other parts of Microsoft).

> I'm pretty sure that the USB version can also be made to use HID.

I really don't think so, I already gave it a try. At least not "out of 
the box".

> I have no idea how the RF protocol would work though. I imagine it
> requires a dongle, or does it actually use Wi-Fi? (that would be
> surprising...).

In theory it does need one, but it is nothing more than normal Wi-Fi 
(2,4 and 5 GHz) - you can talk to the gamepad using any Wi-Fi card / 
stick you want. The problem is, that the connection is secured somehow.
If you are interested, take a look here: 
https://github.com/atar-axis/xpadneo/wiki/Microsoft-Xbox-One-Wireless-Adapter

> Anyway, I don't have much time to work on it right this minute, but it
> would be great if you could send your Bluetooth patch to start with,
> and we can iterate on that, and fix the other problems as we clear the
> priority list.

Jap, I will do that - Thank you so far!

> Cheers

Dito.

  reply	other threads:[~2018-09-26 22:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-10  0:17 [PATCH] hid: microsoft: Add rumble support for Xbox One S controller Andrey Smirnov
2018-08-10  9:36 ` Benjamin Tissoires
2018-08-13 14:25   ` Andrey Smirnov
2018-08-10 11:38 ` Bastien Nocera
2018-08-13 14:37   ` Andrey Smirnov
2018-08-13 14:52     ` Bastien Nocera
2018-09-26 12:51 ` Dollinger Florian
2018-09-26 13:45   ` Bastien Nocera
2018-09-26 15:15     ` AW: " dollinger.florian
2018-09-26 15:15       ` dollinger.florian
2018-09-26 18:02       ` Bastien Nocera
2018-09-26 22:50         ` Florian Dollinger [this message]
2018-09-26 16:09     ` XBox One S controller, Bluetooth support (was Re: hid: microsoft: Add rumble support for Xbox One S controller) Bastien Nocera
2018-09-26 17:43     ` Bastien Nocera
2018-09-26 22:35       ` Florian Dollinger
2018-09-26 15:23 hid: microsoft: Add rumble support for Xbox One S controller dollinger.florian
2018-09-26 15:23 ` dollinger.florian

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=895230e5-05a8-68f4-5794-28e3d3068e81@gmx.de \
    --to=dollinger.florian@gmx.de \
    --cc=andrew.smirnov@gmail.com \
    --cc=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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 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.