From: wolfking <wolfking2000@msn•com>
To: linuxppc-dev@ozlabs•org
Subject: Re: can't access PCIe card under sbc8548
Date: Thu, 30 May 2013 00:32:37 -0700 (PDT) [thread overview]
Message-ID: <1369899157331-71783.post@n7.nabble.com> (raw)
In-Reply-To: <51A6EA1D.7080100@windriver.com>
(continued)
I traced the 8139too.c when it uses pci_iomap, the pci_iomap called the
ioport_map. The difference between 8139 and my PCIe card lies in the
"port" value :
void __iomem *ioport_map(unsigned long port, unsigned int len)
{
return (void __iomem *) (port + _IO_BASE);
}
in 8139too.c, the "port" value is 0x1000; for my PCIe card, the "port"
value
is 0xfefff000. And the value is got from pci_resource_start. So you see, the
8139 case doesn't overflow, my PICe overflows when _IO_BASE's value is
0xfd7fd000.
--
View this message in context: http://linuxppc.10917.n7.nabble.com/can-t-access-PCIe-card-under-sbc8548-tp71775p71783.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.
next prev parent reply other threads:[~2013-05-30 7:32 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 [this message]
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
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=1369899157331-71783.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