> On 17 Jun 2026, at 4:48 PM, Eric Auger <[email protected]> wrote: > > Few notes: > - I saw there are capabilities to define property aliases (source and > destination types must match though). So there could be way to associate > a FEAT_ property to SYSREG property for those who strictly match. > > - In case people would like to have labelled strings, we could turn the > SYSREG props, which are currently uint64 into string props. on set we > would convert the string into the isar uint64. > You could maintain a separate description file that associate enum > values to string values. If an association exists we would do an > intermediate translation. >
This is my plan, but for v3 I am not focusing on property types/names. Let’s get infra/models without that first. User friendly properties will be a separate effort. Warm Regards, Khushit
