From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 35550E00A0A; Mon, 25 May 2015 06:53:58 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [193.201.172.118 listed in list.dnswl.org] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (picmaster[at]mail.bg) * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mx2.mail.bg (mx2.mail.bg [193.201.172.118]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id BF081E009B8 for ; Mon, 25 May 2015 06:52:57 -0700 (PDT) Received: from [192.168.0.62] (unknown [93.152.143.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx2.mail.bg (Postfix) with ESMTPSA id 10A626001593; Mon, 25 May 2015 16:52:56 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1432561976; bh=kxzNcJTiNQnX0YmWIkUjdtF3kHOO3Ja7Qp3ZArsFVs0=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=nUbrD9osWlrQeKUxvkqvvx2zqHOpk5rBELIOgzH3Zvb4U70mKq7IJrpwT9VGt7Vn2 Kw2kBJ6jIU9Ia8GNrMAlYIS/MAlCd6rAgaIIxIJGyHBp3APZM+xvGvW7xkf8ivoxew TiIbyfa3QLWohdoFovwfLdaeiG9Lae395VJtwBTM= Message-ID: <55632937.8080502@mail.bg> Date: Mon, 25 May 2015 16:52:55 +0300 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: Marco Trillo References: <555B61DF.2000903@mail.bg> <555CC752.6060706@mail.bg> <555D1C21.6020402@mail.bg> <555D3C7D.7020406@mail.bg> <555E892B.1010904@mail.bg> <5562D379.4010503@arantia.com> <5562EAEB.7080200@mail.bg> <55632227.9000400@arantia.com> In-Reply-To: <55632227.9000400@arantia.com> Cc: "meta-freescale@yoctoproject.org" Subject: Re: Video overlay on sabresd X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2015 13:53:58 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Hi Marco, On 05/25/2015 04:22 PM, Marco Trillo wrote: > Hi, > > On 05/25/2015 11:27 AM, Nikolay Dimitrov wrote: >> Exactly. Regarding the MXCFB_SET_OVERLAY_POS - I was thinking this >> ioctl is related to X/Y position of the layer and not about the layers' >> Z-order (at least this is the impression I have looking at the mxcfb >> driver and imx lib code). Please correct me if I'm wrong, but I thing >> the Z-order of the BG/FG IPU layers is not programmable. > > Issuing the MXCFB_SET_GBL_ALPHA or MXCFB_SET_LOC_ALPHA ioctls() at > /dev/fb0 should cause the `fb0' layer to display atop the `fb1' or video > layer, mixed according to the global or per-pixel alpha value. This is > what the docs say (which is a bit confusing): > > 3.2.2 DP global alpha combination > To enable DP global alpha combination feature, we need to use fb ioctl > MXCFB_SET_LOC_ALPHA [sic]. [...] By default, /dev/fb0 stands for the > background frame buffer and /dev/fb2 stands for the foreground frame > buffer [...] If the open file descriptor of /dev/fb0 is passed to this > ioctl, the graphics plane of DP is set to the background plane, > otherwise, the graphics plane is set to the foreground plane. > (from Freescale's "Image Processing Unit V3 (IPUV3) Library User's Guide") > > After configuring the DP via these ioctls, you can then use the > MXCFB_SET_CLR_KEY if you need to use color keying. Well, my experiments are showing somewhat different behavior: setting alpha on fb0 causes color key not to work on fb1. Alpha needs to be explicitly set to the FG layer (fb1) in order color key to work. Regards, Nikolay