public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: wolfking <wolfking2000@msn•com>
To: linuxppc-dev@ozlabs•org
Subject: Re: can't access PCIe card under sbc8548
Date: Fri, 31 May 2013 05:46:08 -0700 (PDT)	[thread overview]
Message-ID: <1370004368473-71874.post@n7.nabble.com> (raw)
In-Reply-To: <1369994474.3928.132.camel@pasglop>

hi, Herrenschmidt
 Thanks for replying to this topic!

> That looks more like a HW error to me unless you are hitting completely 
> the wrong system addresses.
The HW is OK. If I plug this card into another ppc board: mpc86641-hpcn,
it works fine. 

> What would be useful would be to add printk's to check what exact 
> physical address pci_iomap ends up using and whether that matches 
> to the iobase_phys of the PCI bridge + the BAR value of the card.
Would you mind telling me at what position should I add the printk?
I can only print pci_iomap's return address which is mentioned in 
the previous mail, it is 0xfc7fc000. The following is part of the
linux boot message:

PCI host bridge /pcie@e000a000  ranges:
 MEM 0x00000000a0000000..0x00000000afffffff -> 0x00000000a0000000 
  IO 0x00000000e2800000..0x00000000ea7fffff -> 0x0000000000000000
/pcie@e000a000: PCICSRBAR @ 0xfff00000

 Is 0xe2800000 the iobase_phys of the PCI bridge?

So any suggestion is appreciated!

regards,
wolfking.




--
View this message in context: http://linuxppc.10917.n7.nabble.com/can-t-access-PCIe-card-under-sbc8548-tp71775p71874.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.

  reply	other threads:[~2013-05-31 12:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30  3:42 can't access PCIe card under sbc8548 wolfking
2013-05-30  5:56 ` tiejun.chen
2013-05-30  7:19   ` wolfking
2013-05-30  8:47     ` tiejun.chen
2013-05-30  9:15       ` wolfking
2013-05-30  9:30         ` tiejun.chen
2013-05-30  7:32   ` wolfking
2013-05-30 10:42     ` tiejun.chen
2013-05-30 12:49       ` wolfking
2013-05-30 16:24         ` Scott Wood
2013-05-31  1:34           ` tiejun.chen
2013-05-31  2:27             ` wolfking
2013-05-31 10:00           ` Benjamin Herrenschmidt
2013-05-30 10:02 ` wolfking
2013-05-30 10:08   ` tiejun.chen
2013-05-30 12:45     ` wolfking
2013-05-30 16:29 ` Scott Wood
2013-05-31  0:40   ` wolfking
2013-05-31 10:01     ` Benjamin Herrenschmidt
2013-05-31 12:46       ` wolfking [this message]
2013-06-08  7:00         ` wolfking

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=1370004368473-71874.post@n7.nabble.com \
    --to=wolfking2000@msn$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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