From: Bjorn Andersson <bjorn@kryo.se>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Josh Cartwright <joshc@codeaurora.org>,
Kumar Gala <galak@codeaurora.org>,
Pramod Gurav <pramod.gurav@smartplayin.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH] ARM: DT: ifc6410: Add board memory range.
Date: Wed, 17 Sep 2014 21:37:59 -0700 [thread overview]
Message-ID: <CAJAp7Og5v-ADm6ekMVUs8++CL5NP+OEw-vZ7mKdChOZyBTBZpA@mail.gmail.com> (raw)
In-Reply-To: <541A01F3.4020303@linaro.org>
On Wed, Sep 17, 2014 at 2:49 PM, Srinivas Kandagatla
<srinivas.kandagatla@linaro.org> wrote:
>
>
> On 17/09/14 20:18, Josh Cartwright wrote:
>>
>> On Wed, Sep 17, 2014 at 12:03:37PM -0700, Kumar Gala wrote:
[..]
>>> Hmm, this doesn?t seem to work for me.
>>
>>
>> I don't see how it could with qcom_defconfig, as we set
>> CONFIG_ARM_ATAG_DTB_COMPAT. Is this patch fixing a real issue?
>
> No, its not fixing any thing by itself.
>
> However along with "ARM: zImage: Allow DTB to override broken ATAG_MEM"
> patch atleast I get to boot my IFC6410 with multi_v7_defconfig.
But that patch was rejected by various people.
Instead have a look at [1], it solves the problem for you (and have
reference to the original source).
[1] https://github.com/andersson/kernel/commit/d4c0061cf7be8a341e6d06a97c85ecb69284e74c
Regards,
Bjorn
next prev parent reply other threads:[~2014-09-18 4:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 5:36 [PATCH] ARM: DT: ifc6410: Add board memory range Srinivas Kandagatla
2014-09-17 6:34 ` Pramod Gurav
2014-09-17 19:03 ` Kumar Gala
2014-09-17 19:18 ` Josh Cartwright
2014-09-17 21:49 ` Srinivas Kandagatla
2014-09-18 4:37 ` Bjorn Andersson [this message]
2014-09-18 14:16 ` Srinivas Kandagatla
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=CAJAp7Og5v-ADm6ekMVUs8++CL5NP+OEw-vZ7mKdChOZyBTBZpA@mail.gmail.com \
--to=bjorn@kryo.se \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=joshc@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=pramod.gurav@smartplayin.com \
--cc=srinivas.kandagatla@linaro.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).