From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 0C18FE009B6; Wed, 20 May 2015 19:01:59 -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 BE386E009EF for ; Wed, 20 May 2015 19:01:34 -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 44A276000D39; Thu, 21 May 2015 05:01:33 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1432173693; bh=qw7U/XW+zAMSMFcVD1O6tgEnSbzQZd4RIBekBHl/dMg=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=asCgCn8r5tgBIn5kEeU/xgkWUWRKSTT+rSvXRwEImhGWPV9dz6TUsqdb/Nbv897ob 2N1OHhOUHjdKa9mP/rNDd95Qv6HsWgPKjOwz0JKWlUK0OrngFD41Q3L9N2gy5RcQqS B8gRJ3DHb/Yj2OWXqsb/7jhFWGFoWFkdcnWW89XY= Message-ID: <555D3C7D.7020406@mail.bg> Date: Thu, 21 May 2015 05:01:33 +0300 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: "meta-freescale@yoctoproject.org" References: <555B61DF.2000903@mail.bg> <555CC752.6060706@mail.bg> <555D1C21.6020402@mail.bg> In-Reply-To: <555D1C21.6020402@mail.bg> 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: Thu, 21 May 2015 02:01:59 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Hi all, On 05/21/2015 02:43 AM, Nikolay Dimitrov wrote: > Hi all, > > On 05/20/2015 08:41 PM, Nikolay Dimitrov wrote: >> Hi Prabhu, >> >> On 05/19/2015 07:22 PM, Prabhu S wrote: >>> How about this? >>> /unit_tests/mxc_v4l2_output.out -iw 1024 -ih 768 -ow 1024 -oh 768 -d >>> /dev/video17 -fr 30 -l 10 -f YUYV ./your-file.yuyv >>> >>> /dev/video17 is for overlay >>> >>> On Tue, May 19, 2015 at 11:16 AM, Nikolay Dimitrov >> > wrote: >>> >>> Hi guys, >>> >>> I'm trying to get the video overlay working on imx6q sabresd's HDMI. >>> Here's the kernel command line: >>> >>> console=ttymxc0,115200 root=/dev/mmcblk2p2 rootwait rw >>> video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB2 >>> 4,bpp=32 fbmem=28M >>> >>> This is the kernel version: >>> >>> # uname -a >>> Linux imx6qsabresd 3.14.28-1.0.0_ga+g91cf351 #1 SMP PREEMPT Tue May >>> 19 17:32:51 EEST 2015 armv7l >>> GNU/Linux >>> >>> Here are the framebuffer devices nodes: >>> >>> # ls -lh /dev/fb* >>> crw-rw---- 1 root video 29, 0 Jan 1 1970 /dev/fb0 >>> crw-rw---- 1 root video 29, 1 Jan 1 1970 /dev/fb1 >>> crw-rw---- 1 root video 29, 2 Jan 1 1970 /dev/fb2 >>> crw-rw---- 1 root video 29, 3 Jan 1 1970 /dev/fb3 >>> >>> I can write arbitrary data on /dev/fb0 and see it on screen, like >>> this: >>> >>> # cat /bin/busybox.nosuid > /dev/fb0 >>> >>> But I can't write to /dev/fb1: >>> >>> # cat /bin/busybox.nosuid > /dev/fb1 >>> cat: write error: No space left on device >>> >>> I'm assuming that fb0 is the background layer, and fb1 is the >>> foreground IPU layer. >>> >>> So the question is - how to make the foreground (fb1) layer >>> working at >>> all? Should I configure mxcfb1 in the bootargs, or it needs some >>> IOCTL >>> in /dev/fb1 to enable the device? >> >> Thanks for sharing. This works, but I'm trying to achieve exactly the >> opposite. >> >> I need to have my UI on the FG layer (which imho means X rendering to >> /dev/fb1), and my video player must render on BG layer (/dev/video16, >> which imho corresponds to /dev/fb0). >> >> At the moment I can't seem to be able to draw anything on /dev/fb1, so >> I doubt that Xorg will also run properly on it. > > I've reordered the video interfaces in the DT, and also in the kernel > cmdline, to make sure the hdmi is the first and only video interface, > so hopefully the IPU driver will create both BG and FG channels for it. > > Unfortunately I still can't write to /dev/fb1, so I'm digging further. Prabhu's comment hinted me to start looking around /unit_tests and if/how they work. It turned out that the mxc_fb_test application worked somewhat and I was able observe alpha-blending between FG & BG layers. Then, after some more head-banging, the issue where I couldn't write to the framebuffer was resolved by this: echo 0 > /sys/class/graphics/fb1/blank Much nicer! Now I can go and test how Xorg works on /dev/fb1, but it's probably a better idea to get some sleep before this... Regards, Nikolay