From: "David S. Miller" <davem@redhat.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>,
"Alexey N. Kuznetsov" <kuznet@ms2.inr.ac.ru>,
david.knierim@tekelec.com,
Robert Olsson <Robert.Olsson@data.slu.se>,
Donald Becker <becker@scyld.com>,
linux-kernel@vger.kernel.org, alexander@netintact.se
Subject: Re: PCI init issues
Date: 03 Mar 2003 08:01:15 -0800 [thread overview]
Message-ID: <1046707275.16884.3.camel@rth.ninka.net> (raw)
In-Reply-To: <20030303151412.A15195@jurassic.park.msu.ru>
On Mon, 2003-03-03 at 04:14, Ivan Kokshaysky wrote:
> > Q2: Should we really be dependent on bios this bad?
>
> We certainly shouldn't wrt PCI IO and MMIO allocations, but irq routing
> appears to be so horribly overcomplexed on x86 that dependence on
> BIOS seems almost unavoidable here...
> Other architectures don't have such kind of problems, BTW.
Actually, for issues like that one Jamal is pointing out, I believe
there is something we can do.
What varies so much from motherboard to motherboard on x86 is how
the interrupts are wired up. So for example, this tells us that
PCI slot X maps to x86 IRQ Y. If we know that, we can figure out
where his deeply bridged tulips will send IRQs.
If the mp tables don't give exactly this kind of information,
then Ivan is right :(
Anyone know if FreeBSD fares better in situations like this?
What do they do if so?
next prev parent reply other threads:[~2003-03-03 15:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 17:44 jamal
2003-03-03 12:14 ` Ivan Kokshaysky
2003-03-03 16:01 ` David S. Miller [this message]
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
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=1046707275.16884.3.camel@rth.ninka.net \
--to=davem@redhat.com \
--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=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
all inboxes | Powered by JetHome®