Linux Input Archive on
 help / color / Atom feed
From: Swyter <>
To: Cameron Gutman <>,
	Dmitry Torokhov <>
	Benjamin Valentin <>
Subject: Re: [PATCH] Input: xpad: Remove a conflicting Razer Sabertooth using the VID/PID for the Razer DeathAdder 2013 mouse
Date: Fri, 31 Jul 2020 08:14:52 +0200
Message-ID: <> (raw)
In-Reply-To: <>

On 31/07/2020 7:54, Cameron Gutman wrote:
> On 7/30/20 8:44 AM, Ismael Ferreras Morezuelas wrote:
>> -	{ 0x1532, 0x0037, "Razer Sabertooth", 0, XTYPE_XBOX360 },
> The list here doesn't actually affect which devices that xpad will attach to.
> xpad_table[] is what determines the devices that xpad's probe() will be
> called for. It does this using the VID + vendor-defined interface subclass
> and interface number, not the VID+PID combos. xpad_device[] just provides a
> friendly name and quirk flags for some supported gamepads. Gamepads that
> aren't in the list will just show up as "Generic X-Box pad" with no quirk
> flags applied.
> If 1532:0037 is actually a mouse, it's unlikely we'd even reach the probe()
> in the first place. The device would lack the expected vendor-defined Xbox
> interface that is required for xpad to attach to the device.
> All that said, I'm definitely not opposed to removing the entry if it isn't
> a real gamepad. Given the difficulty you had finding information about this
> device, I take it you don't have any 'lsusb -v' output for this device, right?
> Regards,
> Cameron

Hi, Cameron. Yeah, the main idea is to clean the list, even if as you say it hasn't
caused mouse issues and that's why probably nobody has noticed it before.

Because, for some reason, everyone assumes some kind of correctness even when most of
these are community-sourced and self-reported, everyone copies these lists from
somewhere else. Hopefully the fixes will trickle downstream.

So yeah, I know for sure that (for example) the internal list Valve uses comes right from here:

(It's commented out)

Actual change referencing this kernel issue:

For more information of the device, take a look here:

You can see a lsusb dump here:

So yeah, let me know what you guys think. This has been a weird tangent for me. :)

  reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30 15:44 Ismael Ferreras Morezuelas
2020-07-31  5:54 ` Cameron Gutman
2020-07-31  6:14   ` Swyter [this message]
2020-08-02 22:50     ` Cameron Gutman

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux Input Archive on

Archives are clonable:
	git clone --mirror linux-input/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-input linux-input/ \
	public-inbox-index linux-input

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone