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
From a conversation on the devicetree-spec mailing list, I asked about how the length element in the ranges property is suppose to be used. A few questions asked (quoted response is from David Gibson):
If a child has a reg outside of the length is it not translated via the range?
Yes.
What if the reg size of a child node overlaps the length? Do we translate up to the point the length specifies?
I believe so, yes.
If #size-cells of the node is 0, does that mean no length element?
I think so, yes, although I don't think I've ever seen a 'ranges'
property on a #size-cells = 0 node.
So if we update the spec, we should clarify such concerns w/ranges.
The text was updated successfully, but these errors were encountered:
From a conversation on the devicetree-spec mailing list, I asked about how the length element in the ranges property is suppose to be used. A few questions asked (quoted response is from David Gibson):
If a child has a reg outside of the length is it not translated via the range?
What if the reg size of a child node overlaps the length? Do we translate up to the point the length specifies?
If #size-cells of the node is 0, does that mean no length element?
So if we update the spec, we should clarify such concerns w/ranges.
The text was updated successfully, but these errors were encountered: