linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Silwer star <fariyaf@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: EBC access
Date: Wed, 20 Feb 2008 21:48:42 -0800 (PST)	[thread overview]
Message-ID: <15605219.post@talk.nabble.com> (raw)


Hi,

I am working on the PPC 405EX processor with a peripheral attached to the
EBC. I've requested for I/O memory & mapped it using ioremap. The following
are my doubts:

1) How do I ensure that the memory range that I requested is non-cacheable.
I've to work with non-cacheable memory.  I've requested for memory using
request_mem_region( ). 
2) Between any consecutive writes or any consecutive reads, if I introduce a
delay of 500msec, the read/write is completing.  Does this have to do
anything with caching? What could be the  reason for this?

Any help will be appreciated.

Regards,
Silwer Star
-- 
View this message in context: http://www.nabble.com/EBC-access-tp15605219p15605219.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.

                 reply	other threads:[~2008-02-21  5:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=15605219.post@talk.nabble.com \
    --to=fariyaf@gmail.com \
    --cc=linuxppc-embedded@ozlabs.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).