From: Dave K. <du...@gm...> - 2005-11-09 15:05:33
|
Thank you both for the information. I had wrongly assumed that i915_dri.so was a binary provided by Intel. Dave On 11/8/05, Felix K=FChling <fx...@gm...> wrote: > Am Dienstag, den 08.11.2005, 17:05 -0400 schrieb Dave Kavanagh: > > I am looking at adding vblank synchronization support to the i915 drive= r. > > I have a few questions on how all of the pieces fit together and where = the > > source code comes from. > > > > From my understanding, the snapshots such as i915-20051107-linux.i386 > > contain source code that is built to update the kernel DRM modules (i91= 5.ko > > and drm.ko). The snapshot also contains binary files (i915_dri.so and > > i810_drv.o) that are copied over the existing X modules. > > i810_drv.so in the latest version. ;-) We're using the DLLoader now. > > > > > My question is this. Where is the source code that builds the new X mod= ules? > > I found the code that builds the original modules in the X source but I= can't > > find the source for the updated modules. > > The DDX (2D) driver modules are built from Xorg CVS HEAD. The DRI (3D) > driver modules are built from Mesa CVS HEAD. > > > > > I am very new to DRM/DRI so I may be missing something but it seems to = me that > > adding vblank synchronization support will require modifications to bot= h the > > DRM and DRI parts of the equation. > > I don't know what the status of this is in the i915 driver. But in > general you are right. Both DRM and DRI need support for vblank > synchronization, for example by using IRQs. > > > > > Can somebody enlighten me? Any information is appreciated. > > > > Thanks, > > Dave Kavanagh > > > > Regards, > Felix > > -- > | Felix K=FChling <fx...@gm...> http://fxk.de.vu | > | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | > > |