| 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
| ||
|
Message-Id: <E8050509-B096-4171-9406-EE3831F79D71@codeaurora.org> Date: Wed, 4 Mar 2015 15:22:49 -0600 From: Kumar Gala <galak@...eaurora.org> To: Arnd Bergmann <arnd@...db.de> Cc: linux-arm-msm <linux-arm-msm@...r.kernel.org>, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, arm@...nel.org, devicetree@...r.kernel.org, heiko@...ech.de Subject: Re: [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id On Mar 4, 2015, at 3:19 PM, Arnd Bergmann <arnd@...db.de> wrote: > On Wednesday 04 March 2015 15:13:20 Kumar Gala wrote: >> 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> > > This seems to duplicate the root-node compatible strings for no particular > reason, with a less flexible format. I think it would be better to fix > the boot loader. While I wish that was an option, this is a solution that has been shipping on MSM platforms and phones for some time. - k -- 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 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