From: Pantelis Antoniou <panto@intracom.gr>
To: Matt Porter <porter@cox.net>,
Tom Rini <trini@kernel.crashing.org>,
Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: new dma API questions
Date: Thu, 03 Jun 2004 12:06:29 +0300 [thread overview]
Message-ID: <40BEEA15.3070505@intracom.gr> (raw)
Hi there.
I have a few questions regarding the new DMA API.
1. dma_map_single finally calls virt_to_bus, which is simplified
to:
return (unsigned long)address - KERNELBASE + PCI_DRAM_OFFSET;
PCI_DRAM_OFFSET is defined to be pci_dram_offset.
Typically it is set be 0 for most arches without pci.
How could we overide it with a constant 0 so that we avoid the
memory access?
2. How soon in the init sequence could we call dma_alloc_consistent?
For example when setting up a serial console on 8xx I need memory
for the fifos, and I have to revert in using m8xx_hostalloc which
IMO should be already dead.
If we could arrange for consistent_alloc to be able to operate with
a fixed memory area until the memory initialization is complete
it would make my life much easier and we could finally kill
m8xx_hostalloc & friends.
3. The first argument is dma_* function is a struct device.
When working with network devices I must set this to NULL.
Granted this is no problem right now, but could this be
a problem in the future?
Regards
Pantelis
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-06-03 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 9:06 Pantelis Antoniou [this message]
2004-06-03 10:56 ` new dma API questions Dan Malek
2004-06-03 11:05 ` Pantelis Antoniou
2004-06-03 15:46 ` Tom Rini
2004-06-03 16:04 ` Matt Porter
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=40BEEA15.3070505@intracom.gr \
--to=panto@intracom.gr \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=porter@cox.net \
--cc=trini@kernel.crashing.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).