On Thu, 26 May 2011 10:10:16 -0400 Matt Edinger <[email protected]> said:
> Hello, > I apologize in advance for this noob question... > I've been attempting to run the example program "evas-buffer-simple.c" > on a Phycore LPC3250 ARM based development board. EFL is installed on a > 586 desktop running Fedora 11. I can cross-compile evas-buffer-simple > and get an executable that runs on the target LPC3250 board running > Linux kernel version: 2.6.34. I can start Xfbdev and get the default > graphics on the attached touchscreen as follows: > > -------------- > [root@nxp etc]# Xfbdev -ac -nolisten inet6 -mouse > tslib,,device=/dev/input/event0 -kb & > > [root@nxp etc]# Couldn't find keyboard driver keybd > -------------- > > The “Xfbdev” screen comes up and the cursor responds. > Now if I try to run evas-buffer-simple, I get the following: > > -------------- > [root@nxp user]# ./evas-buffer-simple > > initial scene, with just background: > UPDATED REGION: pos: 0, 0 size: 320x240 > final scene (note updates): > UPDATED REGION: pos: 10, 10 size: 102x102 > saved scene as '/tmp/evas-buffer-simple-render.ppm' > > [root@nxp user]# > -------------- > > The file evas-buffer-simple-render.ppm contains the expected graphic > pattern. However, nothing shows up on the graphics display. > Additionally, running evas-buffer-simple a second time gives the > following result: > > -------------- > [root@nxp user]# ./evas-buffer-simple > initial scene, with just background: > UPDATED REGION: pos: 0, 0 size: 320x240 > final scene (note updates): > UPDATED REGION: pos: 10, 10 size: 102x102 > nfs: server 192.168.1.50 not responding, still trying > nfs: server 192.168.1.50 not responding, still trying > nfs: server 192.168.1.50 OK > -------------- > > So, there's a lot working correctly, but the graphics display never gets > updated. Am I wrong thinking that the graphics pattern should show up > on the actual display and not just get written to the disk file? Any > other comments, insights, etc would be appreciated. > > Best Regards, you are indeed wrong. the buffer engine - the sample us using it.. renders to memory. thats why it writes out the ppm. it has no display. doesn't need x or even a framebuffer. just renders to memory. if you wanty x.. software-x11 engine is there. fb engine for rendering to a dumb framebuffer etc. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
