An issue raised by DRM people with the new drm core is how to stop users
shotting themselves in the foot when upgrading drm modules from CVS and
mixing up cores and drivers...
This patch (against DRM CVS) proposes a simple internal version that gets
passed from the module to the core, when built
How strong of match requirement do we need? Note that this only
impacts distribution of binary personality modules, if you have source
there is no problem.
Several stronger solutions:
on each CVS check-in to DRM increment a count and use this for an id
manual version number for DRM
embed the
How strong of match requirement do we need? Note that this only
impacts distribution of binary personality modules, if you have source
there is no problem.
Not really I'm thinking more of someone building a module against one core
and insmodding it against another one.. so someone builds a
