mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: tcrix@att.net
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: No sharing IRQ broken board problem
Date: Wed, 2 Nov 2005 16:13:50 -0500	[thread overview]
Message-ID: <20051102211350.GD9488@csclub.uwaterloo.ca> (raw)
In-Reply-To: <110220052106.23704.43692A6C000AA6AE00005C98215876675598079D0C9B@att.net>

On Wed, Nov 02, 2005 at 09:06:53PM +0000, tcrix@att.net wrote:
> I have a pci board in development that works but..
> it can not share the interrupt line.  
> 
> Has someone hacked through the problem of reserving one of the inta, intb, .. 's for a single device?  I would love to see how you did so I could continue on with my driver while I wait for the !@$#!@ hardware guys to fix the board. 

As far as I understand the PCI specs, your device is currently NOT a PCI
device.

Support for shared IRQs on PCI is as far as I can tell not optional.
Short of designing your own mainboard there is no way to prevent the
interrupt lines from being joined.  One one board I use there are 6 PCI
devices, with 3 on INT-A and 3 on INT-B (The SBC doesn't have INT-C and
INT-D).  On my desktop machine, INT A is the same on slot 1 and 5, 2,
and 6 and onyl 3 and 4 have INT-A to themselves.  Of course this doesn't
prevent the bios from assigning the same IRQ to INT-A on multiple sets
as well.  I have run a PPro some years ago with a single IRQ shared
among all the PCI devices in the system.  Neither linux nor windows had
a problem with that and neither did any of the many PCI devices.

I think you are stuck waiting for the hardware guys to give you a PCI
device that is really a PCI device.  If you are lucky you can find one
slot in your machine that doesn't share INT-A with any other PCI device,
although on most modern machines there are so many PCI devices that it
is imposible to find one that isn't shared.

Len Sorensen

  reply	other threads:[~2005-11-02 21:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-02 21:06 tcrix
2005-11-02 21:13 ` Lennart Sorensen [this message]
2005-11-02 21:32 ` linux-os (Dick Johnson)

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=20051102211350.GD9488@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tcrix@att.net \
    /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®