| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 5 Mar 2015 17:59:35 -0800 From: Olof Johansson <olof@...om.net> To: Kumar Gala <galak@...eaurora.org> Cc: Kevin Hilman <khilman@...nel.org>, linux-arm-msm <linux-arm-msm@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "arm@...nel.org" <arm@...nel.org>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, Heiko Stübner <heiko@...ech.de> Subject: Re: [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id On Thu, Mar 5, 2015 at 12:23 PM, Kumar Gala <galak@...eaurora.org> wrote: > > On Mar 5, 2015, at 1:42 PM, Kevin Hilman <khilman@...nel.org> wrote: > >> Kumar Gala <galak@...eaurora.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@...r.kernel.org> >>> Signed-off-by: Kumar Gala <galak@...eaurora.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? -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists