From: ashish anand <ashisha@india.infogain.com>
To: paulus@samba.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: PCI BAR initialisation..?
Date: Thu, 12 Jul 2001 07:17:50 +0530 [thread overview]
Message-ID: <3B4D01C6.91646BE6@india.infogain.com> (raw)
In-Reply-To: 15181.18002.484704.634903@cargo.ozlabs.ibm.com
I have mpc107 pci-host bridge.
motherboard is sandpoint + mcp750 processor.
pci_config_access method is indirect and config_address is 0xfec00000
config_data is 0xfee00000 rather than 0xcfc and 0xcf8.
i wonder if it would have been a case of memory reordering in that case
In bios how can we always believe on resource assignment of devices.
does it just a matter of chance that when we assign through bios this
reordering issue doesn't affect us..
Paul Mackerras wrote:
>
> ashish anand writes:
>
> > But by any chance if somebody has come across a random feature of pci BAR.
> > that is if you write the required pci addresses in BAR after writing 0xffffffff and
> > reading it back , and to confirm if the actual value has reached the BAR , we read it again
> > but then it returns funny values.
> >
> > more surprisingly if i move the code in some other function then everything behaves correctly.
> > I am more then sure that nothing relevant is happening betwen two places.
>
> Hmmm, that sounds like maybe the config space reads and writes are
> getting reordered, which would be a Bad Thing.
>
> What sort of PCI host bridge does your system have?
>
> If you place an mb() call after each pci config read or write, does
> that fix the problem?
>
> Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-07-12 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 7:51 PCI BAR initialisation..? ashish anand
2001-07-12 6:40 ` Paul Mackerras
2001-07-12 1:47 ` ashish anand [this message]
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=3B4D01C6.91646BE6@india.infogain.com \
--to=ashisha@india.infogain.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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).