From: Matt Porter <porter@cox.net>
To: Eric Seppanen <eds@reric.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: cache control functions
Date: Wed, 12 Mar 2003 12:22:40 -0700 [thread overview]
Message-ID: <20030312122240.B28769@home.com> (raw)
In-Reply-To: <20030312130214.A7123@reric.net>; from eds@reric.net on Wed, Mar 12, 2003 at 01:02:14PM -0600
On Wed, Mar 12, 2003 at 01:02:14PM -0600, Eric Seppanen wrote:
>
> I'm writing a driver module, for a pci device that lives in a 405GPr
> based system. I notice that the 405 doesn't seem to have a consistent
> cache after the pci device busmasters a bunch of data into SDRAM (or
> before it pulls data out), so I think the thing I'm supposed to do is
> call (depending on direction) one of these:
<snip>
> Is this intentional or an oversight? I can't see how I can write a
> driver for a busmaster device (that will work on a 405) without them.
Use the standard API described in Documentation/DMA-mapping.txt
You will find that there are PPC-specific (sort of, ARM has the same
names) versions of generic PCI DMA API defined in include/asm-ppc/io.h
Those can be used on on-chip or other non-PCI type device (stuff on
the EBC for 4xx).
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-12 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 19:02 cache control functions Eric Seppanen
2003-03-12 19:22 ` Matt Porter [this message]
2003-03-12 21:12 ` ramdisk source Prakash kanthi
2003-03-12 21:41 ` Wolfgang Denk
2003-03-19 6:26 ` Kenal Panic Kamaraj P
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=20030312122240.B28769@home.com \
--to=porter@cox.net \
--cc=eds@reric.net \
--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).