Most of it should be supported by mainline kernel, so itās mostly just writing a new DTS and config for the new base board. Pretty much daily business for us kernel hackers.
Whatās the big problem here ?
Take a recent android tree, put in new kernel (w/ board specific config) and new mesa.
Canāt be that big deal.
That would imply other changes, eg. new case.
IOW: a really new device.
Simple: When modules arenāt fully compatible anymore.
Iād call the variant w/ just new baseboard 2.1.
Simple: within each generation, the individual components are versioned separately.
Eg. if the cam module is upgraded, it will be version 2.
The only thing that might require some more thoughts is proper module probing
(if the modules dont already come w/ some generic identification mechanism, eg. a tiny i2c eprom, etc). But thatās all solvable, once the specs are on the table.