dm365中VID0,VID1,osd0/1中的参数详细说明

原创 2012年03月25日 19:15:40

DM365 Boot Argument format for the Frame Buffer Driver is as follows

  • video=[davincifb|dm64xxfb|dm355fb] (keywords 'dm64xxfb' and 'dm355fb' are deprecated, 'davincifb' should be used instead.)
  • vid0=[off|MxNxP,S@X,Y]
  • vid1=[off|MxNxP,S@X,Y]
  • osd0=[MxNxP,S@X,Y]
  • osd1=[MxNxP,S@X,Y]

Where MxN are the horizontal and vertical window size; P is the color depth (bits per pixel), S is the frame buffer size in bytes with suffixes such as ‘K’ or ‘M’ for Kilo (2^10) and Mega (2^20); X, Y are the window position. Only video windows can be turned off. Turning off a video window means that no FB device will be registered for it.

For example:

video=davincifb:vid0=720x480x16,2025K@0,0:vid1=720x480,1350K@0,0:osd0=720x480,1350K@0,0:osd1=720x480,1350K@0,0
720*480*2*2 = 1350k

In the above example, the vid0 is reserved with buffer size 2025K bytes, which is large enough for triple buffering at 720x280x16. The osd0 window is reserved with buffer size 1350K, which is for double buffering for 720x480x16. The FB driver limits video windows to triple buffering and osd windows to double buffering. The total size of the buffer for all display windows shall not exceed 40M bytes. Specific window can be disabled using boot argument option as below:

video=davincifb:vid0=off:vid1=off or video=davincifb:vid0=0,0:vid1=0,0

In this example both the vid0 and vid1 will be disabled at boot time. This will prevent the FBDev driver from creating devices for vid0 and vid1 (/dev/fb/1 and /dev/fb/3). If any of the windows is disabled at boot time, any FBDev driver application is not allowed to perform any IO control operation with that window. However, this will allow other video applications (e.g. V4L2) to access the video windows disabled by FB driver bootargs. OSD windows, however, cannot be disabled by boot arguments. Even if setting up an OSD window as “off” in the bootargs, it will be ignored by FB driver and set it up with default values. When a video window is turned off at boot time, no /dev/fb or /proc/dev entry will be created for it. Alternatively, the following boot arguments can be used to prevent the FBDev driver from claiming video windows, but still reserve the frame buffer space and create FBDev devices. In other words, this will allow V4L2 applications to access vid0 and vid1 windows, yet FBDev devices /dev/fb/1 and /dev/fb/3 will still be created.

video=davincifb:vid0=0,2025K:vid1=0,1350K

After booting up, all FB devices are created as normal, and V4L2 applications are able to claim video windows (through /dev/video/2 or /dev/video/3) to use. When an FBDev application needs to use the device, use ‘fbset’ command to allow FBDev driver to re-claim the video windows (to desired resolution):

$fbset -fb /dev/fb1 -xres 720 -yres 480 -vxres 720 -vyres 1440 -depth 16
$fbset -fb /dev/fb3 -xres 720 -yres 480 -vxres 720 -vyres 1440 -depth 16

A second alternative is, instead of disabling these windows using boot arguments, using ‘fbset’ to release the windows from FBDev driver’s control for other applications to use even if FBDev devices are enabled at boot argument. The following example shows two console commands to “turn off” osd0 and vid0 windows, respectively.

$ fbset -fb /deb/fb0 -xres 0 $ fbset -fb /dev/fb1 -xres 0

When these display windows need to be used by an FBDev application, use ‘fbset’ again to restore the frame buffer device. The following example shows the command of setting vid0 display window to NTSC window size with triple buffering.

$ fbset -fb /dev/fb1 -xres 720 -yres 480 -vxres 720 -vyres 1440

 

Dm365 VPBE 后端模块讲解

Data: 2016.12.22 Author: cjh Theme: DM365 explain of VPBE  研一进来先是接触了TI的dm6437 一款DSP处理器,DaVinc...
  • chenjiehua123456789
  • chenjiehua123456789
  • 2016年12月22日 14:06
  • 898

嵌入式 DM365镜像信号前端ISP

DM365的一个特点是集成了 数字前端ISP(Image Signal Processor,影像信号处理) 。通常,数字摄像机一般包括一个CCD或CMOS传感器,后面还要一个前端视频处理,这部分被称作...
  • skdkjxy
  • skdkjxy
  • 2013年12月02日 14:48
  • 1081

DM365 linux内核&文件系统的烧写步骤及其uboot参数配置

DM365 linux内核&文件系统的烧写步骤及其uboot参数配置     目录 源文档下载:http://download.csdn.net/detail/zhangjikuan/6443...
  • zhangjikuan
  • zhangjikuan
  • 2014年03月25日 19:51
  • 2554

DM365 adc学习笔记

Data: 2015.11.23 Author: cjh Theme: DM365 adc Note 数据手册并没有写明ADC可采集电压的范围,但是整个ADC模块的供电电压是...
  • chenjiehua123456789
  • chenjiehua123456789
  • 2016年12月20日 10:27
  • 298

DM368开发 --IPNC 设置过程

第一步: IPNC 安装:安装软件包,解压后包含以下组件:1. IPNC_RDK_DM36x_Version3.1.0.tar.gz:这是linux tar文件,需要解压在linux机器。这是主要ta...
  • qq_29350001
  • qq_29350001
  • 2017年06月22日 14:35
  • 1104

Qt-4.7.2在dm365下的移植

此篇为我的上一篇博客“Qt-4.7.2及QtEmbedded-4.7.2在ubuntu11.10下的安装”后续,主要参考:博客http://blog.chinaunix.net/uid-256...
  • donganwu
  • donganwu
  • 2013年06月24日 19:28
  • 1038

dm365的LCD显示

原文地址:dm365的LCD显示作者:mick 对DM365的decode做了修改,想让他原来的从小电视输出,改成用LCD输出。 在DM365上面接了一个LCD屏幕。屏幕是800*48...
  • zhangjikuan
  • zhangjikuan
  • 2014年03月11日 20:13
  • 1193

dm365的LCD显示

对DM365的decode做了修改,想让他原来的从小电视输出,改成用LCD输出。 在DM365上面接了一个LCD屏幕。屏幕是800*480,被设置成720*480大小。 从decode出来的数据,应该...
  • micklf
  • micklf
  • 2015年10月31日 11:14
  • 288

DM36x视频前端处理(VPBE)(译)

http://blog.csdn.net/ninver2007/article/details/8048805 1 视频处理前端概要 TMS320DM36X数字多媒体片上系统包括管理视...
  • chenbang110
  • chenbang110
  • 2013年03月27日 20:17
  • 3731

ubuntu开发环境搭建----dm365

////////////////
  • WY1468840047
  • WY1468840047
  • 2017年01月06日 14:48
  • 215
内容举报
返回顶部
收藏助手
不良信息举报
您举报文章:dm365中VID0,VID1,osd0/1中的参数详细说明
举报原因:
原因补充:

(最多只允许输入30个字)