From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
raarts@office.netland.nl, david.knierim@tekelec.com,
alexander@netintact.se, Donald Becker <becker@scyld.com>,
Greg KH <greg@kroah.com>, jamal <hadi@cyberus.ca>,
Jeff Garzik <jgarzik@pobox.com>,
kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
Robert Olsson <Robert.Olsson@data.slu.se>
Subject: Re: PCI init issues
Date: Wed, 5 Mar 2003 01:46:56 +0300 [thread overview]
Message-ID: <20030305014656.B678@localhost.park.msu.ru> (raw)
In-Reply-To: <Pine.LNX.4.44.0303041046370.1426-100000@home.transmeta.com>; from torvalds@transmeta.com on Tue, Mar 04, 2003 at 10:54:21AM -0800
On Tue, Mar 04, 2003 at 10:54:21AM -0800, Linus Torvalds wrote:
> Well, I'd say it looks like the MP table _claims_ that only pin0 is
> connected. Remember: the claim was that this machine worked on WinXP.
It seems that "IRQ redirection table" is gathered directly from
IO_APIC hardware (I may be wrong though), and it conforms to other
data...
> So there are at least two potential reasons for that:
>
> - The MP table is simply wrong, and WinXP gets the routing information
> from somewhere else (ie most likely ACPI)
>
> - The MP table is right, and only pin0 is connected, and WinXP only uses
> pin0 (ie it puts the card in some state where all irqs are shared
> across all of the four tulip chips).
>
> Maybe somebody can come up with other schenarios.
- XP is able to reprogramm the IO_APIC so that all four pins are
routed properly.
Sounds a bit heretical, I know. :-)
Ivan.
next prev parent reply other threads:[~2003-03-04 22:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 16:26 PCI init issues 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 [this message]
2003-03-04 23:12 ` kuznet
2003-03-05 11:06 ` Ivan Kokshaysky
2003-03-05 13:54 ` Ron Arts
2003-03-07 19:19 ` [fixed] " Ivan Kokshaysky
2003-03-10 18:43 ` jamal
2003-03-11 12:39 ` Ivan Kokshaysky
-- strict thread matches above, loose matches on Subject: below --
2003-03-04 21:50 david.knierim
2003-03-02 17:44 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
2003-03-04 22:59 ` kuznet
2003-03-04 23:36 ` Donald Becker
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=20030305014656.B678@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=raarts@office.netland.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.