linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark S. Mathews" <mark@linux-wlan.com>
To: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: 405EP and pci_alloc_consistent()
Date: Thu, 19 Aug 2004 13:11:30 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0408191303100.3546@chef.linux-wlan.com> (raw)


Hi Folks,

I've got a wlan driver I'm running on a 405EP target with the 2.4.27
rsynch'd from the mvista site last week (my customer did that, I don't
have the exact details).

This device/driver relies on a dma'd 'control block' where all the queues
(heads,tails,metadata etc.) are managed.  We allocate that block with
pci_alloc_consistent().  I had some trouble with stale values until I
wrapped all the accesses of the block with invalidate_dcache_range()
before reads and flush_dcache_range() after writes.

I don't have a problem with the necessity to do all that, but it does
leave me a little uncomfortable.  I thought the pci_alloc_consistent call
should mark the tlb entrie(s) for that memory as non-cacheable.  Am I
missing something?

Thanks,
-Mark

--

Mark S. Mathews

AbsoluteValue Systems      Web:    http://www.linux-wlan.com
721-D North Drive          e-mail: mark@linux-wlan.com
Melbourne, FL 32934        Phone:  321.259.0737
USA                        Fax:    321.259.0286

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

             reply	other threads:[~2004-08-19 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19 17:11 Mark S. Mathews [this message]
2004-08-19 17:36 ` 405EP and pci_alloc_consistent() Eugene Surovegin
2004-08-19 18:26   ` Mark S. Mathews

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=Pine.LNX.4.61.0408191303100.3546@chef.linux-wlan.com \
    --to=mark@linux-wlan.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 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).