> On 16 Jul 2001 12:00:23 -0600, Jeff Hartmann wrote:
> [...]
>
>> will do this. This will make the 4.0 -> 4.1 have to be a compile time
>> decision, but 4.1 -> 4.1.1 and higher will just coexist with each
>> other. I'm currently working out integrating this into the kernel
>> build, and I should hopefully have a patch for Linus and Alan soon.
>
>
> I would have preferred if you were just versionning vs the API, not the
> X version (and keep the API rather stable).
The problem is that the API can't be completely stable because of the 3D
client-side drivers, 2D ddx drivers, and the drm kernel modules have to
be tightly coupled. The drm kernel module has to provide a secure
method of sending data to the card, but we also want it to be efficent.
For example, the mesa-3.5 versions of the drm kernel modules can send
multiple states inside one dma buffer, this greatly increases the
efficency of the driver, but it costs API compatibility. We do version
the API, and will not attempt to use the drivers if their API versions
are wrong. However we want multiple versions of the API to coexist.
Adding the version number to the module name will allow for all the
versions to coexist.
> I wouldn't like to update my
> kernel just to go from X 4.1.1 to X 4.1.1-pl1.
Well if there are changes to the drm kernel drivers, you have to update
your kernel or compile the kernel modules by hand. We could easily
create a stable API if cards were secure, or we did not care about
security. Unfortunately neither one is the case, so the API is not
completely static.
-Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/