Am 24.06.2014 10:17, schrieb Markus Armbruster: > Back then gerd created a way to do the compatibility stuff without > getting into the other target's hair: compat_props. They've served us > well enough, but now that more targets get interested in migration, > their shortcomings start to hurt. Having to duplicate device > compatibility gunk in multiple places, all far away from the device, is > decidedly suboptimal. Better ideas welcome.
Might it make sense to reconsider the proposed machine type hierarchy and have machine-2.2 <- pc-i440fx-2.2, with global properties in machine-x.y types and pc_compat_x_y() taking care of PC inheritence? We can't inherit from both pc-x.y and machine-x.y though, so probably not, just throwing thoughts around. Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
