From: "Allen Curtis" <acurtis@onz.com>
To: "Sylvain Latulippe" <slatulippe@mediatrix.com>,
<linuxppc-embedded@lists.linuxppc.org>
Subject: RE: 8260 FCC and local bus
Date: Tue, 24 Sep 2002 09:25:06 -0700 [thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFKEHHDMAA.acurtis@onz.com> (raw)
In-Reply-To: <2702075D4DE2B043BF5EB82E9CFAD45B0CAD23@mail1.mediatrix.com>
> I have found some information in the mailing list regarding usage of local
> bus ram for FCC BD's and buffers. However I haven't found any
> conclusion if
> it's working.
Yes, you can use local RAM for the BD's and buffers. There is a penalty
because you need to move the buffers between local and 60X RAM. I have found
information on the list indicating that you can use IDMA for this purpose.
(search with the keyword "profiling" in embedded)
> Has anyone done it successfully?
> What kind of support does linux provide regarding local bus ram? (Ram
> drive,...)
No real support for local RAM per say. You need to treat it as any other
memory mapped device. Therefore you need to change all _va()/_pa() calls to
ioremap() and iopa().
Note: If you are using rev-A 8260 processors, this helps a lot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-09-24 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 15:48 8260 FCC and local bus Sylvain Latulippe
2002-09-24 16:25 ` Allen Curtis [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-27 14:36 8260, " Matt Gessner
2000-06-27 20:01 ` Matt Gessner
2000-06-27 23:19 ` 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=NCBBIINEHIPFGJPLBEIFKEHHDMAA.acurtis@onz.com \
--to=acurtis@onz.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=slatulippe@mediatrix.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 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).