From: "Neil Wilson" <nwilson@airspan.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: pci_consistent_alloc & mpc107 snoop
Date: Wed, 29 May 2002 18:31:43 +0100 [thread overview]
Message-ID: <002101c20736$bb52f640$7c99883e@m5axc> (raw)
Hi,
I hope someone can enlighten me .....
Am I right in thinking that pci_consistent_alloc gets me
uncached memory ?, if not is there an easy way to modify the pages allocated
?
The reason being is that we have an mpc7450/mpc107 board with a custom
pci ethernet card (it runs a modified pcnet32 driver) and also a soft
ethernet
port in an fpga. The hardware designer reckons we are getting stung with a
motorola 7450 errata (#46 if anyone is interested), where the 7450 can hang
during signalling retries with the 107.
Our hardware designer therefore wants the pci ethernet to use uncached
buffers &
also to have the 107 pci snoop disabled. I have disabled snoop in the boot
code (ppcboot) and the ethernet card still works, but now it does not work
under Linux (it used to be fine with snoop enabled, nfs etc all worked).
Any ideas ....?
Thanks.
Neil
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-05-29 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 17:31 Neil Wilson [this message]
2002-05-29 18:30 ` pci_consistent_alloc & mpc107 snoop Dan Malek
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='002101c20736$bb52f640$7c99883e@m5axc' \
--to=nwilson@airspan.com \
--cc=linuxppc-embedded@lists.linuxppc.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).