quoted

quoted

I don't think vfb's framebuffer can be mmapped.  It's fixable, but
nobody seems to have a need for it,  yet.

Tony

fb is getting successfully mapped.. its just that memcpy gives bus error
when i try to copy the mapped memory of framebuffer device to a "mapped
file,"

Well, I am able to get the ball rolling by writing the mapped framebuffer
onto the file by using write system call

Unless you modified vfb yourself, it's not possible because
fix->smem_start is not set all (it's pointing to NULL). What's actually
being mmapped is physical addres 0UL.

what i wanted to do......as i wrote in my very first mail........ i
have got that, now i am able to capture the snapshot using c program
and the results are output on my screen....
      printf("frame bufffer mapped  @ %p\n", src);
      for(i = 0; i < vinfo.xres*vinfo.yres*vinfo.bits_per_pixel/8; i++)
                *src++ = 0xBB;

Framebuffer is getting mapped... by mmap system call
  // Map the device to memory
        src = (char *)mmap(0, screensize, PROT_READ|PROT_WRITE,
MAP_SHARED, fdin, 0);
        if ((int)src == -1) {
                printf("Error: failed to map framebuffer device to memory.\n");
                return -1;
        }

and therefore  physical addres 0UL is not what is mapped.....its the
framebuffer.
doubt in my last mail was w.r.t memcpy().

thanx,
vishal.

Tony

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV