On Monday 23 of December 2013 23:08:14 David Gibson wrote: > On Fri, Dec 13, 2013 at 05:49:09PM +0100, Tomasz Figa wrote: > > This series intends to extend dtc with appropriate infrastructure > > to handle property data types. First, dtc is modified to preserve > > type information when parsing DTS. Then type guessing is implemented > > for flat and fs trees where type data is not available. After that, > > DTS generation code is modified to use only type information when > > printing property data. > > Hrm. I think this is completely backwards to the right approach. > > For dt checking what we want is a schema. That can specify datatypes > amongst other constraints, but in the end you can check the actual > bytes of the DT against the constraints imposed by the schema, > regardless of how those bytes are presented to the checker. Those constraints are usually types, so you need a way to extract them from source DTS. > > By adding type information to the in-flight tree you're checking not > the actual content of the DT, but how you've chosen to express that > information in DTS format. > > More concretely, we should be able to schema-check trees in binary > format, not just source. With these patches that will fail if -I dtb > makes the wrong type guesses. I'm not quite sure what do you want to check in binary format, where properties are just strings of bytes. All you can check is whether there is enough bytes or possibly some value constraints on particular parts of it, but not types. IMHO what we primarily need is source validation. Of course using schemas, but that's already decided. Best regards, Tomasz -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
