You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should require device trees to be backwards compatible. The easiest way to ensure this is to have a tag in the DT that tells reviewers and users of the DT that they can expect backwards compatibility of the device tree.
This tag and requirement of the tag needs to get documented in EBBR. Without the tag, EBBR compliance won't exist.
The tag also needs to get an official binding in the Linux DT binding documents.
The text was updated successfully, but these errors were encountered:
We don't have a clear way forward on this one. I'm closing the issue because we cannot do anything on EBBR until we've got consensus amongst the DT devs.
We should require device trees to be backwards compatible. The easiest way to ensure this is to have a tag in the DT that tells reviewers and users of the DT that they can expect backwards compatibility of the device tree.
This tag and requirement of the tag needs to get documented in EBBR. Without the tag, EBBR compliance won't exist.
The tag also needs to get an official binding in the Linux DT binding documents.
The text was updated successfully, but these errors were encountered: