From: Ryan Underwood <nemesis-lists@icequake.net>
To: gnupic@linuxhacker.org, linux-msdos@vger.kernel.org
Subject: Re: PICs on Linux
Date: Thu, 11 Nov 2004 15:38:14 -0600 [thread overview]
Message-ID: <20041111213814.GC32418@dbz.icequake.net> (raw)
In-Reply-To: <418eca0c.17.4429.1500450417@ihug.co.nz>
Hi Bart,
On Mon, Nov 08, 2004 at 02:21:16PM +1300, Bart Oldeman wrote:
>
> Speed shouldn't be such a big deal: according to
> http://www.ussg.iu.edu/hypermail/linux/kernel/0303.0/0978.html
> you can only do about 300000 inb's and outb's per second
> anyway.
Speed betweeen a virtualized and non-virtualized parallel port I/O can
be a big deal in my experience. I have at least one device that gives
up when parallel ports are passed through in non-fast mode. It operates
with tristate data lines and one strobe pin. I'm not sure what the
problem is, only that the port must be fast for it to work. On a
(much?) faster machine, probably the port virtualization would not
affect it. But requiring the use of ppdev doesn't make sense in this
case.
By the way, I have benchmarked ppdev vs raw portio performance on this
device with a linux program. The difference is quite significant (ppdev
only performs around 60% of the rawio speed IIRC). On a better device
which uses interrupt or DMA driven I/O, the difference would not be that
significant, but on this device, transfer rate depends on how fast the
registers of parallel port can be "twiddled", so it is greatly affected
by any delay therein.
--
Ryan Underwood, <nemesis@icequake.net>
next prev parent reply other threads:[~2004-11-11 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 1:21 PICs on Linux Bart Oldeman
2004-11-11 21:38 ` Ryan Underwood [this message]
[not found] <20041111213944.GD32418@dbz.icequake.net>
2004-11-12 3:11 ` Bill Couture
-- strict thread matches above, loose matches on Subject: below --
2004-11-08 2:03 Bart Oldeman
[not found] <20041107041204.513276C@mail.icequake.net>
2004-11-07 23:02 ` Ryan Underwood
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=20041111213814.GC32418@dbz.icequake.net \
--to=nemesis-lists@icequake.net \
--cc=gnupic@linuxhacker.org \
--cc=linux-msdos@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