* [git pull] Input updates for v6.9-rc6
@ 2024-05-05 3:25 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
0 siblings, 2 replies; 6+ messages in thread
From: Dmitry Torokhov @ 2024-05-05 3:25 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, linux-input
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git tags/input-for-v6.9-rc6
to receive updates for the input subsystem. You will get:
- a new ID for ASUS ROG RAIKIRI controllers added to xpad driver
- amimouse driver structure annotated with __refdata to prevent section
mismatch warnings.
Changelog:
---------
Uwe Kleine-König (1):
Input: amimouse - mark driver struct with __refdata to prevent section mismatch
Vicki Pfau (1):
Input: xpad - add support for ASUS ROG RAIKIRI
Diffstat:
--------
drivers/input/joystick/xpad.c | 2 ++
drivers/input/mouse/amimouse.c | 8 +++++++-
2 files changed, 9 insertions(+), 1 deletion(-)
Thanks.
--
Dmitry
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [git pull] Input updates for v6.9-rc6
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
1 sibling, 0 replies; 6+ messages in thread
From: pr-tracker-bot @ 2024-05-05 17:12 UTC (permalink / raw)
To: Dmitry Torokhov; +Cc: Linus Torvalds, linux-kernel, linux-input
The pull request you sent on Sat, 4 May 2024 20:25:58 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git tags/input-for-v6.9-rc6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/3f1d0865002795eb45c49e30a4fbc40f7956b6ae
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
^ permalink raw reply [flat|nested] 6+ messages in thread
* Mismatched product ids for the ASUS ROG RAIKIRI PRO
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 ` Justin Opini
2026-05-19 21:18 ` Dmitry Torokhov
1 sibling, 1 reply; 6+ messages in thread
From: Justin Opini @ 2026-05-19 17:37 UTC (permalink / raw)
To: dmitry.torokhov; +Cc: linux-input, linux-kernel, torvalds
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'"
Regards,
Justin
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Mismatched product ids for the ASUS ROG RAIKIRI PRO
2026-05-19 17:37 ` Mismatched product ids for the ASUS ROG RAIKIRI PRO Justin Opini
@ 2026-05-19 21:18 ` Dmitry Torokhov
2026-05-20 19:06 ` opinijm
0 siblings, 1 reply; 6+ messages in thread
From: Dmitry Torokhov @ 2026-05-19 21:18 UTC (permalink / raw)
To: Justin Opini; +Cc: linux-input, linux-kernel, torvalds, Luke D. Jones
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Mismatched product ids for the ASUS ROG RAIKIRI PRO
2026-05-19 21:18 ` Dmitry Torokhov
@ 2026-05-20 19:06 ` opinijm
2026-05-20 19:13 ` opinijm
0 siblings, 1 reply; 6+ messages in thread
From: opinijm @ 2026-05-20 19:06 UTC (permalink / raw)
To: Dmitry Torokhov; +Cc: linux-input, linux-kernel, torvalds, Luke D. Jones
On Tuesday, May 19th, 2026 at 5:19 PM, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> 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.
>
Ah i was thinking about this more. The device has 3 modes of connection, there is Bluetooth(on the Github tracker), and 2.4GHz via USB receiver(which is what I use) as well as USB directly to the device. Not use if this is enough to introduce variants, but I thought it was worth thinking out aloud. Maybe Luke could chime in on usage? In any case is a patch appropriate here to introduce variant?
> Thanks.
>
> --
> Dmitry
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Mismatched product ids for the ASUS ROG RAIKIRI PRO
2026-05-20 19:06 ` opinijm
@ 2026-05-20 19:13 ` opinijm
0 siblings, 0 replies; 6+ messages in thread
From: opinijm @ 2026-05-20 19:13 UTC (permalink / raw)
To: Dmitry Torokhov; +Cc: linux-input, linux-kernel, torvalds, Luke D. Jones
On Wednesday, May 20th, 2026 at 3:06 PM, opinijm@provdh.com <opinijm@provdh.com> wrote:
>
> On Tuesday, May 19th, 2026 at 5:19 PM, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
>
> > 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.
> >
>
> Ah i was thinking about this more. The device has 3 modes of connection, there is Bluetooth(on the Github tracker), and 2.4GHz via USB receiver(which is what I use) as well as USB directly to the device. Not use if this is enough to introduce variants, but I thought it was worth thinking out aloud. Maybe Luke could chime in on usage? In any case is a patch appropriate here to introduce variant?
Connected via USB I get,
Bus 003 Device 004: ID 0b05:1abb ASUSTek Computer, Inc. ROG RAIKIRI PRO
I can't test Bluetooth because I have a motherboard that doesn't have a supported driver yet.
>
> > Thanks.
> >
> > --
> > Dmitry
> >
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2026-05-20 19:13 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2026-05-20 19:06 ` opinijm
2026-05-20 19:13 ` opinijm
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox