From: Stephen Wille Padnos <spadnos@sover.net>
To: gene.heskett@verizon.net
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: I/O card vs linux
Date: Mon, 18 Oct 2004 00:31:29 -0400 [thread overview]
Message-ID: <41734721.3070508@sover.net> (raw)
In-Reply-To: <200410160423.43597.gene.heskett@verizon.net>
Gene Heskett wrote:
>Greetings;
>
>This may be OT, but can anyone advise me on a pci card thats basicly
>an 8255 with a 34 pin or greater port on the card or back panel to
>bring out all 3 ports, and a suitable linux compatible driver for it?
>
3 possibilities: (there are more, including some with industrial
protection, isolation, etc.)
www.computerboards.com : PCI-DIO24 and PCI-DIO24H, $89. These are
basically a single 8255 connected to the bus through a PCI glue chip.
They don't seem to provide a driver, but I would think the board would
be set up automatically by the PCI code, and then there are just the
standard 4 ports to read/write (you just have to find the base address
theough the PCI subsystem).
www.ni.com : NI-PCI-6503, $145. This is a 24 I/O board, but has added
logic (like a programmable power-on I/O state). There don't seem to be
Linux drivers, but they may exist if you ask tech support. (NI is
fairly Linux-friendly - they made a LabView/Linux version).
www.byterunner.com : PCI-1284-P2, $39.95. This is a dual IEEE1284 PCI
parallel port card, with Linux drivers. It's not quite what you're
looking for, but it will give you 24 I/O's (16 bidir, 10 dedicated, 2
interrupts).
Hope this helps
- Steve
next prev parent reply other threads:[~2004-10-18 4:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 8:23 I/O card vs linux Gene Heskett
2004-10-17 12:18 ` Jan-Benedict Glaw
2004-10-17 14:15 ` Gene Heskett
2004-10-18 4:31 ` Stephen Wille Padnos [this message]
2004-10-18 9:46 ` Gene Heskett
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=41734721.3070508@sover.net \
--to=spadnos@sover.net \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@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