On Tuesday, April 14, 2020 3:33 PM, Daniel Vetter <daniel@xxxxxxxx> wrote: > > What I'm suggesting isn't to make all enum values UAPI. I'm suggesting > > to add standard enum values as #defines in the UAPI headers to make > > these values UAPI. Non-standard properties wouldn't be in the UAPI > > headers, so user-space would need to query values from KMS just like > > they do now. > > Hm that sounds like the half-way that wont work. Because then some > compositors will only use the hard-coded versions, and if they don't > have them, nag us to add them. And then be really disappointed if we > don't (or we screw up and add them where we shouldn't). That's the > status quo "let's have it both ways" that I think is the worst of all > options we have. So I guess from that pov the "userspace needs to > decode from symbolic values, always" as the only consistent one. Fair enough. Let's just continue using symbolic names then. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
