From: Adrian McMenamin <adrian@newgolddream.dyndns.info>
To: linux-sh@vger.kernel.org
Subject: Re: How can I test a joystick type device?
Date: Sun, 10 Feb 2008 19:43:59 +0000 [thread overview]
Message-ID: <1202672639.6237.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1202514806.6237.1.camel@localhost.localdomain>
On Fri, 2008-02-08 at 19:18 -0600, Harley Laue wrote:
> On Friday 08 February 2008 05:53:26 pm you wrote:
> > As below shows I think I have successfully ported the 2.4 Dreamcast
> > controller driver to 2.6 - but how can I test it? Is there a device I
> > should be looking for in /dev that I could just cat?
> Cool.
> if a /dev/input/js? or /dev/js? does not show up you can try:
> mknod js0 c 13 0
> then you can cat js0 and move the joystick to see if it's working
Clearly the porting isn't as simple as I'd hoped: I cannot seem to get a
udev rule to recognise the thing and if I create the node manually there
is strangeness and an unwillingness to work!
I'll hack away at it, but I obviously need to get a better understanding
of the 2.6 input layer also...
-bash-3.1# ls js* -l
crw-r--r-- 1 root 4294967258 13, 0 Feb 10 19:39 js0
-bash-3.1# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda1 189303128 159489980 20197044 89% /
tmpfs 6852 0 6852 0% /lib/init/rw
udev 10240 4 10236 1% /dev
tmpfs 6852 0 6852 0% /dev/shm
/dev/gdrom 189303128 159489980 20197044 89% /mnt
-bash-3.1# mknod js0 c 13 0
mknod: `js0': File exists
-bash-3.1# rm js0
-bash-3.1# mknod js0 c 13
0
-bash-3.1# ls js* -l
crw-r--r-- 1 root 4294967258 13, 0 Feb 10 19:40 js0
-bash-3.1# cat js0
cat: js0: No such device
next prev parent reply other threads:[~2008-02-10 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 23:53 How can I test a joystick type device? Adrian McMenamin
2008-02-09 1:18 ` Harley Laue
2008-02-09 2:58 ` Paul Mundt
2008-02-09 14:57 ` Adrian McMenamin
2008-02-10 19:43 ` Adrian McMenamin [this message]
2008-02-11 0:11 ` Adrian McMenamin
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=1202672639.6237.2.camel@localhost.localdomain \
--to=adrian@newgolddream.dyndns.info \
--cc=linux-sh@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox