From: Dan Malek <dan@mvista.com>
To: Ralph Blach <rblach@intrex.net>
Cc: linuxppc-embedded@lists.linuxppc.org,
David Blythe <blythe@routefree.com>
Subject: Re: Proposed new kernel noncaching memory allocator for the 405gp
Date: Thu, 22 Mar 2001 13:27:40 -0500 [thread overview]
Message-ID: <3ABA441C.6261BC52@mvista.com> (raw)
In-Reply-To: 3ABA3A5B.2EFA8D6D@intrex.net
Ralph Blach wrote:
> Using these in the OHCI driver would greatly simply the driver because the
> TD would not be cached.
I'm not sure that is for us to decide. I don't really want to
know that much detail about USB, and the experts that ported these
drivers to processors without cache coherent DMA requested the
functions as you see them now. If they decide they want something
different, we'll provide those. The IBM4xx is a late-comer to
the issues of ensuring cache coherency, and all we are doing is
adopting existing functions that standard Linux software has been
using on other platforms.
> Where are these functions that you say you have implemented?
arch/ppc/8xx_io/commproc.c allocates one (or more) pages of memory
during early initialization, marks them uncached, and will allocate
a few bytes for some drivers. I think only the uart driver uses
this right now for allocating its DMA FIFOs.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-03-22 18:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 15:34 Proposed new kernel noncaching memory allocator for the 405gp Ralph Blach
2001-03-22 16:32 ` Dan Malek
2001-03-22 17:46 ` Ralph Blach
2001-03-22 18:27 ` Dan Malek [this message]
2001-03-23 14:14 ` Kernel Dumps Brad Bonkoski
2001-03-23 15:10 ` Wolfgang Denk
2001-03-22 19:24 ` Proposed new kernel noncaching memory allocator for the 405gp Frank Rowand
2001-03-22 19:50 ` Dan Malek
2001-03-22 20:57 ` Ralph Blach
2001-03-22 21:14 ` Frank Rowand
2001-03-22 21:23 ` Dan Malek
2001-03-22 22:06 ` acmay
2001-03-22 22:18 ` Ralph Blach
2001-03-25 1:42 ` Brad Parker
2001-03-22 23:04 ` andrew may
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=3ABA441C.6261BC52@mvista.com \
--to=dan@mvista.com \
--cc=blythe@routefree.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rblach@intrex.net \
/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).