Hi, It does not have any OSD and attribute window. It has only two Video windows. I don't know which demo you are talking about. Applications like DirectFB only runs on the the FBDEV so they will not run on dm6467. For these kind of applications, you need to write a V4L2 layer, same as the FBDEV layer, to display frames.
Thanks, Brijesh Jadav ________________________________ From: Naveena M. [EMAIL PROTECTED] Sent: Monday, September 29, 2008 8:43 AM To: Jadav, Brijesh R; Phil Quiney; [email protected] Subject: RE: OSD support in DM6467 Hi, Thank you. So what can be done for displays, Like we had in DM6446, video window, OSD window and Attribute window. What should be done to run the demo available with EVM kit? Regards, Naveena ________________________________ From: Jadav, Brijesh R [mailto:[EMAIL PROTECTED] Sent: Monday, September 29, 2008 7:04 PM To: Phil Quiney; Naveena M.; [email protected] Subject: RE: OSD support in DM6467 Hi, As far as i know, dm6467 does not support FBDEV driver. It has only video pipelines so it supports only V4L2 drivers. You will find /dev/video0 to /dev/video3 for the V4L2 devices. Thanks, Brijesh Jadav ________________________________ From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Phil Quiney [EMAIL PROTECTED] Sent: Monday, September 29, 2008 3:54 AM To: Naveena M.; [email protected] Subject: RE: OSD support in DM6467 Hi, Can you check the output of /proc/devices, there should be a 'fb' character device (major 29). This corresponds to the /dev/fb/0 device (maj 29, minor 0) on my system (a DM355). This indicates that the kernel has the framebuffer driver built in. If this does not appear then, it has either been built as a module or not at all. You should also be able to check the kernel configuration has DAVINCI_FB set - extract it from the running kernel to remove any mistakes about how the current kernel is configured.... [EMAIL PROTECTED]:~#<UrlBlockedError.aspx> zcat /proc/config.gz |grep FB CONFIG_FB=y # CONFIG_FB_MODE_HELPERS is not set # CONFIG_FB_TILEBLITTING is not set CONFIG_FB_DAVINCI=y # CONFIG_FB_VIRTUAL is not set Check boot arguments.... Kernel boot arguments (on 1 line so be wary of linewrap) mem=100M console=ttyS0,115200n8 noinitrd root=/dev/nfs rw nfsroot=172.18.0.13:/t ftpboot/remote_fs/davinci_dm355 ip=dhcp video=davincifb:vid0=720x480x16,4050K:vi d1=720x480x16,4050K:osd0=720x480x16,2025K davinci_enc_mngr.ch0_mode=ntsc davinci _enc_mngr.ch0_output=COMPOSITE Also during bootup I get the following framebuffer related items... davincifb davincifb.0: dm_osd0_fb: [EMAIL PROTECTED],0 with framebuffer size 2025KB davincifb davincifb.0: dm_vid0_fb: [EMAIL PROTECTED],0 with framebuffer size 4050KB davincifb davincifb.0: dm_osd1_fb: [EMAIL PROTECTED],0 with framebuffer size 1350KB davincifb davincifb.0: dm_vid1_fb: [EMAIL PROTECTED],0 with framebuffer size 4050KB Confirm 'udev' is running....you should see (during boot up) INIT: version 2.85 booting Mounting a tmpfs over /dev...done. Creating initial device nodes...done. Also 'udevd' should appear in a 'ps aux' once logged in. It is possible that the device node has not been created because udev is not running. Regards Phil Q Phil Quiney, Senior Software Engineer Trinity Convergence Cambridge Business Park Cowley Road Cambridge CB4 0WZ, UK T: +44(0)1223-435536 F: +44(0)1223-435560 www.trinityconvergence.com<http://www.trinityconvergence.com/> ________________________________ From: Naveena M. [mailto:[EMAIL PROTECTED] Sent: 29 September 2008 09:07 To: Phil Quiney; [email protected] Subject: RE: OSD support in DM6467 Hi, There is no device like /dev/fb/0 or /dev/fb/0. We tested the demos available with the DM6446 kit, it was working. It was also dealing with frame buffers. Is it sure that there is frame buffer support in DM6467? Has anybody worked with it? We are trying to do OSD on it. Regards, Naveena. ________________________________ From: Phil Quiney [mailto:[EMAIL PROTECTED] Sent: Monday, September 29, 2008 1:30 PM To: Naveena M.; [email protected] Subject: RE: OSD support in DM6467 Hi, The davinci boards should have /dev/fb/0 rather than /dev/fb/0 - this is true for DM355 & DM6446. I do not have a DM6467 to check against but I would guess it is the same. Regards Phil Q Phil Quiney, Senior Software Engineer Trinity Convergence Cambridge Business Park Cowley Road Cambridge CB4 0WZ, UK T: +44(0)1223-435536 F: +44(0)1223-435560 www.trinityconvergence.com<http://www.trinityconvergence.com/> ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Naveena M. Sent: 29 September 2008 07:24 To: [email protected] Subject: OSD support in DM6467 Hi, We got encode and decode application with DM6467 EVM kit. But the composite video output is not working as we followed the instructions. In the application, we are opening /dev/fb0 (frame buffer) device. But /dev/fbx is not there in the root file system. First we used the uImage in the hard disk. Then we built a new kernel after ensuring framebuffer console, VDCE driver are enabled( by make menucofig). With this kernel also, we didn’t get the frame buffer node. Can anybody tell what may be the issue? And also provide a solution ? or how to proceed? Regards, Naveena
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
