On Wed 19 Oct 20:17 PDT 2016, Andy Gross wrote:
> On Wed, Oct 19, 2016 at 08:07:25PM -0500, Rob Herring wrote:
[..]
> > Makes sense to me for things like Nexus phones here. What about DB410
> > for example? Is there hope for a fix there? My bootloader is only a
> > couple of months old and needs the properties still.
>
> There won't be a fix for the 410c. We barely got them to respin to use PSCI.
> Stephen can correct me if I am wrong on this.
>
> If this is fixed, it would be 8996+. If..........
>
> So this means introducing the msm-id's for the boards that currently require it,
> and for the boards that will require it in the future. And this would stay in
> effect until the bootloader is able to parse the compatible strings or figure
> this out without the msm-ids.
>
But if the bootloader at any point in the future would support picking a
dtb by compatible strings instead of {msm,board,pmic}-id we wouldn't we
just be back to the ridiculous compatible strings that tipped over into
acceptance to these ids in the first place.
Or do we expect the boot loader to do a deep scan of the dtb to match on
multiple nodes from the tree?
Am I missing something here?
Regards,
Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
