linux-kernel - Re: [PATCH 0/1] Input: xpad - add disable

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-next>] [day] [month] [year] [list]

Message-ID: <ogmv67n3rdia67ttj6whj4wnr2humhl2fjpo56phghqf67bpjx@bbdmdsmbp4kk>
Date: Mon, 19 May 2025 14:36:32 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Apoorv Parle <apparle@...il.com>
Cc: linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/1] Input: xpad - add disable_xboxone module parameter

On Mon, May 19, 2025 at 01:30:13PM -0700, Apoorv Parle wrote:
> The goal is to not blacklist the xpad driver completely, because I still
> need that driver for other controllers (older Xbox 360 controller or 3rd
> party controllers) when using multiple controllers (couch multiplayer) on
> the same machine.
> 
> Today I'm forced to blacklist xpad altogether to get xone up because they
> conflict on the device IDs, and then I can only use 1 controller, not both.
> Or I have to create a copy of xpad with Xbox-One device IDs stripped out
> (i.e. xpad-noone) to keep both drivers active side-by-side, so my new
> XboxOne can use xone and my old Xbox 360 can use the xpad driver.
> This patch is trying to make that seamless. And it'll have the added
> benefit of making distro packaging easier as xpad can just stay upstream
> with no separate builds needed, and xone driver can be a non-free opt-in
> installation with this module param enabled.

I understand. However you can unbind and bind individual devices to
individual drivers via sysfs by writing into
/sys/bus/usb/drivers/{xpad|xone}/{un}bind.

Thanks.

-- 
Dmitry