From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-kernel@vger.kernel.org
Subject: parport - interrupt sharing possible?
Date: Sun, 11 Jul 2004 22:51:19 -0500 [thread overview]
Message-ID: <20040712035119.GA1865@dbz.icequake.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
Hi,
Does anyone know if the generic parport interrupt handler is okay (or not)
for sharing interrupts? The reason I ask is that I have a PCI parallel
card with two ports on it. Without a IRQ sharing capability, it is not
possible for both of them to operate in interrupt-driven mode. I tested
a quick hack to enable IRQ sharing:
http://home.icequake.net/~nemesis/parport.diff
and it seems to work okay with both ports in use. I'm hoping someone
more knowledgeable on the parallel port subject (Tim Waugh?) can shed
some light on whether this is acceptable or not. The interrupt handler
eventually ends up in parport_ieee1284_interrupt which really doesn't do
much besides wake up sleepers.
Thanks!
PS: Heh, the power just went out and back on as I wrote this. Giving thanks
for having multiple UPS units around!
--
Ryan Underwood, <nemesis@icequake.net>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-07-12 3:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 3:51 Ryan Underwood [this message]
2004-07-12 14:03 ` parport - interrupt sharing possible? Marcelo Tosatti
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=20040712035119.GA1865@dbz.icequake.net \
--to=nemesis-lists@icequake.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