Am Sonntag, 13. Oktober 2002 20:49 schrieb Linus Torvalds: > On Sun, 13 Oct 2002, Dieter Nützel wrote: > > But maybe it is related to my 2.5.42-mm1 kernel. It do not include the > > latest DRI CVS DRM code and DRI CVS DRM do not compile with this kernel. > > Actually, you should be able to just use the in-kernel DRM code, since it > is actually up-to-date wrt the CVS tree apart from some minor MGA DMA > updates and an added pci_enable_device() - which should be a non-issue if > you already see interrupts from your gfx card. > > (The current BK tree has those things merged too, fwiw)
OK, hoped that. Thank you Linus. But I didn't get this with 2.4.19/2.4.20-preX plus DRI CVS DRM module. VTK/bin> ut& [1] 4193 VTK/bin> r200CreateScreen bad type 0x0 for device fcntl: Invalid argument fcntl: Invalid argument [1] Fertig ut Second, do you think that latency could be "optimized" for the current DRM/2.5.42+ kernels. With Robert Love's 2.4.XX preemption patch I had much better responseability (latencytest0.42-png numbers) together with my V5 5500 (tdfx driver). -Dieter ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
