LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Andriy Korud" <a.korud@vector.com.pl>
To: <linuxppc-embedded@ozlabs.org>
Subject: PCI mapping problems? (440EP/Bamboo)
Date: Fri, 6 May 2005 15:18:33 +0200	[thread overview]
Message-ID: <60E856FD577CC04BA3727AF4122D3F16113578@3bit.vector.com.pl> (raw)

Hi, I'm trying to make PCI on Bamboo usable at 33MHz and have the =
following problem:
Kernel 2.6.11 with Bamboo patches (either from the list or my own) =
boots, PCI is scanned fine:

PCI: Probing PCI hardware
Scanning bus 00
Found 00:20 [1260/3890] 000280 00
Fixups for bus 00
Bus scan for 00 returning with max=3D00
PCI fixup irq: (0000:00:04.0) got 25
PCI: bridge rsrc 0..ffff (100), parent c01b0f80
PCI: bridge rsrc a0000000..afffffff (200), parent c01b0f64
PCI:0000:00:04.0: Resource 0: afffe000-afffffff (f=3D200)

lspci is also working fine, but when trying to load any driver, kernel =
crashes on first actual device access, i.e. on writew() operation.
When tried to look which address it's trying to access - 0xd1058000 in =
my case - seems confusing for me - should not this address be withing =
PCI address range - 0xa... and withing this device address range - =
0xafffe000-afffffff?
Tracking deeper I've found that this address is taken from calling =
pci_resource_start(pdev, 0) whithing probe function in driver.=20

This problem is generic - at least 3 different pci drivers crash when =
trying to writew() to bad address.

Can anybody give some advice in which direction should I continue my =
debugging?

Thanks in advance,

--

Andriy Korud

                 reply	other threads:[~2005-05-06 13:18 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=60E856FD577CC04BA3727AF4122D3F16113578@3bit.vector.com.pl \
    --to=a.korud@vector.com.pl \
    --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