All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Jeremy Rosen <Jeremy.Rosen@au.thalesgroup.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Workaround for USB DMA bugs
Date: Thu, 04 Apr 2002 01:16:46 -0500	[thread overview]
Message-ID: <3CABEFCE.8050006@embeddededge.com> (raw)
In-Reply-To: scac60f5.069@au.thalesgroup.com


Jeremy Rosen wrote:


> can't we use the __GFP_DMA flag to specify that the area must have
> algnment enforced ?

Maybe, but that isn't its intended use.

> or did I misunderstand the use of this flag ?

This flag is used on architectures that have memory only accessible
from the processor, not from a DMA device, to ensure a DMA device
gets a memory bank that it can access.


	-- Dan


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

  reply	other threads:[~2002-04-04  6:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-04  4:19 Workaround for USB DMA bugs Jeremy Rosen
2002-04-04  6:16 ` Dan Malek [this message]
2002-04-04  6:32   ` David Gibson
  -- strict thread matches above, loose matches on Subject: below --
2002-04-04  6:40 Rosen Jeremy
2002-04-04  6:52 ` David Gibson
2002-04-03  2:43 David Gibson
2002-04-03  8:17 ` Armin
2002-04-03 17:39   ` Frank Rowand
2002-04-03 17:49   ` Dan Malek
2002-04-03 20:43     ` David Blythe
2002-04-03 23:34       ` David Gibson
2002-04-03  9:45 ` "David Müller (ELSOFT AG)"
2002-04-03 23:35   ` David Gibson
2002-04-03 17:42 ` Dan Malek
2002-04-03 23:40   ` David Gibson
2002-04-04  2:54     ` Dan Malek
2002-04-04  3:48       ` David Gibson
2002-04-04  4:09         ` Dan Malek
2002-04-04  5:23           ` David Gibson
2002-04-04  6:08             ` Dan Malek
2002-04-04  6:30               ` David Gibson
2002-04-04 20:21                 ` David Blythe
2002-04-04 12:35       ` Brad Parker
2002-04-04 14:12         ` Dan Malek

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=3CABEFCE.8050006@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=Jeremy.Rosen@au.thalesgroup.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 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.