linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Trent George <trent@norwalkdist.com>, linux-ide@vger.kernel.org
Subject: Re: multiple irqs per card on the sata_sil24
Date: Wed, 27 Sep 2006 10:09:05 +0900	[thread overview]
Message-ID: <4519CF31.2080303@gmail.com> (raw)
In-Reply-To: <4519CEBA.90307@gmail.com>

Tejun Heo wrote:
> Trent George wrote:
>> While reading the specs, I noticed that the pci-x cards support 
>> splitting each port to a unique irq pin.
> 
> 3124 doesn't seem to support multiple MSI interrupts either.  Multiple 

s/either//

> Theoretically, yes, but linux currently cannot do multiple MSI 
> interrupts and I don't think it's gonna be supported anytime soon. pci-e 
> + multiple MSIX interrupts are supported but AFAIK 3132 supports that.

s/supports/doesn't support/

Sorry.

-- 
tejun

      reply	other threads:[~2006-09-27  1:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-27  0:31 multiple irqs per card on the sata_sil24 Trent George
2006-09-27  0:46 ` Jeff Garzik
2006-09-27  1:07 ` Tejun Heo
2006-09-27  1:09   ` Tejun Heo [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=4519CF31.2080303@gmail.com \
    --to=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=trent@norwalkdist.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;
as well as URLs for NNTP newsgroup(s).