From: Paul Mackerras <paulus@samba.org>
To: Linh Dang <dang.linh@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][PPC32[NEWBIE] enhancement to virt_to_bus/bus_to_virt (try 2)
Date: Mon, 6 Dec 2004 08:12:58 +1100 [thread overview]
Message-ID: <16819.31194.561882.514591@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <3b2b32004120306463b016029@mail.gmail.com>
Linh Dang writes:
> I wrote a DMA engine (to used by other drivers) that (would like to) accept
> all kind of buffers as input (vmalloced, dual-access shared RAM mapped
> by BATs, etc). The DMA engine has to decode the virtual address of the
> input buffer to (possibly multiple) physical address(es). virt_to_phys()
> has the right name for the job except it only works for the kernel virtual
> addresses initially mapped at KERNELBASE
Have you read Documentation/DMA-API.txt? It explains the official
kernel API for DMA, and drivers should use it in order to be portable
to more than just one architecture.
If you want to create a competing DMA API, you'll have to show us at
least one driver that really needs your new API.
Also, please don't change the existing virt_to_*/*_to_virt functions.
Instead define your own functions (with different names) in the same
source file as your other new code.
Paul.
next prev parent reply other threads:[~2004-12-05 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 14:49 [PATCH][PPC32] enhancement to virt_to_bus/bus_to_virt (resent with spell-checked subject line) Linh Dang
2004-12-02 16:28 ` [PATCH][PPC32[NEWBIE] enhancement to virt_to_bus/bus_to_virt (try 2) Linh Dang
2004-12-02 20:31 ` Paul Mackerras
2004-12-03 14:46 ` Linh Dang
2004-12-05 10:11 ` Eugene Surovegin
2004-12-05 19:18 ` Linh Dang
2004-12-05 20:52 ` Eugene Surovegin
2004-12-05 21:12 ` Paul Mackerras [this message]
2004-12-06 1:31 ` Linh Dang
2004-12-06 1:56 ` Linh Dang
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=16819.31194.561882.514591@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=dang.linh@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®