help required for Frame buffer update region

[sanjeev sinha <sinha_crl@yahoo.co.in>]

[-- Attachment #1.1: Type: text/plain, Size: 1864 bytes --]

 
  Dear all,
   
  I am a student.My academic project is similar to VNC. I have to design remote display sharing and on linux.
  For that what I did is I accessed the frame buffer using fixed info and varable info structure (include/fb.h) , IOCTL  and mmap call(after enabling the frame buffer). Problem is that I have to send this frame buffer memory area to other network computer to display the complete picture (like VNC). I can not send complete frame buffer every  time(1.5-2. MB). I want to send the complete fb once and then the updated  region only. Is there any way by which I can directly know what all frame buffer memory region has been updated so that I will send only that portion. Otherwise I have to compare all the bytes,compress it and send.But this will have refresh rate (effiency ) issue. Please help me
   
   
   
  After mmap application is not writing anything to framebuffer pointer(descriptor).
  For every update kernel is writing. So we can not make the mmap with read option and find the page fault and send the updated pages. This option (in this way ) is ruled out.
   
  I have one idea. All the X calls to driver (for display update) can be hooked and then I will send those calls (hook Information) to remote computer where in the display can be updated using this hook information. I don't know how to hook the display. In window it can be done ( I got this window info from Net),but in linux I am not aware of it.If you can help , please suggest.
   
   
  The later part of my project is both the display should behave as dual head.Now I am blank about how to share the frame buffer area of one CPU on two display screen like dual head.please help me in this matter also.
   
  Regards,
  Sanjeev
   
  

 

       
---------------------------------
 Unlimited freedom, unlimited storage. Get it now

[-- Attachment #1.2: Type: text/html, Size: 2272 bytes --]

[-- Attachment #2: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 182 bytes --]

_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel