Bug 62136

Summary: [staging intel-driver] Using i965_image_processing to convert NV12 to RGB produce corrupted RGB image.
Product: libva Reporter: Ung, Teng En <teng.en.ung>
Component: intelAssignee: ykzhao <yakui.zhao>
Status: RESOLVED FIXED QA Contact: Sean V Kelley <seanvk>
Severity: normal    
Priority: medium CC: haihao.xiang
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Some code change to take the fastscale flag and use i965_image_processing to convert NV12 to RGM into swap buffer.
Change the pitch of the RGB format.

Description Ung, Teng En 2013-03-11 02:59:26 UTC
Created attachment 76302 [details]
Some code change to take the fastscale flag and use i965_image_processing to convert NV12 to RGM into swap buffer.

Hi,

    I need some image format conversion features to test difference performance.  Anyway, with staging-20130205 on both libva and intel-va-driver.  I modified some code to use the i965_image_processing to convert NV12 to RGB but the output is corrupted.

    Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 08)
    OS : Fedora 18
    Kernel : 3.7.4-204.fc18.i686
    libva : staging-20130205
    intel-va-driver : staging-20130205 with some patch to enable NV12 to RGB with i965_image_processing.
    vaapi-mplayer : latest
    screen info : 1920x1200@60

    With the attached patch apply to intel-va-driver.  Now when calling "./mplayer -vo vaapi:scaling=fast -va vaapi <video clip>" it will go to the path that use i965_image_processing to convert the NV12 to RGB into swap buffer and display it.  Anyway, the image is corrupted.

    Using the normal command are fine, "mplayer -vo vaapi -vaapi <video>".
Comment 1 Ung, Teng En 2013-03-11 03:03:28 UTC
Created attachment 76303 [details]
Change the pitch of the RGB format.

By applying this patch (correct the RGB pitch), the output image show up, but the whole image are reddish.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.