On Sun, 2015-04-19 at 01:31 +0530, Amit Pundir wrote:
AOSP master do not parse "/proc/cpuinfo" anymore to set ro.hardware and other boot related properties [1].
Hurray :-)
We can still boot by either adding "androidboot.hardware=XXX" bootarg (where XXX could be juno/hikey/ifc6410 or any other supported hardware platform) Or by embedding this boot information in the platform device tree blob as suggested by this AOSP commit [2].
I was wondering if ARMLT would be interested in keeping this Android boot related information in dts for Juno?
I can't find any documentation on the 'firmware' device-tree binding, but I can't help but think that:
a) firmware nodes should describe some property of the firmware b) be set by that firmware
Neither of which are true.
So my feeling would be that the 'correct' thing to do would be to use the kernel commandline argument method instead.
(Well, the most correct method IMO is for Android user-side to use the 'compatible' name from device-tree, and other existing device-tree entries if necessary, rather than invent it's own method of identifying the hardware it's running on).