From: Florian Fuchs <fuchsfl@gmail.com>
To: Artur Rojek <contact@artur-rojek.eu>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sh: maple: fix empty port handling
Date: Wed, 12 Nov 2025 23:46:37 +0100 [thread overview]
Message-ID: <aRUOTfCJtqnNBjU3@lithos> (raw)
In-Reply-To: <999e3970e1580def5ddbf1921a9ef4a4@artur-rojek.eu>
Hi Artur,
thank you so much for fixing the DC boot on linux again!
Adrian, thank you for looking at it!
On 12 Nov 22:46, Artur Rojek wrote:
> thanks for the patch! Can this be tested with just regular controllers?
Yes, indeed you can test it with the controller, when you compile with
joystick support, like:
CONFIG_MAPLE=y
CONFIG_INPUT=y
CONFIG_INPUT_JOYDEV=y
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_MAPLE=y
You should not put a VMU in though, as thats currently broken (I have a
patch ready).
Then you can directly read from the evdev and listen for the button
presses:
bash-5.3# cat /dev/input/event2 | xxd
You need to press a button for 20-30 times, as it seems to buffer the
events and outputs it in batches.
Then, you should see the following outputs for the buttons:
Button A:
00000000: 7800 0000 94c3 0d00 0100 3001 0000 0000 x.........0.....
Button B:
000001e0: 7800 0000 94c3 0d00 0100 3101 0100 0000 x.........1....
Button X:
000003b0: 7800 0000 94c3 0d00 0100 3301 0100 0000 x.........3.....
Button Y:
00000900: 7800 0000 94c3 0d00 0100 3401 0100 0000 x.........4.....
The Joystick should be detected like this:
/ # dmesg|grep maple
maple: bus core now registered
maple (null): detected Dreamcast Controller: function 0x1: at (2, 0)
maple (null): no driver found
input: Dreamcast Controller as /devices/maple/2:00.1/input/input2
Another indicator is the dmesg log for empty ports:
maple (null): no devices to port 3
These messages were previously not there, as the empty ports were never
detected.
btw, I have also a cdi file, that boots for me, although I heard there
were issues on the NTSC-U devices, if helpful:
https://github.com/foxdrodd/dreamcast-linux/releases/download/6.17.7/linux6177-joystick.cdi
Thank you for your efforts,
Florian
next prev parent reply other threads:[~2025-11-12 22:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 19:04 [PATCH] sh: maple: fix empty port handling Florian Fuchs
2025-11-12 21:31 ` John Paul Adrian Glaubitz
2025-11-12 21:46 ` Artur Rojek
2025-11-12 22:46 ` Florian Fuchs [this message]
2025-11-16 12:34 ` Artur Rojek
2025-11-16 17:52 ` Florian Fuchs
2025-11-16 18:25 ` Artur Rojek
2026-04-12 7:29 ` John Paul Adrian Glaubitz
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=aRUOTfCJtqnNBjU3@lithos \
--to=fuchsfl@gmail.com \
--cc=contact@artur-rojek.eu \
--cc=dalias@libc.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox