I have occasionally seen replies to CVS commit messages on this list, but
I don't find a place where CVS commit messages are sent. Is there such a
place? A few people (me for instance) have pending problems which we know
about (in my case, VIA chipset + AGP gart + Radeon 64 == down in flames)
Hello
i want to update my Linux Kernel 2.2.18 to 2.2.19 can this
brake my working DRI driver modules?
So that i have to recompile the dri tree again?
Best Regards
Oliver C.
___
Dri-devel mailing list
[EMAIL PROTECTED]
Joseph Carter wrote:
I have occasionally seen replies to CVS commit messages on this list, but
I don't find a place where CVS commit messages are sent. Is there such a
place? A few people (me for instance) have pending problems which we know
about (in my case, VIA chipset + AGP gart +
The DRM module from the DRI CVS seems to work fine in 2.4.4.
(The one in the kernel however does seem to be broken.)
Zephaniah E. Hull.
I can't second that.
2.4.4-pre8 (latest pre) was broken (rwsem problem) and the DRI drm module
worked fine but the final 2.4.4 kernel module works smooth.
The DRM module from the DRI CVS seems to work fine in 2.4.4.
(The one in the kernel however does seem to be broken.)
Isn't it generally best to use the module from the CVS/packages in any
case, no matter if the kernel module works? Just alone for the fact that we
then know that the driver
