From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755682AbbCFPJp (ORCPT ); Fri, 6 Mar 2015 10:09:45 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:35987 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754379AbbCFPJj (ORCPT ); Fri, 6 Mar 2015 10:09:39 -0500 Message-ID: <54F9C330.5090208@codeaurora.org> Date: Fri, 06 Mar 2015 10:09:36 -0500 From: Christopher Covington User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Thunderbird/36.0 MIME-Version: 1.0 To: Rob Clark , Olof Johansson CC: Kumar Gala , Kevin Hilman , linux-arm-msm , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "arm@kernel.org" , "devicetree@vger.kernel.org" , =?UTF-8?Q?Heiko_St=c3=bcbner?= Subject: Re: [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id References: <1425503602-24916-1-git-send-email-galak@codeaurora.org> <7h8ufbjkod.fsf@deeprootsystems.com> <07D4E4D1-BF8C-4583-9505-9F321DB10406@codeaurora.org> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/05/2015 09:28 PM, Rob Clark wrote: > On Thu, Mar 5, 2015 at 8:59 PM, Olof Johansson wrote: >> On Thu, Mar 5, 2015 at 12:23 PM, Kumar Gala wrote: >>> >>> On Mar 5, 2015, at 1:42 PM, Kevin Hilman wrote: >>> >>>> Kumar Gala writes: >>>> >>>>> The top level qcom,msm-id and qcom,board-id are utilized by bootloaders >>>>> on Qualcomm MSM platforms to determine which device tree should be >>>>> utilized and passed to the kernel. >>>>> >>>>> Cc: >>>>> Signed-off-by: Kumar Gala >>>> >>>> Is this the special magic that allows qcom bootloaders to take a kernel >>>> plus multiple DTBs and figure out which DTB to pass? >>>> >>>> Kevin >>> >>> yes >> >> That's a bummer. >> >> Luckily, the solution for upstream is still quite simple: Provide only >> one devicetree, and it'll be used, right? >> > > I never managed to figure out how to get that to work (at least on my > apq8074 dragonboard.. fortunately ifc6540 seems to work w/ appended > dtb).. kind of a pita because it is a bit of a non-standard boot.img > format too.. I think you're talking about the boot flow from plain poweron which I wish I knew more about, but in case it's any help, here are some fastboot boot steps what worked for me a while back. http://elinux.org/Dragonboard/APQ8074 Chris -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project