All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Rowand <frank_rowand@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 11:24:02 -0800	[thread overview]
Message-ID: <3ABA5152.34E4F5B4@mvista.com> (raw)
In-Reply-To: 3ABA1B6A.87C5FE9B@intrex.net


Ralph Blach wrote:
>


>
> David Blythe wrote:


> > I think something more general then pci_alloc_consistent would be
> better
> > for devices that are not pci based.  We are still working on getting a
>
> > pci OHCI usb to work with the walnut card and are running into a lot
> of
> > cache coherency problems.


Dan Malek has provided the functions consistent_alloc(), consistent_free(),
and consistent_sync() for uses other than PCI.  They are in linuxppc_2_5
rev 1.446 and later (I'm not sure if they are in any earlier version).
They are also in my active development kernel, but not yet in any kernel
that I have put on my ftp site.

-Frank
--
Frank Rowand <frank_rowand@mvista.com>
MontaVista Software, Inc

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2001-03-22 19:24 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 ` Frank Rowand [this message]
2001-03-22 19:50   ` Proposed new kernel noncaching memory allocator for the 405gp 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=3ABA5152.34E4F5B4@mvista.com \
    --to=frank_rowand@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.