From: Dan Malek <dan@embeddededge.com>
To: Alex Zeffertt <ajz@cambridgebroadband.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: consistent_alloc() on 82xx
Date: Wed, 8 Jun 2005 12:12:01 -0400 [thread overview]
Message-ID: <d32482ab845e745a00426671eff86b9e@embeddededge.com> (raw)
In-Reply-To: <20050608102938.023f271f.ajz@cambridgebroadband.com>
On Jun 8, 2005, at 5:29 AM, Alex Zeffertt wrote:
> Does anybody know why it isn't built for 6xx cores?
Because 6xx cores are cache coherent and there shouldn't
be any need for "uncached" memory regions.
> I'm working on the ATM driver and it seems that certain external memory
> areas accessed by the PQII CPM by-pass the cache.
That's news to me, and I've written lots of CPM drivers, including ATM.
Do you have a specific example?
Thanks.
-- Dan
next prev parent reply other threads:[~2005-06-08 16:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 9:29 consistent_alloc() on 82xx Alex Zeffertt
2005-06-08 16:12 ` Dan Malek [this message]
2005-06-09 6:15 ` Pantelis Antoniou
2005-06-09 9:06 ` Alex Zeffertt
2005-06-09 18:05 ` Dan Malek
2005-06-09 9:04 ` Alex Zeffertt
2005-06-09 19:05 ` Dan Malek
2005-06-10 10:11 ` Alex Zeffertt
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=d32482ab845e745a00426671eff86b9e@embeddededge.com \
--to=dan@embeddededge.com \
--cc=ajz@cambridgebroadband.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).