http://blog.csdn.net/tju355/article/details/6881389
 
借助于framebuffer,我们能够在console下面作很多事情。首先下载framebuffer的配置工具fbset:
# apt-get install fbset 下载完毕后,配置文件/etc/fb.modes随之产生。

比较简单的作法是用万能的vesafb,如果它被编译进了内核,如:
Device Drivers -> Graphics support ->

  • VESA VGA graphics support
    那么在grub内核引导那一行的后面加上vga=791 它的含义是VESA framebuffer console @ 1024x768x64k,进入系统后可以直接使用framebuffer,看一下这种情况下的各项数据:
    # fbset -s
    mode "1024x768-76"
        # D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz
        geometry 1024 768 1024 768 16
        timings 12714 128 32 16 4 128 4
        rgba 5/11,6/5,5/0,0/0
    endmode

    用具体显卡的framebuffer驱动是另一种选择,拿Nvidia显卡为例,Nvidia显卡的xorg驱动模块与其framebuffer的驱动模块是互相排斥的,如果要用一个就必须清除另一个:
    # rmmod nvidia
    装载nvidia的framebuffer驱动:
    # modprobe nvidiafb
    装载成功的时候,会产生/dev/fb0设备,console屏幕上的字体会有变化。
    看一下当前的配置:
    # fbset -s
    mode "1024x768-85"
        # D: 94.500 MHz, H: 68.677 kHz, V: 84.997 Hz
        geometry 1024 768 1024 32767 8
        timings 10582 208 48 36 1 96 3
        hsync high
        vsync high
        accel true
        rgba 8/0,8/0,8/0,0/0
    endmode

    需要改变一下geometry及色深:
    # fbset -g 1024 768 1024 768 32
    # fbset -s
    mode "1024x768-85"
        # D: 94.500 MHz, H: 68.677 kHz, V: 84.997 Hz
        geometry 1024 768 1024 768 32
        timings 10582 208 48 36 1 96 3
        hsync high
        vsync high
        accel true
        rgba 8/16,8/8,8/0,8/24
    endmode

    我们把它与使用VESA ramebuffer后的数据比较一下,显然,根据具体的显卡来驱动framebuffer可以在颜色上达到最佳值,好,现在我们在console下面能够作的事情:
    一、视频播放,可以用mplayer 或者 fbxine:
    # mplayer -vo fbdev -vf scale=1024:768 video_file.avi
    -vo fbdev 是告诉mplayer用framebuffer作视频驱动.
    -vf scale=1024:768 是全屏的方法,可按屏幕的具体情况作调整
    用fbxine的话需要下载:
    # apt-get install xine-console
    二、图片文件与pdf文件浏览:
    # apt-get install fbi
    用这个软件包里的fbi可以浏览图片,fbgs可以观看pdf文件:
    # fbi -a *jpg
    # fbgs -c *pdf
    三、中文显示:
    # apt-get install jfbterm
    # jfbterm
    中文显示的效果完美。

    文章出处:飞诺网(http://www.diybl.com/course/6_system/linux/Linuxjs/2008721/133651.html)

    ------------------------------------------------------------------------
    在内核Documentation/fb/vesafb.txt文件中,有如下vesa-framebuffer的说明
    Switching modes is done using the vga=... boot parameter. Read
    Documentation/svga.txt for details.
    You should compile in both vgacon (for text mode) and vesafb (for
    graphics mode). Which of them takes over the console depends on
    whenever the specified mode is text or graphics.
    The graphic modes are NOT in the list which you get if you boot with
    vga=ask and hit return. The mode you wish to use is derived from the
    VESA mode number. Here are those VESA mode numbers:
    | 640x480 800x600 1024x768 1280x1024
    ----+-------------------------------------
    256 | 0x101 0x103 0x105 0x107 8位色
    32k | 0x110 0x113 0x116 0x119 15位色
    64k | 0x111 0x114 0x117 0x11A 16位色
    16M | 0x112 0x115 0x118 0x11B 24位色
    The video mode number of the Linux kernel is the VESA mode number plus
    0x200.
    Linux_kernel_mode_number = VESA_mode_number + 0x200
    So the table for the Kernel mode numbers are:
    | 640x480 800x600 1024x768 1280x1024
    ----+-------------------------------------
    256 | 0x301 0x303 0x305 0x307 8位色
    32k | 0x310 0x313 0x316 0x319 15位色
    64k | 0x311 0x314 0x317 0x31A 16位色
    16M | 0x312 0x315 0x318 0x31B 24位色
    To enable one of those modes you have to specify "vga=ask" in the
    lilo.conf file and rerun LILO. Then you can type in the desired
    mode at the "vga=ask" prompt. For example if you like to use 
    1024x768x256 colors you have to say "305" at this prompt.
    If this does not work, this might be because your BIOS does not support
    linear framebuffers or because it does not support this mode at all.
    Even if your board does, it might be the BIOS which does not. VESA BIOS
    Extensions v2.0 are required, 1.2 is NOT sufficient. You will get a
    "bad mode number" message if something goes wrong.
    1. Note: LILO cannot handle hex, for booting directly with 
    "vga=mode-number" you have to transform the numbers to decimal.
    2. Note: Some newer versions of LILO appear to work with those hex values,
    if you set the 0x in front of the numbers.
    本文来自CSDN博客,转载请标明出处:http://blog.csdn.net/songbohr/archive/2010/03/25/5415637.aspx
  • 这两天拾起以前做过的Framebuffer,不相同的是以前在嵌入式上做的,现在在自己电脑上Debian上进行测试,不过都类似罢了,嵌入式里要初始化很多东西。下面具体列一下步骤。至于Framebuffer的原理,就我的理解是比较简单的,无非往mmap好的fb上填写显示数据罢了,不对这些数据进行处理,FrameBuffer 只是一个提供显示内存和显示芯片寄存器从物理内存映射到进程地址空间中的设备,它需要真正的显卡驱动的支持。在这次测试中,我用了默认就安装的vesafb,好像又被称为万能Fb驱动。

    1、   首先在系统Grub启动时按e进入命令启动行的编辑模式,改为:kernel /boot/vmlinuz-2.6.18-5-686 root=/dev/sda6 ro vga=791(vga=791表示fb用1024 * 768 * 16bpp,其他模式的参数可以上网查查);

    2、   进入系统的命令行模式,编译fb测试例子:gcc fb_test.c;

    3、   允许测试例子:sudo ./a.out >> fb.txt(必须要用超级用户权限,>>将屏幕打印写到fb.txt中),效果如下:

    打印如下:

    Fixed screen info:
        id: VESA VGA
        smem_start: 0xf0000000
        smem_len: 3145728
        type: 0
        type_aux: 0
        visual: 2
        xpanstep: 0
        ypanstep: 0
        ywrapstep: 0
        line_length: 2048
        mmio_start: 0x0
        mmio_len: 0
        accel: 0

    Variable screen info:
        xres: 1024
        yres: 768
        xres_virtual: 1024
        yres_virtual: 768
        yoffset: 0
        xoffset: 0
        bits_per_pixel: 16
        grayscale: 0
        red: offset: 11, length: 5, msb_right: 0
        green: offset: 5, length: 6, msb_right: 0
        blue: offset: 0, length: 5, msb_right: 0
        transp: offset: 0, length: 0, msb_right: 0
        nonstd: 0
        activate: 0
        height: -1
        width: -1
        accel_flags: 0x0
        pixclock: 12714
        left_margin: 128
        right_margin: 32
        upper_margin: 16
        lower_margin: 4
        hsync_len: 128
        vsync_len: 4
        sync: 0
        vmode: 0

    Frame Buffer Performance test...
            Average: 2508 usecs
            Bandwidth: 1196.172 MByte/Sec
            Max. FPS: 398.724 fps

    4、还可以通过fb在命令行模式下看视频,如:sudo mplayer –vo fbdev ./air_nessesity.mpg。

    1. #include <stdlib.h>
    2. #include <unistd.h>
    3. #include <stdio.h>
    4. #include <fcntl.h>
    5. #include <linux/fb.h>
    6. #include <linux/kd.h>
    7. #include <sys/mman.h>
    8. #include <sys/ioctl.h>
    9. #include <sys/time.h>
    10. #include <string.h>
    11. #include <errno.h>
    12. struct fb_var_screeninfo vinfo;
    13. struct fb_fix_screeninfo finfo;
    14. char *frameBuffer = 0;
    15. //打印fb驱动中fix结构信息,注:在fb驱动加载后,fix结构不可被修改。
    16. void
    17. printFixedInfo ()
    18. {
    19. printf ("Fixed screen info:\n"
    20. "\tid: %s\n"
    21. "\tsmem_start: 0x%lx\n"
    22. "\tsmem_len: %d\n"
    23. "\ttype: %d\n"
    24. "\ttype_aux: %d\n"
    25. "\tvisual: %d\n"
    26. "\txpanstep: %d\n"
    27. "\typanstep: %d\n"
    28. "\tywrapstep: %d\n"
    29. "\tline_length: %d\n"
    30. "\tmmio_start: 0x%lx\n"
    31. "\tmmio_len: %d\n"
    32. "\taccel: %d\n"
    33. "\n",
    34. finfo.id, finfo.smem_start, finfo.smem_len, finfo.type,
    35. finfo.type_aux, finfo.visual, finfo.xpanstep, finfo.ypanstep,
    36. finfo.ywrapstep, finfo.line_length, finfo.mmio_start,
    37. finfo.mmio_len, finfo.accel);
    38. }
    39. //打印fb驱动中var结构信息,注:fb驱动加载后,var结构可根据实际需要被重置
    40. void
    41. printVariableInfo ()
    42. {
    43. printf ("Variable screen info:\n"
    44. "\txres: %d\n"
    45. "\tyres: %d\n"
    46. "\txres_virtual: %d\n"
    47. "\tyres_virtual: %d\n"
    48. "\tyoffset: %d\n"
    49. "\txoffset: %d\n"
    50. "\tbits_per_pixel: %d\n"
    51. "\tgrayscale: %d\n"
    52. "\tred: offset: %2d, length: %2d, msb_right: %2d\n"
    53. "\tgreen: offset: %2d, length: %2d, msb_right: %2d\n"
    54. "\tblue: offset: %2d, length: %2d, msb_right: %2d\n"
    55. "\ttransp: offset: %2d, length: %2d, msb_right: %2d\n"
    56. "\tnonstd: %d\n"
    57. "\tactivate: %d\n"
    58. "\theight: %d\n"
    59. "\twidth: %d\n"
    60. "\taccel_flags: 0x%x\n"
    61. "\tpixclock: %d\n"
    62. "\tleft_margin: %d\n"
    63. "\tright_margin: %d\n"
    64. "\tupper_margin: %d\n"
    65. "\tlower_margin: %d\n"
    66. "\thsync_len: %d\n"
    67. "\tvsync_len: %d\n"
    68. "\tsync: %d\n"
    69. "\tvmode: %d\n"
    70. "\n",
    71. vinfo.xres, vinfo.yres, vinfo.xres_virtual, vinfo.yres_virtual,
    72. vinfo.xoffset, vinfo.yoffset, vinfo.bits_per_pixel,
    73. vinfo.grayscale, vinfo.red.offset, vinfo.red.length,
    74. vinfo.red.msb_right, vinfo.green.offset, vinfo.green.length,
    75. vinfo.green.msb_right, vinfo.blue.offset, vinfo.blue.length,
    76. vinfo.blue.msb_right, vinfo.transp.offset, vinfo.transp.length,
    77. vinfo.transp.msb_right, vinfo.nonstd, vinfo.activate,
    78. vinfo.height, vinfo.width, vinfo.accel_flags, vinfo.pixclock,
    79. vinfo.left_margin, vinfo.right_margin, vinfo.upper_margin,
    80. vinfo.lower_margin, vinfo.hsync_len, vinfo.vsync_len,
    81. vinfo.sync, vinfo.vmode);
    82. }
    83. //画大小为width*height的同色矩阵,8alpha+8reds+8greens+8blues
    84. void
    85. drawRect_rgb32 (int x0, int y0, int width, int height, int color)
    86. {
    87. const int bytesPerPixel = 4;
    88. const int stride = finfo.line_length / bytesPerPixel;
    89. int *dest = (int *) (frameBuffer)
    90. + (y0 + vinfo.yoffset) * stride + (x0 + vinfo.xoffset);
    91. int x, y;
    92. for (y = 0; y < height; ++y)
    93. {
    94. for (x = 0; x < width; ++x)
    95. {
    96. dest[x] = color;
    97. }
    98. dest += stride;
    99. }
    100. }
    101. //画大小为width*height的同色矩阵,5reds+6greens+5blues
    102. void
    103. drawRect_rgb16 (int x0, int y0, int width, int height, int color)
    104. {
    105. const int bytesPerPixel = 2;
    106. const int stride = finfo.line_length / bytesPerPixel;
    107. const int red = (color & 0xff0000) >> (16 + 3);
    108. const int green = (color & 0xff00) >> (8 + 2);
    109. const int blue = (color & 0xff) >> 3;
    110. const short color16 = blue | (green << 5) | (red << (5 + 6));
    111. short *dest = (short *) (frameBuffer)
    112. + (y0 + vinfo.yoffset) * stride + (x0 + vinfo.xoffset);
    113. int x, y;
    114. for (y = 0; y < height; ++y)
    115. {
    116. for (x = 0; x < width; ++x)
    117. {
    118. dest[x] = color16;
    119. }
    120. dest += stride;
    121. }
    122. }
    123. //画大小为width*height的同色矩阵,5reds+5greens+5blues
    124. void
    125. drawRect_rgb15 (int x0, int y0, int width, int height, int color)
    126. {
    127. const int bytesPerPixel = 2;
    128. const int stride = finfo.line_length / bytesPerPixel;
    129. const int red = (color & 0xff0000) >> (16 + 3);
    130. const int green = (color & 0xff00) >> (8 + 3);
    131. const int blue = (color & 0xff) >> 3;
    132. const short color15 = blue | (green << 5) | (red << (5 + 5)) | 0x8000;
    133. short *dest = (short *) (frameBuffer)
    134. + (y0 + vinfo.yoffset) * stride + (x0 + vinfo.xoffset);
    135. int x, y;
    136. for (y = 0; y < height; ++y)
    137. {
    138. for (x = 0; x < width; ++x)
    139. {
    140. dest[x] = color15;
    141. }
    142. dest += stride;
    143. }
    144. }
    145. void
    146. drawRect (int x0, int y0, int width, int height, int color)
    147. {
    148. switch (vinfo.bits_per_pixel)
    149. {
    150. case 32:
    151. drawRect_rgb32 (x0, y0, width, height, color);
    152. break;
    153. case 16:
    154. drawRect_rgb16 (x0, y0, width, height, color);
    155. break;
    156. case 15:
    157. drawRect_rgb15 (x0, y0, width, height, color);
    158. break;
    159. default:
    160. printf ("Warning: drawRect() not implemented for color depth %i\n",
    161. vinfo.bits_per_pixel);
    162. break;
    163. }
    164. }
    165. #define PERFORMANCE_RUN_COUNT 5
    166. void
    167. performSpeedTest (void *fb, int fbSize)
    168. {
    169. int i, j, run;
    170. struct timeval startTime, endTime;
    171. unsigned long long results[PERFORMANCE_RUN_COUNT];
    172. unsigned long long average;
    173. unsigned int *testImage;
    174. unsigned int randData[17] = {
    175. 0x3A428472, 0x724B84D3, 0x26B898AB, 0x7D980E3C, 0x5345A084,
    176. 0x6779B66B, 0x791EE4B4, 0x6E8EE3CC, 0x63AF504A, 0x18A21B33,
    177. 0x0E26EB73, 0x022F708E, 0x1740F3B0, 0x7E2C699D, 0x0E8A570B,
    178. 0x5F2C22FB, 0x6A742130
    179. };
    180. printf ("Frame Buffer Performance test...\n");
    181. for (run = 0; run < PERFORMANCE_RUN_COUNT; ++run)
    182. {
    183. /* Generate test image with random(ish) data: */
    184. testImage = (unsigned int *) malloc (fbSize);
    185. j = run;
    186. for (i = 0; i < (int) (fbSize / sizeof (int)); ++i)
    187. {
    188. testImage[i] = randData[j];
    189. j++;
    190. if (j >= 17)
    191. j = 0;
    192. }
    193. gettimeofday (&startTime, NULL);
    194. memcpy (fb, testImage, fbSize);
    195. gettimeofday (&endTime, NULL);
    196. long secsDiff = endTime.tv_sec - startTime.tv_sec;
    197. results[run] =
    198. secsDiff * 1000000 + (endTime.tv_usec - startTime.tv_usec);
    199. free (testImage);
    200. }
    201. average = 0;
    202. for (i = 0; i < PERFORMANCE_RUN_COUNT; ++i)
    203. average += results[i];
    204. average = average / PERFORMANCE_RUN_COUNT;
    205. printf (" Average: %llu usecs\n", average);
    206. printf (" Bandwidth: %.03f MByte/Sec\n",
    207. (fbSize / 1048576.0) / ((double) average / 1000000.0));
    208. printf (" Max. FPS: %.03f fps\n\n",
    209. 1000000.0 / (double) average);
    210. /* Clear the framebuffer back to black again: */
    211. memset (fb, 0, fbSize);
    212. }
    213. int
    214. main (int argc, char **argv)
    215. {
    216. const char *devfile = "/dev/fb0";
    217. long int screensize = 0;
    218. int fbFd = 0;
    219. /* Open the file for reading and writing */
    220. fbFd = open (devfile, O_RDWR);
    221. if (fbFd == -1)
    222. {
    223. perror ("Error: cannot open framebuffer device");
    224. exit (1);
    225. }
    226. //获取finfo信息并显示
    227. if (ioctl (fbFd, FBIOGET_FSCREENINFO, &finfo) == -1)
    228. {
    229. perror ("Error reading fixed information");
    230. exit (2);
    231. }
    232. printFixedInfo ();
    233. //获取vinfo信息并显示
    234. if (ioctl (fbFd, FBIOGET_VSCREENINFO, &vinfo) == -1)
    235. {
    236. perror ("Error reading variable information");
    237. exit (3);
    238. }
    239. printVariableInfo ();
    240. /* Figure out the size of the screen in bytes */
    241. screensize = finfo.smem_len;
    242. /* Map the device to memory */
    243. frameBuffer =
    244. (char *) mmap (0, screensize, PROT_READ | PROT_WRITE, MAP_SHARED,
    245. fbFd, 0);
    246. if (frameBuffer == MAP_FAILED)
    247. {
    248. perror ("Error: Failed to map framebuffer device to memory");
    249. exit (4);
    250. }
    251. //测试virt fb的性能
    252. performSpeedTest (frameBuffer, screensize);
    253. printf ("Will draw 3 rectangles on the screen,\n"
    254. "they should be colored red, green and blue (in that order).\n");
    255. drawRect (vinfo.xres / 8, vinfo.yres / 8,
    256. vinfo.xres / 4, vinfo.yres / 4, 0xffff0000);
    257. drawRect (vinfo.xres * 3 / 8, vinfo.yres * 3 / 8,
    258. vinfo.xres / 4, vinfo.yres / 4, 0xff00ff00);
    259. drawRect (vinfo.xres * 5 / 8, vinfo.yres * 5 / 8,
    260. vinfo.xres / 4, vinfo.yres / 4, 0xff0000ff);
    261. sleep (5);
    262. printf (" Done.\n");
    263. munmap (frameBuffer, screensize);    //解除内存映射,与mmap对应
    264. close (fbFd);
    265. return 0;
    266. }

    复制代码

 
0

Framebuffer的配置及应用——先转载留着,以后一定要弄懂的更多相关文章

  1. Python安装、配置图文详解(转载)

    Python安装.配置图文详解 目录: 一. Python简介 二. 安装python 1. 在windows下安装 2. 在Linux下安装 三. 在windows下配置python集成开发环境(I ...

  2. mysql配置和管理(转载)

    MySQL的配置与管理 (2012-08-09 13:06:59) 转载▼ 标签: mysql 配置 管理 分类: MySQL 安装 yum -y install mysql-server   启动服 ...

  3. mac 配置nginx 虚拟域名(转载)

    我是通过homebrew 安装nginx 的,所以安装目录是默认的,之前多个server都是放在默认安装目录下的nginx.conf里的,但是这样不太好,就是会导致nginx.conf 越来越长,而且 ...

  4. maven关于pom文件配置详解(转载)

    转载:http://www.cnblogs.com/hafiz <project xmlns="http://maven.apache.org/POM/4.0.0" xmln ...

  5. Windows下OpenFOAM开发及使用环境配置指南 (2)【转载】

    转载自:http://openfoam.blog.sohu.com/158751915.html *************************************************** ...

  6. Windows下OpenFOAM开发及使用环境配置指南 (1)【转载】

    转载自:http://openfoam.blog.sohu.com/158614863.html *************************************************** ...

  7. spring-security2配置精讲(转载)

    本文转载自牛人downpour的帖子: http://www.iteye.com/topic/319965 Spring 论坛上看了不少Spring Security的相关文章.这些文章基本上都还是基 ...

  8. Spring基础篇——通过Java注解和XML配置装配bean(转载)

      作者:陈本布衣 出处:http://www.cnblogs.com/chenbenbuyi 本文版权归作者和博客园共有,欢迎转载分享,但必须保留此段声明,且在文章页面明显位置给出原文链接,否则保留 ...

  9. eclipse 配置黑色主题(转载)

    转载:http://www.cnblogs.com/csulennon/p/4231405.html 虽然以前也使用eclipse的黑色主题,但是配置起来稍微麻烦一点. 这里先声明,下面的方式适合最新 ...

随机推荐

  1. winform程序中为无边框窗体手动添加窗体拖动代码

            Point oldMousePoint;//记录开始移动窗口前鼠标点下箭头的位置        Point oldFormPoint;//记录开始移动窗口前窗体位置        // ...

  2. CSS学习小记

    搜狗主页页面CSS学习小记 1.边框的处理   要形成上图所示的布局效果,即,点选后,导航下面的边框不显示而其他的边框形成平滑的形状.相对于把导航的下面边框取消然后用空白覆盖掉下面搜索栏的边框比较而言 ...

  3. 趋势:Chrome为打包应用提供强大新特性

    Chrome 7月9日刚为Chrome打包的应用提供了强大的访问Google服务例如Google统计.GoogleAPI和Google 钱包的能力,除此之外,还能够使用系统层面的服务包括蓝牙和原生应用 ...

  4. 横瓜先生关于如何利用MYSQL数据库设计CMS系统处理100亿级TB规模的数据量

    遥执乾坤(44758121)  18:21:23 mysql据说只能使用一个索引,我这里几乎所有字段都有索引. 但每个字段就算用索引,也需要扫描至少100w以上记录. 横瓜(601069289)  1 ...

  5. KendoUI 用下来的小总结

    Kendoui Aspnetmvc * 引用jquery.1.10以上 * 1.项目引用 Kendo.Mvc.dll 2.页面引用 @using Kendo.Mvc.UI; 3.Name和 HtmlA ...

  6. 《微信小程序七日谈》- 第五天:你可能要在登录功能上花费大力气

    <微信小程序七日谈>系列文章: 第一天:人生若只如初见: 第二天:你可能要抛弃原来的响应式开发思维: 第三天:玩转Page组件的生命周期: 第四天:页面路径最多五层?导航可以这么玩: 第五 ...

  7. linux基础命令大全

    编辑器 ed vi/vim (交互式) sed (非交互) vi/vim 的使用 1.命令模式 移动光标 方向键 hjkl H L M G 1G nG 复制行 yy nyy 粘贴 p 删除行 dd n ...

  8. grunt--自动化打包工具使用

    用grunt搭建自动化的web前端开发环境-完整教程 jQuery在使用grunt,bootstrap在使用grunt,百度UEditor在使用grunt,你没有理由不学.不用! 1. 前言 各位we ...

  9. iOS 让UIButton根据文字内容自动计算宽高

    Xcode自带的UIButton控件是没有办法根据文字内容计算自身的宽和高的,下面演示一下问题, 我用代码方式创建一个UIButton,并且设置了一些属性,下面看一下效果图 一切都是这么的美好,跟我们 ...

  10. SHELL中,如何分割字符串

    done.csv中,形如 amoy9812@163.com的数据 #!/bin/shwhile read linedo ar=(${line//@/ }) echo ${ar[0]} #说明:分解出账 ...