From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Donald Becker <becker@scyld.com>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
jamal <hadi@cyberus.ca>, Greg KH <greg@kroah.com>,
Linus Torvalds <torvalds@transmeta.com>,
Jeff Garzik <jgarzik@pobox.com>,
kuznet@ms2.inr.ac.ru, david.knierim@tekelec.com,
Robert Olsson <Robert.Olsson@data.slu.se>,
linux-kernel@vger.kernel.org, alexander@netintact.se
Subject: Re: PCI init issues
Date: Wed, 5 Mar 2003 01:30:37 +0300 [thread overview]
Message-ID: <20030305013037.A678@localhost.park.msu.ru> (raw)
In-Reply-To: <Pine.LNX.4.44.0303041312230.974-100000@beohost.scyld.com>; from becker@scyld.com on Tue, Mar 04, 2003 at 01:16:22PM -0500
On Tue, Mar 04, 2003 at 01:16:22PM -0500, Donald Becker wrote:
> Incorrect.
> Most quad Tulip boards have the bus bridge wired so that all interrupts
> are sent on the INTA output of the board.
This can be true for older cards, but post-1998 hardware must follow
the spec.
PCI-to-PCI Bridge Architecture Specification, Rev 1.1, Dec 18, 1998,
pp 113-114:
"... The interrupt binding defined in this table is mandatory for
expansion boards utilizing a bridge.
[table skipped]
Device 0 on a secondary bus will have its INTA# line connected to
the INTA# line of the connector. Device 1 will have its INTA# line
connected to INTB# of the connector. This sequence continues and
then wraps around once INTD# has been assigned."
I know for a fact that at least D-Link card mentioned in some reports
utilizes all four INT# lines, because I have one.
Ivan.
next prev parent reply other threads:[~2003-03-04 22:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 17:44 PCI init issues jamal
2003-03-03 12:14 ` Ivan Kokshaysky
2003-03-03 16:01 ` David S. Miller
2003-03-04 1:51 ` jamal
2003-03-04 1:48 ` jamal
2003-03-04 15:28 ` Ivan Kokshaysky
2003-03-04 18:16 ` Donald Becker
2003-03-04 22:30 ` Ivan Kokshaysky [this message]
2003-03-04 22:59 ` kuznet
2003-03-04 23:36 ` Donald Becker
-- strict thread matches above, loose matches on Subject: below --
2003-03-04 16:26 david.knierim
2003-03-04 16:41 ` Linus Torvalds
2003-03-04 17:54 ` Ron Arts
2003-03-04 18:26 ` Ivan Kokshaysky
2003-03-04 18:54 ` Linus Torvalds
2003-03-04 19:37 ` Ron Arts
2003-03-04 22:46 ` Zwane Mwaikambo
2003-03-04 23:22 ` Ron Arts
2003-03-04 23:58 ` Zwane Mwaikambo
2003-03-04 22:46 ` Ivan Kokshaysky
2003-03-04 23:12 ` kuznet
2003-03-05 11:06 ` Ivan Kokshaysky
2003-03-05 13:54 ` Ron Arts
2003-03-04 21:50 david.knierim
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=20030305013037.A678@localhost.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=Robert.Olsson@data.slu.se \
--cc=alexander@netintact.se \
--cc=becker@scyld.com \
--cc=david.knierim@tekelec.com \
--cc=greg@kroah.com \
--cc=hadi@cyberus.ca \
--cc=jgarzik@pobox.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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