This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

How different is Video-Pipeline from the GFX-Pipeline

Hi

I have been able to display a splash screen in u-boot, (jpg image converted to a Header (*h)) on the screen.

Using GFX pipeline, now I trying to overlay 2 images, so I'm playing around with the VID1-pipeline
but I'm not able to get anything on the screen.

How different is is the configuration ? 
Can the VID-pipelines handles simple images like the GFX pipeline ? 

Please help me out with this..

  • Hi Bhargav,

    (1) The features, that GFX pipeline has in advance are the 'support for color look-up table (CLUT): 256 × 24-bit entries palette in RGB' , and the support for antiflicker on 'RGB pixel formats using 3-tap filter'. Regarding to them, there's additional registers for configuring - DISPC_GFX_TABLE_BA ( TRM, section 10.2.7.3 )

    (2) Of course, VID1 pipeline is able to handle sample images.(check the TRM).

    About the issue you get - All of the pipelines are disabled by DSS core during boot time (see drivers/video/omap2/dss/core.c.), and may be thats the reason you didn't get any of the content assigned to VID1 pipeline... however, you would need to configure DISPC_VID1_BA_0 register to use a valid physical address as the base pointer for the framebuffer pixel data. During the u-boot stage only the framebuffer can be used as a source of the content, so you are able to display only the data, thats there. i.e the logo.h header file with "static char * header_data" that contains your desired splash screen bitmap. Just merge the two images you want to be displayed, and use the approach with GFX pipeline:

    user2011 1989 said:
    I have been able to display a splash screen in u-boot, (jpg image converted to a Header (*h)) on the screen.



  • Thank you very much for the reply..

    I found the problem, It was with the "Self Refresh" bit field, I had enabled this by some calculation error.
    I also made the following observation:

    Self Refresh should not be used as we fetch data from the memory, not DMA buffers.
    When Z order: 0 display was garbled. when I set it to 1 it worked fine.

    Please give me ur suggestions on the same. 

  • Hi,

    Regarding to the bit field description: Z-Order defining the priority of the layer compared to
    others when overlaying, i.e. this configures the layers arrangement by it's priority (defined in ZORDER).

    For example if GFX pipeline has ZORDER attribute set to 0x0, and on other side VID1 ZORDER set to 0x1, it's layer should be above the GFX one. ( OF course VID1 ZORDERENABLE should be set to 0x1, in order to have Z-ordering, otherwise ZORDER of the layer is 0 )