From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Omar Ramirez Luna <omar.ramirez@ti.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
Tony Lindgren <tony@atomide.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
Fernando Guzman Lugo <x0095840@ti.com>,
Rene Sapiens <rene.sapiens@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH 01/02] omap: dsp: remove shm from normal memory
Date: Thu, 2 Dec 2010 21:32:13 +0000 [thread overview]
Message-ID: <20101202213213.GI10461@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1289440225-27221-2-git-send-email-omar.ramirez@ti.com>
On Wed, Nov 10, 2010 at 07:50:24PM -0600, Omar Ramirez Luna wrote:
> From: Felipe Contreras <felipe.contreras@gmail.com>
>
> Also, don't be picky about the location, which incidentally fixes the
> build since MEMBLOCK_REAL_LIMIT is gone on 2.6.37.
That comment is wrong. memblock_alloc() is still as picky as the
original.
phys_addr_t __init memblock_alloc(phys_addr_t size, phys_addr_t align)
{
return memblock_alloc_base(size, align, MEMBLOCK_ALLOC_ACCESSIBLE);
}
/* Pump up max_addr */
if (end == MEMBLOCK_ALLOC_ACCESSIBLE)
end = memblock.current_limit;
and current_limit is initialized to what was MEMBLOCK_REAL_LIMIT. So,
memblock_alloc() will always allocate from lowmem.
next prev parent reply other threads:[~2010-12-02 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 1:50 [PATCH 00/02] staging: tidspbridge: 2.6.37-rcX fixes Omar Ramirez Luna
2010-11-11 1:50 ` [PATCH 01/02] omap: dsp: remove shm from normal memory Omar Ramirez Luna
2010-12-02 21:32 ` Russell King - ARM Linux [this message]
2010-11-11 1:50 ` [PATCH 02/02] staging: tidspbridge: hardcode SCM macros while fix is upstreamed Omar Ramirez Luna
2010-11-11 13:17 ` [PATCH 00/02] staging: tidspbridge: 2.6.37-rcX fixes Greg KH
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=20101202213213.GI10461@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=devel@driverdev.osuosl.org \
--cc=felipe.contreras@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=omar.ramirez@ti.com \
--cc=rene.sapiens@ti.com \
--cc=tony@atomide.com \
--cc=x0095840@ti.com \
/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