From: Ameya Palande <ameya.palande@nokia.com>
To: "ext Kanigeri, Hari" <h-kanigeri2@ti.com>
Cc: "Doyu Hiroshi (Nokia-D/Helsinki)" <hiroshi.doyu@nokia.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"2ameya@gmail.com" <2ameya@gmail.com>
Subject: Re: [PATCH 1/1] DSPBRIDGE: move platform_device_register under mach-omap2
Date: Wed, 25 Mar 2009 15:16:59 +0200 [thread overview]
Message-ID: <49CA2ECB.5040204@nokia.com> (raw)
In-Reply-To: <8F7AF80515AF0D4D93307E594F3CB40E2349AE08@dlee03.ent.ti.com>
ext Kanigeri, Hari wrote:
> Thanks, Doyu-San.
>
> I am still going through the patch, but one quick question regarding this. One of the requirements of DSP memory pool is that it should be physically contiguous and non-cacheable. I hope the below patch is taking care of this requirement.
>
> Thank you,
> Best regards,
> Hari
>
Hi Hari,
I just checked __alloc_bootmem_nopanic() function.
I think memory allocated by that function is physically contiguous since
page frames are allocated in sequential order.
But I didn't get any information about page cacheing :(
Cheers,
Ameya.
prev parent reply other threads:[~2009-03-25 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 11:51 [PATCH 1/1] DSPBRIDGE: move platform_device_register under mach-omap2 Hiroshi DOYU
[not found] ` <8F7AF8 0515AF0D4D93307E594F3CB40E2349AE08@dlee03.ent.ti.com>
[not found] ` <20090325.151129.02294 438.Hiroshi.DOYU@nokia.com>
2009-03-25 12:53 ` Kanigeri, Hari
2009-03-25 13:11 ` Hiroshi DOYU
2009-03-26 12:23 ` Hiroshi DOYU
2009-03-26 13:24 ` Problem in Flashing uboot on OSK5912c Manoj Kotnala
2009-03-26 18:54 ` Suresh Rajashekara
2009-03-27 14:39 ` Philip Balister
2009-03-30 15:47 ` Manoj Kotnala
2009-03-27 13:42 ` [PATCH 1/1] DSPBRIDGE: move platform_device_register under mach-omap2 Kanigeri, Hari
2009-03-27 15:30 ` Hiroshi DOYU
2009-03-28 13:50 ` Kanigeri, Hari
2009-03-25 13:16 ` Ameya Palande [this message]
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=49CA2ECB.5040204@nokia.com \
--to=ameya.palande@nokia.com \
--cc=2ameya@gmail.com \
--cc=h-kanigeri2@ti.com \
--cc=hiroshi.doyu@nokia.com \
--cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.