All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Justin Opini <opinijm@provdh.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	 torvalds@linux-foundation.org, "Luke D. Jones" <luke@ljones.dev>
Subject: Re: Mismatched product ids for the ASUS ROG RAIKIRI PRO
Date: Tue, 19 May 2026 14:18:56 -0700	[thread overview]
Message-ID: <agzSfM3TH8Pg0M4I@google.com> (raw)
In-Reply-To: <20260519173800.6765-1-opinijm@provdh.com>

Hi Justin,

On Tue, May 19, 2026 at 01:37:59PM -0400, Justin Opini wrote:
> Hey Dimity,
> 
> I had a question on the product id,
> { 0x0b05, 0x1abb, "ASUS ROG RAIKIRI PRO", 0, XTYPE_XBOXONE },
> 
> This doesn’t match both my devices so I was wondering if somehow we
> have similar named devices with need for different product ids or if
> there was a mistake in the original commit?
> 
> My relevant entries from lsusb are 
> Bus 001 Device 002: ID 0b05:1a3c ASUSTek Computer, Inc. ROG RAIKIRI PRO
> Bus 001 Device 003: ID 0b05:1a3c ASUSTek Computer, Inc. ROG RAIKIRI PRO
> 
> On my system I have ended up using this udev rule for quite some time
> ACTION=="add", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="1a3c", GROUP="input", MODE="0660", TAG+="uaccess", TAG+="seat", RUN+="/bin/sh -c 'echo 0b05 1a3c > /sys/bus/usb/drivers/xpad/new_id'"

I am CC-ing Luke who added this VID/PID comboi to double check, but it
looks like there are many variants of this controller using the same
"ROG RAIKIRI PRO" name. For example
https://github.com/atar-axis/xpadneo/issues/612 talks about
0x0b05/0x1abd.

Thanks.

-- 
Dmitry

  reply	other threads:[~2026-05-19 21:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-05  3:25 [git pull] Input updates for v6.9-rc6 Dmitry Torokhov
2024-05-05 17:12 ` pr-tracker-bot
2026-05-19 17:37 ` Mismatched product ids for the ASUS ROG RAIKIRI PRO Justin Opini
2026-05-19 21:18   ` Dmitry Torokhov [this message]
2026-05-20 19:06     ` opinijm
2026-05-20 19:13       ` opinijm

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=agzSfM3TH8Pg0M4I@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.dev \
    --cc=opinijm@provdh.com \
    --cc=torvalds@linux-foundation.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.