From: Conor McLoughlin <cml3227@eircom.net>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Does kmalloc on MPC82xx work correctly with GFP_DMA?
Date: Tue, 19 Oct 2004 16:26:27 +0100 [thread overview]
Message-ID: <41753223.2030202@eircom.net> (raw)
In-Reply-To: <5925F5E8-21D9-11D9-A47E-003065F9B7DC@embeddededge.com>
Thanks to everyone who replied. I appreciate your time to help
educate me.
> It works because the 82xx is cache coherent. The MMU mapping
> is irrelevant.
That is the missing piece of the puzzle. I had worked with the 860
before and this was an issue. It hadn't occurred to me that the 82xx
was different.
> There is no bug here. Just because people don't
> understand how something works doesn't mean there is a bug
> present.
The reason I asked the question in the first place was because I didn't
understand how it could work. I now understand it and can rest easier.
Thanks,
Conor
next prev parent reply other threads:[~2004-10-19 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 4:01 SCC UART hang Jeff Angielski
2004-10-18 9:30 ` Does kmalloc on MPC82xx work correctly with GFP_DMA? Conor McLoughlin
2004-10-18 15:31 ` Dan Malek
2004-10-19 8:36 ` Conor McLoughlin
2004-10-19 14:15 ` Dan Malek
2004-10-19 15:26 ` Conor McLoughlin [this message]
2004-10-19 14:31 ` Matt Porter
2004-10-19 14:27 ` Matt Porter
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=41753223.2030202@eircom.net \
--to=cml3227@eircom.net \
--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).