From: Dan Malek <dan@embeddededge.com>
To: Kevin Fry <kevin@carts.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: allocating non-cacheable memory
Date: Wed, 19 Dec 2001 21:17:44 -0500 [thread overview]
Message-ID: <3C214A48.4080508@embeddededge.com> (raw)
In-Reply-To: 3C214290.D6D1B53A@carts.com
Kevin Fry wrote:
> What is the best way to allocate some non-cacheable memory for I/O use?
> Right now we are going to setup a BAT table with a non-cacheable memory
If you have a processor with BAT, why do you need non-cached memory?
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-20 2:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 1:44 allocating non-cacheable memory Kevin Fry
2001-12-20 2:17 ` Dan Malek [this message]
2001-12-20 4:57 ` Sangmoon Kim
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=3C214A48.4080508@embeddededge.com \
--to=dan@embeddededge.com \
--cc=kevin@carts.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).