As indicated here:
the input to CRTC is the framebuffer, and output of CRTC is already monitor-level information...which is meaningless to you. So but best bet is to get it at the framebuffer level?
Correct me if wrong?
On Thu, Jan 16, 2014 at 8:06 PM, Sannu K <sannumail4foss@xxxxxxxxx> wrote:
On Thu, Jan 16, 2014 at 1:14 PM, Peter Teoh <htmldeveloper@xxxxxxxxx> wrote:
In general how it worked is explained here:Not sure which is the name of your video card, but I think in general all the page flip API should have access to the scan buffer (see link above). For Intel these are possible APIs:
Thanks. I was trying to find out a generic way to access the scan out buffer. The page flip functions looks specific to hardware.
static void do_intel_finish_page_flip(struct drm_device *dev,void intel_finish_page_flip(struct drm_device *dev, int pipe)do_intel_finish_page_flip(dev, crtc);void intel_finish_page_flip_plane(struct drm_device *dev, int plane)do_intel_finish_page_flip(dev, crtc);void intel_prepare_page_flip(struct drm_device *dev, int plane)* is also accompanied by a spurious intel_prepare_page_flip().inline static void intel_mark_page_flip_active(struct intel_crtc *intel_crtc)
--
Regards,
Peter Teoh
It is enough to have a way to get the content of scan out buffer instead of accessing it directly using a pointer.Thanks for you help,Sannu K
Regards,
Peter Teoh
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
