linux-kernel - Re: [RESEND PATCH] Support Xbox One controllers in xpad driver.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140817162022.GA17367@core.coreip.homeip.net>
Date:	Sun, 17 Aug 2014 09:20:22 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Ted Mielczarek <ted@...lczarek.org>
Cc:	linux-input@...r.kernel.org, paul.gortmaker@...driver.com,
	hor27@...il.com, petr@...soft.com, magissia@...issia.com,
	linux-kernel@...r.kernel.org
Subject: Re: [RESEND PATCH] Support Xbox One controllers in xpad driver.

On Fri, Aug 08, 2014 at 10:46:09AM -0400, Ted Mielczarek wrote:
> Xbox One controllers require an initialization message to start sending data,
> so xpad_init_output becomes a required function. The Xbox One controller does
> not have LEDs like the Xbox 360 controller, so that functionality is not
> implemented. The format of messages controlling rumble is currently
> undocumented, so rumble support is not yet implemented.
> 
> The only thing I'm not certain about in this patch is the check against bInterfaceNumber in xpad_probe. The Xbox One controller advertises three interfaces with the same interface class, subclass and protocol, and I couldn't see any way to match just the first one using usb_device_id.
> 
> Signed-off-by: Ted Mielczarek <ted@...lczarek.org>

Applied, thank you.

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/