From: Ryan Underwood <nemesis-lists@icequake.net>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Ryan Underwood <nemesis-lists@icequake.net>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: PCI parport irq sharing?
Date: Thu, 8 Jan 2004 19:38:18 -0600 [thread overview]
Message-ID: <20040109013818.GB26519@dbz.icequake.net> (raw)
In-Reply-To: <Pine.LNX.4.53.0401081340240.25165@chaos>
[-- Attachment #1: Type: text/plain, Size: 2506 bytes --]
On Thu, Jan 08, 2004 at 02:08:19PM -0500, Richard B. Johnson wrote:
> >
> > parport0: PC-style at 0x3bc (0x7bc), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
> > parport1: PC-style at 0xc400 (0xc800), irq 9, using FIFO [PCSPP,TRISTATE,COMPAT,ECP]
> > parport1: irq 9 in use, resorting to polled operation
> > parport2: PC-style at 0xcc00 (0xd000) [PCSPP,TRISTATE]
> >
> > parport0 is the mb's builtin parallel port, and parport1/parport2 are
> > the two ports on the PCI card. IRQ 9 is taken by USB already. But
> > since it's a modern PCI card, it would stand to reason that it should be
> > able to share the IRQ with another PCI device, no? Unfortunately, my
> > application requires interrupt-driven operation.
>
> To share interrupts requires that the interrupting device
> generate a level instead of an edge. The parallel ports
> that exist in "super I/O chips" and in bare boards, produce
> edges. If you have a special parallel port in a PCI slot, it
> should generate levels because the PCI specification demands
> that it does.
>
> Since IRQ7 (the dedicated, edge, ISA parallel port interrupt)
> should never go to any PCI slot, I don't see how it could
> ever report using that. Perhaps it's a bug or the BIOS allowed
> it to be configured that way (remove IRQ7 from the PCI bus).
> This should make something else show up on the PCI bus.
> Move the board to another slot and see if the shared problem
> still remains.
We might have talked past each other here. The IRQ7 is okay, because
that's the motherboard's super I/O chip. The PCI parallel card is
allocated IRQ9, which shares with USB and ACPI. However, the parport_pc
driver doesn't seem to realize this is a PCI card and can share
interrupts, hence the "irq %d in use, resorting to polled..." Worse,
even if I find a free IRQ, I still can't use both the PCI card's
parallel ports in interrupt-driven operation; as soon as one parport_pc
is enabled on that IRQ, then the second parport can't use that IRQ
anymore. Like the board is conflicting with itself....
My question was whether or not IRQ sharing was possible with the basic
parport driver or not. If not, would something like parport_serial help
me out here? Though, this is a NetMos card:
00:08.0 Communication controller: NetMos Technology VScom 021H-EP2 2 port parallel adaptor (rev 01)
and I don't think NetMos support has made it into parport_serial yet.
thanks,
--
Ryan Underwood, <nemesis@icequake.net>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-01-09 1:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 18:16 Ryan Underwood
2004-01-08 19:08 ` Richard B. Johnson
2004-01-09 1:38 ` Ryan Underwood [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=20040109013818.GB26519@dbz.icequake.net \
--to=nemesis-lists@icequake.net \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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
all inboxes | Powered by JetHome®