From mboxrd@z Thu Jan 1 00:00:00 1970 From: Srinivas Kandagatla Subject: Re: [PATCH] ARM: DT: ifc6410: Add board memory range. Date: Thu, 18 Sep 2014 15:16:37 +0100 Message-ID: <541AE945.9030203@linaro.org> References: <1410932179-4652-1-git-send-email-srinivas.kandagatla@linaro.org> <54192B64.6070604@smartplayin.com> <20140917191829.GC3749@joshc.qualcomm.com> <541A01F3.4020303@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-arm-msm-owner@vger.kernel.org To: Bjorn Andersson Cc: Josh Cartwright , Kumar Gala , Pramod Gurav , "linux-arm-kernel@lists.infradead.org" , "devicetree@vger.kernel.org" , linux-arm-msm List-Id: devicetree@vger.kernel.org On 18/09/14 05:37, Bjorn Andersson wrote: > On Wed, Sep 17, 2014 at 2:49 PM, Srinivas Kandagatla > 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 Looks cool.. I think we can ignore this patch with this fixup. On IFC6410 now that we have some way to unbrick the board we could even try to fix this at bootloader level. Thanks to Kumar and You for redirecting me to this link. --srini > > Regards, > Bjorn >