Hi, >>> + prop->info->print(dev, prop, buffer, sizeof(buffer)); >>> + visit_type_str(v,&ptr, name, errp); >> >> I think you can look at prop->info->type here and do something more >> clever at least for the bool + integer properties. > > That might get a little tough because I want legacy<> types to be > handled as strings. I guess we could promote bool/int to non-legacy types.
Indeed. For chardev and drive properties which will be some kind of link<..> in the new world (correct?) it probably makes sense to keep them as legacy<...>. While being at it: bus properties might need some more thinking here too. Partly they are used for physical addressing, so they will be replaced by link<...> too I guess? Some of them have special parsing and will end up in legacy<...> anyway. Some are plain integers though (hda for example) ... cheers, Gerd
