From: Pantelis Antoniou <panto@intracom.gr>
To: Dan Malek <dan@embeddededge.com>
Cc: Matt Porter <porter@cox.net>,
Tom Rini <trini@kernel.crashing.org>,
Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: new dma API questions
Date: Thu, 03 Jun 2004 14:05:08 +0300 [thread overview]
Message-ID: <40BF05E4.9030604@intracom.gr> (raw)
In-Reply-To: <9A23BE48-B54C-11D8-853B-003065F9B7DC@embeddededge.com>
Dan Malek wrote:
>
> On Jun 3, 2004, at 5:06 AM, Pantelis Antoniou wrote:
>
>
>> 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.
>
>
> It's typically set to zero for all architectures.
>
>> How could we overide it with a constant 0 so that we avoid the
>> memory access?
>
>
> What memory access?
>
Oops, correct :)
>> 2. How soon in the init sequence could we call dma_alloc_consistent?
>
>
> Not soon enough.
>
>> 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.
>
>
> As you pointed out, that is going to have to stay for a while. The
> CPM and peripherals must do DMA long before the generic
> supporting functions are ready.
>
>> 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.
>
>
> I don't think it is worth the complication.
>
Let me work on it a bit...
>
> -- Dan
>
>
>
Regards
Pantelis
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-03 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 9:06 new dma API questions Pantelis Antoniou
2004-06-03 10:56 ` Dan Malek
2004-06-03 11:05 ` Pantelis Antoniou [this message]
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=40BF05E4.9030604@intracom.gr \
--to=panto@intracom.gr \
--cc=dan@embeddededge.com \
--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).