All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Dimitrov <picmaster@mail.bg>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Video overlay on sabresd
Date: Tue, 19 May 2015 19:16:31 +0300	[thread overview]
Message-ID: <555B61DF.2000903@mail.bg> (raw)

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 in advance. Regards,
Nikolay


             reply	other threads:[~2015-05-19 16:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 16:16 Nikolay Dimitrov [this message]
2015-05-19 16:22 ` Video overlay on sabresd Prabhu S
2015-05-20 17:41   ` Nikolay Dimitrov
2015-05-20 23:43     ` Nikolay Dimitrov
2015-05-21  2:01       ` Nikolay Dimitrov
2015-05-22  1:40         ` Nikolay Dimitrov
2015-05-25  7:47           ` Marco Trillo
2015-05-25  9:27             ` Nikolay Dimitrov
2015-05-25 13:22               ` Marco Trillo
2015-05-25 13:52                 ` Nikolay Dimitrov
2015-05-25 14:24           ` Nikolay Dimitrov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=555B61DF.2000903@mail.bg \
    --to=picmaster@mail.bg \
    --cc=meta-freescale@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.