linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-kernel@vger.kernel.org
Subject: PCI parport irq sharing?
Date: Thu, 8 Jan 2004 12:16:16 -0600	[thread overview]
Message-ID: <20040108181615.GA20930@dbz.icequake.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]


Hi,

Does parport_pc have the capability to share IRQs?  I have a PCI
parallel card with two ports on it:

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.

/proc/interrupts:
CPU0       
  0:     276501          XT-PIC  timer
  1:       1196          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  7:          7          XT-PIC  parport0
  8:          4          XT-PIC  rtc
  9:    2724988          XT-PIC  acpi, usb-ohci
 10:       8745          XT-PIC  eth0
 11:          0          XT-PIC  CMI8738-MC4
 12:          0          XT-PIC  PS/2 Mouse
 14:      16219          XT-PIC  ide0
 15:         29          XT-PIC  ide1
NMI:          0 
LOC:          0 
ERR:          0
MIS:          0

Kernel 2.4.24

thanks,

-- 
Ryan Underwood, <nemesis@icequake.net>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-01-08 18:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08 18:16 Ryan Underwood [this message]
2004-01-08 19:08 ` PCI parport irq sharing? Richard B. Johnson
2004-01-09  1:38   ` 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=20040108181615.GA20930@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;
as well as URLs for NNTP newsgroup(s).