linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Rune Torgersen <runet@innovsys.com>
To: Mark Chambers <markc@mail.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Why not kmalloc() ??
Date: Fri, 16 Jul 2004 10:42:15 -0500	[thread overview]
Message-ID: <1089992535.1546.37.camel@runet> (raw)
In-Reply-To: <005d01c46b3e$12adf030$0301a8c0@chuck2>


On Fri, 2004-07-16 at 09:06, Mark Chambers wrote:
> Is there any reason to use m8xx_cpm_hostalloc() over dma_alloc_consistent()
> for a loadable driver (that is, one loaded after VM initialized)?

Yous should even be able to use kmalloc(x, GFP_KERNEL | GFP_DMA)

This works on 82xx CPU's (and is actually used as a replacement for hostalloc
on the rewritten cpm memory allocation stuff that is yet to be released)

Might not work on 8xx though...


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

  reply	other threads:[~2004-07-16 15:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-16  9:25 Why not kmalloc() ?? Rupesh S
2004-07-16 10:25 ` kernel 2.4.26 doesn't seem to work with a MPC859T Pedro Aguilar
2004-07-16 11:34 ` Why not kmalloc() ?? Magnus Damm
2004-07-16 12:06   ` sanjeev ramachandran
2004-07-16 13:32     ` Dan Malek
2004-07-16 14:06       ` Mark Chambers
2004-07-16 15:42         ` Rune Torgersen [this message]
2004-07-16 19:03           ` Dan Malek
2004-07-16 19:02         ` Dan Malek
2004-07-16 13:29   ` Dan Malek
2004-07-16 11:46 ` Dan Malek
  -- strict thread matches above, loose matches on Subject: below --
2004-07-17  4:51 Rupesh S

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=1089992535.1546.37.camel@runet \
    --to=runet@innovsys.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=markc@mail.com \
    /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).