From: Donald Becker <becker@scyld.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: 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: Tue, 4 Mar 2003 13:16:22 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0303041312230.974-100000@beohost.scyld.com> (raw)
In-Reply-To: <20030303151412.A15195@jurassic.park.msu.ru>
On Mon, 3 Mar 2003, Ivan Kokshaysky wrote:
> On Sun, Mar 02, 2003 at 12:44:06PM -0500, jamal wrote:
> > Interupt routing as can be seen above is really messed for that device.
>
> Indeed. Quad tulip cards usually have irq pin A of each chip routed
> to pins A-D on the connector, so they cannot have the same irq unless
Incorrect.
Most quad Tulip boards have the bus bridge wired so that all interrupts
are sent on the INTA output of the board.
The tulip.c driver has worked around the BIOS bug on x86 machines for
years. It should really be handled in the generic PCI quirks code, but
has not yet been correctly handled in the kernel's code.
--
Donald Becker becker@scyld.com
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Scyld Beowulf cluster system
Annapolis MD 21403 410-990-9993
next prev parent reply other threads:[~2003-03-04 18:10 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 [this message]
2003-03-04 22:30 ` Ivan Kokshaysky
2003-03-04 22:59 ` kuznet
2003-03-04 23:36 ` Donald Becker
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=Pine.LNX.4.44.0303041312230.974-100000@beohost.scyld.com \
--to=becker@scyld.com \
--cc=Robert.Olsson@data.slu.se \
--cc=alexander@netintact.se \
--cc=david.knierim@tekelec.com \
--cc=greg@kroah.com \
--cc=hadi@cyberus.ca \
--cc=ink@jurassic.park.msu.ru \
--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;
as well as URLs for NNTP newsgroup(s).