From: Christopher Covington <cov-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Rob Clark <robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
Cc: "Kumar Gala" <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
"Kevin Hilman" <khilman-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-arm-msm
<linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Heiko Stübner" <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
Subject: Re: [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id
Date: Fri, 06 Mar 2015 10:09:36 -0500 [thread overview]
Message-ID: <54F9C330.5090208@codeaurora.org> (raw)
In-Reply-To: <CAF6AEGssMoo6c3nf_7fcATwocuETGZ8nbpGQpUO=KcKWC+rvHw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 03/05/2015 09:28 PM, Rob Clark wrote:
> On Thu, Mar 5, 2015 at 8:59 PM, Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org> wrote:
>> On Thu, Mar 5, 2015 at 12:23 PM, Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> wrote:
>>>
>>> On Mar 5, 2015, at 1:42 PM, Kevin Hilman <khilman-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
>>>
>>>> Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 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: <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
>>>>> Signed-off-by: Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
>>>>
>>>> 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
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: cov@codeaurora.org (Christopher Covington)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id
Date: Fri, 06 Mar 2015 10:09:36 -0500 [thread overview]
Message-ID: <54F9C330.5090208@codeaurora.org> (raw)
In-Reply-To: <CAF6AEGssMoo6c3nf_7fcATwocuETGZ8nbpGQpUO=KcKWC+rvHw@mail.gmail.com>
On 03/05/2015 09:28 PM, Rob Clark wrote:
> On Thu, Mar 5, 2015 at 8:59 PM, Olof Johansson <olof@lixom.net> wrote:
>> On Thu, Mar 5, 2015 at 12:23 PM, Kumar Gala <galak@codeaurora.org> wrote:
>>>
>>> On Mar 5, 2015, at 1:42 PM, Kevin Hilman <khilman@kernel.org> wrote:
>>>
>>>> Kumar Gala <galak@codeaurora.org> 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: <devicetree@vger.kernel.org>
>>>>> Signed-off-by: Kumar Gala <galak@codeaurora.org>
>>>>
>>>> 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
WARNING: multiple messages have this Message-ID (diff)
From: Christopher Covington <cov@codeaurora.org>
To: Rob Clark <robdclark@gmail.com>, Olof Johansson <olof@lixom.net>
Cc: "Kumar Gala" <galak@codeaurora.org>,
"Kevin Hilman" <khilman@kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"arm@kernel.org" <arm@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Heiko Stübner" <heiko@sntech.de>
Subject: Re: [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id
Date: Fri, 06 Mar 2015 10:09:36 -0500 [thread overview]
Message-ID: <54F9C330.5090208@codeaurora.org> (raw)
In-Reply-To: <CAF6AEGssMoo6c3nf_7fcATwocuETGZ8nbpGQpUO=KcKWC+rvHw@mail.gmail.com>
On 03/05/2015 09:28 PM, Rob Clark wrote:
> On Thu, Mar 5, 2015 at 8:59 PM, Olof Johansson <olof@lixom.net> wrote:
>> On Thu, Mar 5, 2015 at 12:23 PM, Kumar Gala <galak@codeaurora.org> wrote:
>>>
>>> On Mar 5, 2015, at 1:42 PM, Kevin Hilman <khilman@kernel.org> wrote:
>>>
>>>> Kumar Gala <galak@codeaurora.org> 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: <devicetree@vger.kernel.org>
>>>>> Signed-off-by: Kumar Gala <galak@codeaurora.org>
>>>>
>>>> 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
next prev parent reply other threads:[~2015-03-06 15:09 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 21:13 [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Kumar Gala
2015-03-04 21:13 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Kumar Gala
2015-03-04 21:13 ` [PATCH v2 2/3] arm64: qcom: Add support for Qualcomm MSM8916 SoC Kumar Gala
2015-03-04 21:13 ` Kumar Gala
2015-03-04 22:33 ` Stephen Boyd
2015-03-04 22:33 ` Stephen Boyd
2015-03-05 15:06 ` Kumar Gala
2015-03-05 15:06 ` Kumar Gala
2015-03-05 16:03 ` Stephen Boyd
2015-03-05 16:03 ` Stephen Boyd
2015-03-04 21:13 ` [PATCH v2 3/3] arm64: dts: Add Qualcomm MSM8916 SoC and evaluation board dts Kumar Gala
2015-03-04 21:13 ` Kumar Gala
2015-03-04 21:19 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Arnd Bergmann
2015-03-04 21:19 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Arnd Bergmann
2015-03-04 21:22 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Kumar Gala
2015-03-04 21:22 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Kumar Gala
2015-03-05 19:42 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Kevin Hilman
2015-03-05 19:42 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Kevin Hilman
2015-03-05 20:23 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Kumar Gala
2015-03-05 20:23 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Kumar Gala
2015-03-06 1:59 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Olof Johansson
2015-03-06 1:59 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Olof Johansson
2015-03-06 2:28 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Rob Clark
2015-03-06 2:28 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Rob Clark
[not found] ` <CAF6AEGssMoo6c3nf_7fcATwocuETGZ8nbpGQpUO=KcKWC+rvHw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-06 15:09 ` Christopher Covington [this message]
2015-03-06 15:09 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Christopher Covington
2015-03-06 15:09 ` Christopher Covington
2015-03-06 16:08 ` Kumar Gala
2015-03-06 16:08 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Kumar Gala
2015-03-06 19:15 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Olof Johansson
2015-03-06 19:15 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Olof Johansson
2015-03-06 20:37 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Kumar Gala
2015-03-06 20:37 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Kumar Gala
2015-03-09 12:11 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Arnd Bergmann
2015-03-09 12:11 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Arnd Bergmann
2015-03-10 17:13 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Kumar Gala
2015-03-10 17:13 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Kumar Gala
[not found] ` <F5017A7F-0EA2-41B3-A9DD-6123CCFD36FA-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-03-10 17:55 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Olof Johansson
2015-03-10 17:55 ` Olof Johansson
2015-03-10 17:55 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Olof Johansson
2015-03-10 18:10 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Kumar Gala
2015-03-10 18:10 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Kumar Gala
2015-03-10 19:52 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Arnd Bergmann
2015-03-10 19:52 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Arnd Bergmann
2015-03-10 19:57 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Kumar Gala
2015-03-10 19:57 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Kumar Gala
2015-03-11 15:33 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Bjorn Andersson
2015-03-11 15:33 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Bjorn Andersson
2015-03-11 15:57 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Kumar Gala
2015-03-11 15:57 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Kumar Gala
[not found] ` <CAJAp7OiVwvPjRbrBxw7Dndvk4Apwz_bx=CzSqeqd3JzYhmB7Kw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-11 20:20 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Arnd Bergmann
2015-03-11 20:20 ` Arnd Bergmann
2015-03-11 20:20 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Arnd Bergmann
2015-03-11 20:35 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Kumar Gala
2015-03-11 20:35 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Kumar Gala
2015-03-11 21:48 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Arnd Bergmann
2015-03-11 21:48 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Arnd Bergmann
2015-03-10 22:01 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Rob Clark
2015-03-10 22:01 ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id Rob Clark
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=54F9C330.5090208@codeaurora.org \
--to=cov-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
--cc=arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
--cc=khilman-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.