From: Marek Szyprowski <m.szyprowski@samsung.com>
To: monstr@monstr.eu, "'Russell King - ARM Linux'" <linux@arm.linux.org.uk>
Cc: "'Kyungmin Park'" <kyungmin.park@samsung.com>,
"'Ohad Ben-Cohen'" <ohad@wizery.com>,
"'LKML'" <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: RE: CMA on arm from zero address
Date: Wed, 08 Feb 2012 14:30:02 +0100 [thread overview]
Message-ID: <000c01cce665$c3394ee0$49abeca0$%szyprowski@samsung.com> (raw)
In-Reply-To: <4F3276D6.3060507@monstr.eu>
Hello,
On Wednesday, February 08, 2012 2:21 PM Michal Simek wrote:
> Russell King - ARM Linux wrote:
> > On Wed, Feb 08, 2012 at 01:27:58PM +0100, Michal Simek wrote:
> >> Hi,
> >>
> >> I would like to setup CMA space at the beginning of ram because
> >> I want to use remoteproc to run code on the second cpu which has to
> >> use addresses 0x0 - 32MB.
> >>
> >> I have changed textofs in arch/arm/Makefile but there is not possible
> >> to setup all values which I would like to use.
> >
> > What a broken setup. Placing the kernel outside of the 16MB window
> > effectively prevents you from using modules. Why do people come up
> > with stupid things like this. Please stop. Put such things at the
> > end of RAM instead and save the rest of the ARM community from this
> > madness.
>
> First of all I have found how to do it (by CONFIG_PHYS_OFFSET) so the problem is in QEMU.
> Currently experimenting how to convince CMA to allocate that memory for my purpose.
I'm not sure if CMA is the right allocation api for this purpose. You should
better use memblock allocator to grab specific address ranges for your custom
setup. Alternatively you can compile Linux kernel to start physical memory
at 16MiB and access the 0-16MiB range with ioremap for example.
(snipped)
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
prev parent reply other threads:[~2012-02-08 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 12:27 Michal Simek
2012-02-08 13:08 ` Russell King - ARM Linux
2012-02-08 13:21 ` Michal Simek
2012-02-08 13:26 ` Russell King - ARM Linux
2012-02-10 10:15 ` Michal Simek
2012-02-08 13:30 ` Marek Szyprowski [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='000c01cce665$c3394ee0$49abeca0$%szyprowski@samsung.com' \
--to=m.szyprowski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=monstr@monstr.eu \
--cc=ohad@wizery.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
all inboxes | Powered by JetHome®