From: Niall Parker <niall@ve7hex.ampr.org>
To: Christian Reynolds <cyberdoc@matrix.subsolar.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: Linux box / repeater project
Date: Sat, 26 Apr 2003 14:44:19 -0700 [thread overview]
Message-ID: <3EAAFDB3.1080107@ve7hex.ampr.org> (raw)
In-Reply-To: a05200f00bad091036543@[10.10.1.6]
Christian Reynolds wrote:
>
>
> Thinking aloud, I am wondering if I can use linux to read the game /
> joystick port. Let's say that each receiver has a wire that carries a +
> voltage when the receiver is active (a COS signal). Can I assign the
> pins on the Joystick port so that
>
> Pin 1 = Receive 1
> Pin 2 = Receive 2
> Pin 3 = Receive 3
> Pin 4 = Receive 4
> Pin 5 = Ground
If it is a standard joystick port then reassigning the pins isn't
possible, but fortunately there are already 4 inputs intended for button
inputs you can use, and you could also use switches + resistors on the
analog inputs for another 4 input bits if needed. I'm sure you can find
the pinouts somewhere on the web faster than I can dig out my docs.
I've used the button inputs to do a soft boot on a headless terminal
before, just hacking some code together that polled the pins. This was a
while back and I understand the Linux kernel may have restrictions on
direct port access, but I expect using the joystick module in the
standard would work fine (only gotcha may be setting a fixed resistor on
one of the analog inputs so the module doesn't complain about no
joystick present)
... Niall (VE7HEX)
prev parent reply other threads:[~2003-04-26 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-26 20:26 Linux box / repeater project Christian Reynolds
2003-04-26 21:38 ` Robert L Cochran
2003-04-26 22:00 ` Robert L Cochran
2003-04-26 21:44 ` Niall Parker [this message]
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=3EAAFDB3.1080107@ve7hex.ampr.org \
--to=niall@ve7hex.ampr.org \
--cc=cyberdoc@matrix.subsolar.com \
--cc=linux-hams@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 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.