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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160628171759.GZ1521@codeaurora.org>
Date:	Tue, 28 Jun 2016 10:17:59 -0700
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:	Andy Gross <andy.gross@...aro.org>,
	Rob Herring <robh+dt@...nel.org>,
	David Brown <david.brown@...aro.org>,
	devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
	linux-soc@...r.kernel.org
Subject: Re: [PATCH 1/8] arm64: dts: db820c: add basic board support

On 06/21, Srinivas Kandagatla wrote:
> I agree, this should match up with the dtbTool. I have been manually
> patching up dtb to include the board-id, pmic id stuff.

Uh oh :/

> 
> I will fix it in next version,
> 
> Did not look at full details but, For some reason dtbTool does not
> support multiple compatible strings, do you think it makes sense to
> add this support in dtb tool to cope up with compatible strings
> like:
> 
> compatible = "qcom,apq8096-db820c", "qcom,apq8096-sbc";
> 

Hmm I suppose we can add support to look for the first compatible
that matches something that we can generate an id for? That would
allow us to have the LK compatible and then whatever is more
specific than that which the bootloader doesn't care about.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ