From: Andy Gross <agross@codeaurora.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Varadarajan Narayanan <varada@codeaurora.org>,
Kumar Gala <galak@codeaurora.org>,
David Brown <davidb@codeaurora.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Lina Iyer <lina.iyer@linaro.org>,
Georgi Djakov <gdjakov@mm-sol.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-soc@vger.kernel.org
Subject: Re: [PATCH] ARM: Set proper TEXT_OFFSET for IPQ806x
Date: Thu, 20 Aug 2015 12:20:10 -0500 [thread overview]
Message-ID: <20150820172010.GB10796@qualcomm.com> (raw)
In-Reply-To: <20150820130005.GS7557@n2100.arm.linux.org.uk>
On Thu, Aug 20, 2015 at 02:00:06PM +0100, Russell King - ARM Linux wrote:
> On Thu, Aug 20, 2015 at 05:45:41PM +0530, Varadarajan Narayanan wrote:
> > RAM starts at 0x40000000 for IPQ. The lower 21MB of RAM is used
> > for Shared Memory and the kernel can start from 0x41500000.
>
> Why do people keep creating crap like this? Each time something like
> this is created, it means that you _need_ to have a special kernel for
> your platform and you can't be part of the single zImage.
>
> Please, rather than creating crap like this, find a better way.
In the case of the IPQ, we don't use the zImage because the decompress requires
a larger jump than we can do on that platform. Having this change at least gets
us back 2MB of memory.
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-08-20 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 12:15 [PATCH] ARM: Set proper TEXT_OFFSET for IPQ806x Varadarajan Narayanan
2015-08-20 13:00 ` Russell King - ARM Linux
2015-08-20 17:20 ` Andy Gross [this message]
2015-08-20 19:54 ` Russell King - ARM Linux
2015-08-21 4:59 ` Varadarajan Narayanan
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=20150820172010.GB10796@qualcomm.com \
--to=agross@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=galak@codeaurora.org \
--cc=gdjakov@mm-sol.com \
--cc=lina.iyer@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=sboyd@codeaurora.org \
--cc=varada@codeaurora.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