From: Brian Beattie <beattie@beattie-home.net>
To: linuxppc-embedded@ozlabs.org
Subject: MPC8249 PCI Bus 2
Date: Fri, 22 Dec 2006 15:47:00 -0800 [thread overview]
Message-ID: <1166831220.5602.14.camel@localhost.localdomain> (raw)
I'm working on bringing up a board and having some trouble with the
second PCI Bus and was wondering if anybody had any idea.
The kernel is 2.6.19.1 patched to set the Local Access Window because
out u-boot does not do that yet. I have an Intel 82541 GigE chip
hanging off PCI Bus 1 that seems to be working fine.
On Bus 2 I have a mini-pci connector:
Trying an el-cheapo i82551 based 10/100 NIC it hangs after about 5 pings
on an quiet segment and before I can send anything on a noisy segment
with both the eepro100 and e100 drivers.
Trying a prism II based wireless nic, it fails in the device probe
trying to read a status register because the result is all ones (as if
nothing is there).
Near as I can tell I am getting interrupts.
--
Brian Beattie LFS12947 | "Honor isn't about making the right choices.
beattie@beattie-home.net | It's about dealing with the consequences."
www.beattie-home.net | -- Midori Koto
reply other threads:[~2006-12-23 0:06 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=1166831220.5602.14.camel@localhost.localdomain \
--to=beattie@beattie-home.net \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).