On 10-08-15, 14:22, Lee Jones wrote: > > Optional properties: > > +- opp-cuts: One or more strings, describing the versions of hardware the > > OPPs > > + can support. > > This isn't very generic. > > I'm guessing some vendors my have quite a few ways to differentiate > between board versions/revisions/cuts etc. > > How about another array where a vendor can choose to identify a piece > of hardware however they see fit. > > Example 1 (simple version): > > /* Version 1 */ > opp-version = <1>; > > Example 2 (using the kernel's versioning): > > /* 2.6.32-rc1 */ > opp-version = <2 6 32 1>; > > Example 3 (using ST's versioning): > > /* Major 2, Minor 0, Cut 2, All substrates */ > opp-version = <2 0 2 0xff>;
But how will we parse this with generic code ? -- viresh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
