A while back when discussing property iterators (http://ozlabs.org/pipermail/linuxppc-dev/2008-January/049891.html), you said that you'd prefer not to expose property offsets, because more common uses would be affected by changing offsets. I'm looking again at this, and was wondering what alternative and would-be-broken use cases you were thinking of?
We could operate on property indices or names at an efficiency cost. Most nodes should be small enough that the cost isn't too much, but I'd like to know which use cases really need it. The ones I'd use it for involve reading from one tree and adding to another, so moving offsets aren't an issue. Even in a use case where one makes in-place changes while iterating over properties, changes to the property currently being iterated over should only move later properties -- the next call to fdt_next_prop would be based on the start of the property that was modified, which did not change. -Scott _______________________________________________ devicetree-discuss mailing list [email protected] https://ozlabs.org/mailman/listinfo/devicetree-discuss
