From: Dan Malek <dan@embeddededge•com>
To: paulus@samba•org
Cc: Armin Kuster <akuster@mvista•com>,
ppcdevel <linuxppc-dev@lists•linuxppc.org>
Subject: Re: New API for non cache coherent ppc cpu's
Date: Fri, 23 Nov 2001 11:08:29 -0500 [thread overview]
Message-ID: <3BFE747D.4080908@embeddededge.com> (raw)
In-Reply-To: 15357.42818.227392.566129@cargo.ozlabs.ibm.com
Paul Mackerras wrote:
> To go with pci_map_page and pci_unmap_page. These give you the
> ability to do DMA to highmem pages without using bounce buffers.
IIRC, there was a virt_to_bus in the code at one time, making it
unusable for highmem pages, which is why I couldn't understand
the appearance of the function.
> My preference would be to make the one set of functions work
> everywhere.
Mine, too. I just wish this was a common concept across a variety
of our I/O interfaces.
> .... OTOH these non-PCI devices you're talking about are
> presumably very specific to PPC embedded chips so maybe it doesn't
> matter so much.
That is always a challenge with the embedded parts. It is often
very convenient to make the (promper, IMHO) assumption this software
isn't going to be used outside of these parts.
Thanks.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-23 16:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 20:13 New API for non cache coherent ppc cpu's Armin Kuster
2001-11-21 11:15 ` Roman Zippel
2001-11-21 18:29 ` Armin Kuster
2001-11-21 20:20 ` Roman Zippel
2001-11-22 20:57 ` Paul Mackerras
2001-11-22 23:07 ` Dan Malek
2001-11-22 23:54 ` Roman Zippel
2001-11-23 1:32 ` Paul Mackerras
2001-11-23 16:08 ` Dan Malek [this message]
2001-11-22 23:50 ` Roman Zippel
2001-11-23 1:09 ` Paul Mackerras
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=3BFE747D.4080908@embeddededge.com \
--to=dan@embeddededge$(echo .)com \
--cc=akuster@mvista$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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