Ok, thanks everybody for the suggestions!! I already had XFree86 4.2.0 downloaded, configured (defaults except for install locations) and compiled, just not installed.
So I started looking in the source code. It looks like what I would want to do is change the call to shadowAdd in xc/programs/Xserver/hw/xfree86/drivers/fbdev/fbdev.c to not pass in shadowUpdatePacked, but instead pass it the address of my own function which i will base off of shadowUpdatePacked in xc/programs/Xserver/miext/shadow/shpacked.c. Actually it looks like the call to *pBuf->window is what does the actual updating, so I'll have to go find that code and create my own version of it in my replacement for shadowUpdatePacked. does this sound right? thanks again On Tue, Feb 12, 2002 at 06:46:57PM +0100, Michel D�nzer wrote: > On Tue, 2002-02-12 at 18:17, Kevin Geiss wrote: > > > So, what i need to do is figure out how to intercept accesses to the > > frame buffer memory to enforce the memory write speed limit and the > > 32-pixel-at-a-time rule. > > You can optionally provide a special update function for the shadow > framebuffer which sticks to the rules. Looking for 'shadow' in the fbdev > driver source should get you started, then you'll likely soon ask back > more specific questions. :) BTW make sure to work with 4.2.0 or current > CVS, the shadow framebuffer code in the fbdev driver has improved a lot > since 4.1.0. > > > -- > Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer > XFree86 and DRI project member / CS student, Free Software enthusiast > _______________________________________________ > Xpert mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xpert
msg04138/pgp00000.pgp
Description: PGP signature
