[lkml]   [2015]   [Mar]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id
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..

Otoh getting an upstream (or even different kernel) kernel working can
be hard enough as-is on random different tablet/phone/etc. Why not
make whoever tries' life a bit easier by allowing some nonsense node
into the qcom dtbs which makes it compatible w/ bootloaders already
out there in the field ;-)


> -Olof
> --
> To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
> the body of a message to
> More majordomo info at

 \ /
  Last update: 2015-03-06 03:41    [W:0.070 / U:0.084 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site