From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Linux kernel <linux-kernel@vger.kernel.org>,
linuxppc-dev@lists.linuxppc.org
Subject: help with pci probing at boot time
Date: Tue, 08 Jun 2004 18:13:59 -0400 [thread overview]
Message-ID: <40C63A27.6030902@nortelnetworks.com> (raw)
I'm trying to boot an mcpn765 card with 2.6.5 and I seem to be running into PCI
issues.
There is a calling sequence in the 765 boot that goes like this:
arch_initcall(ppc_init);
ppc_md.init()
mcpn765_init2()
mcpn765_setup_via_82c586b()
This last function tries to find a particular VIA bridge using
pci_find_device(), and if it doesn't find it it dumps an error message and
halts. This is what I'm seeing.
I tried to figure out how the PCI probing thing worked (I have CONFIG_HOTPLUG=n)
but I couldn't figure out the call chain. (pci_devices gets added to by
pci_bus_add_devices, which gets called by pci_do_scan_bus and
pci_scan_bus_parented, but neither of those seems to get called by anyone in the
ppc kernel, and all other callers of pci_bus_add_devices are hotplug-related or
in another architecture.)
I instrumented the PCI probing functions, and they do not seem to be called
before the ppc_init path, which presents difficulties since pci_find_device()
doesn't have the data it needs to actually do its job.
Any suggestions?
Chris
reply other threads:[~2004-06-08 22:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40C63A27.6030902@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.org \
/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