2011/1/3 Pekka Paalanen :
> On Wed, 22 Dec 2010 10:51:26 +0100
> Sedat Dilek wrote:
>
>> DRIVER_DATE is not maintained or upgraded on changes in many drm
>> drivers.
>>
>> For example radeon has one DRIVER_DATE for User and Kernel
>> ModeSetting driver, this makes no sense as UMS and KMS driver
>>
On Wed, 22 Dec 2010 10:51:26 +0100
Sedat Dilek wrote:
> DRIVER_DATE is not maintained or upgraded on changes in many drm
> drivers.
>
> For example radeon has one DRIVER_DATE for User and Kernel
> ModeSetting driver, this makes no sense as UMS and KMS driver
> have different versions. And of cou
On Wed, 22 Dec 2010 10:51:26 +0100
Sedat Dilek wrote:
> DRIVER_DATE is not maintained or upgraded on changes in many drm
> drivers.
>
> For example radeon has one DRIVER_DATE for User and Kernel
> ModeSetting driver, this makes no sense as UMS and KMS driver
> have different versions. And of cou
DRIVER_DATE is not maintained or upgraded on changes in many drm drivers.
For example radeon has one DRIVER_DATE for User and Kernel ModeSetting
driver, this makes no sense as UMS and KMS driver have different versions.
And of course this all increases maintenance, too.
For radeon it is enough to
DRIVER_DATE is not maintained or upgraded on changes in many drm drivers.
For example radeon has one DRIVER_DATE for User and Kernel ModeSetting
driver, this makes no sense as UMS and KMS driver have different versions.
And of course this all increases maintenance, too.
For radeon it is enough to