From: Sylvain Munaut <tnt@246tNt.com>
To: Mark Chambers <markc@mail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC5200 PCI byte-swapping
Date: Mon, 03 Jan 2005 17:47:48 +0100 [thread overview]
Message-ID: <41D97734.3070800@246tNt.com> (raw)
In-Reply-To: <003c01c4f19d$98a16510$0301a8c0@chuck2>
>Thanks. I had an older manual that didn't spell it out so
>clearly.
>
>I've been trying to interpret the PCI sections for some other
>82xx family parts, and it appears that they do NOT do this
>byte lane swapping, so this make the 5200 non-standard in
>this regard, which is unfortunate. If I'm understanding this
>right, one would have to have different drivers for a PCI
>device on a 5200 and an 8270, for instance.
>
>
Mmmm ...
Still I use the intel eepro driver without problems or modifications.
As long as the driver uses the proper readl/writel that should do
it or am I mistaken ?
I have a FPGA mounted with pci interface, I'll try to see what happens on
the bus
>Also, I note that when doing simple block reads from pre-
>fetchable PCI space, it appears the 5200 does not prefetch,
>but does each read individually. This is using stock ELDK
>u-boot and 2.4.24 so I haven't yet determined if it's a
>configuration matter, (or ruled out target disconnects)
>but I'm suspecting that you can't get burst mode from the
>5200 without using DMA.
>
>
Last time I checked, the 2.4 from denx didn't create a pci
window for prefetchable memory so prefetch mem zone
were mapped as non-prefetchable, so no burst for sure.
Sylvain
next prev parent reply other threads:[~2005-01-03 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 11:46 SMC/SCC uart problem with MPC852T David Jander
2004-12-30 15:30 ` Dan Malek
2004-12-30 20:35 ` MPC5200 PCI byte-swapping Mark Chambers
2005-01-01 22:39 ` Sylvain Munaut
2005-01-03 14:07 ` Mark Chambers
2005-01-03 16:47 ` Sylvain Munaut [this message]
2005-01-04 9:37 ` Stefan Nickl
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=41D97734.3070800@246tNt.com \
--to=tnt@246tnt.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=markc@mail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.