From: Dan Malek <dan@mvista.com>
To: frowand@mvista.com
Cc: Ralph Blach <rblach@intrex.net>,
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 14:50:00 -0500 [thread overview]
Message-ID: <3ABA5768.6986524B@mvista.com> (raw)
In-Reply-To: 3ABA5152.34E4F5B4@mvista.com
Frank Rowand wrote:
> Dan Malek has provided the functions consistent_alloc(), consistent_free(),
> and consistent_sync() for uses other than PCI.
But, what I haven't yet done is modify the general PowerPC PCI
functions (like pci_consistent_alloc()) to use these lower level
functions on the MPC8xx or the IBM4xx. If you want to hack those
PCI functions in your local sources, go ahead, as the plan is to
make those work. I just have to test against other platforms to
ensure I didn't break something, which is much more time consuming
that just making them work for a specific test environment.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-03-22 19:50 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
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 [this message]
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=3ABA5768.6986524B@mvista.com \
--to=dan@mvista.com \
--cc=blythe@routefree.com \
--cc=frowand@mvista.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).