linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Måns Rullgård" <mans@mansr.com>
To: video4linux-list@redhat.com
Cc: linux-omap@vger.kernel.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] OMAP 2/3 V4L2 display driver on video planes
Date: Mon, 06 Oct 2008 09:41:48 +0100	[thread overview]
Message-ID: <yw1x63o6cdyr.fsf@thrashbarg.mansr.com> (raw)
In-Reply-To: 200810060829.25055.hverkuil@xs4all.nl

Hans Verkuil <hverkuil@xs4all.nl> writes:

> On Monday 06 October 2008 08:06:30 Shah, Hardik wrote:
>> 4.  VIDIOC_S/G_OMAP2_COLORKEY:  Color keying allows the pixels with
>> the defined color on the video pipelines to be replaced with the
>> pixels on the graphics pipelines.  I believe similar feature must be
>> available on almost all next generation of video hardware. We can add
>> new ioctl for this feature in V4L2 framework. I think VIDIOC_S_FBUF
>> ioctl is used for setting up the buffer parameters on per buffer
>> basis.  So IMHO this ioctl is not a natural fit for the above
>> functionality. Please provide your comments on same.
>
> Do I understand correctly that if the color in the *video* streams 
> matches the colorkey, then it is replaced by the color in the 
> *framebuffer* (aka menu/overlay)? Usually it is the other way around: 
> if the framebuffer (menu) has chromakey pixels, then those pixels are 
> replaced by pixels from the video stream. That's what the current API 
> does.

The OMAP3 hardware supports both type of keying, but not
simultaneously.

-- 
Måns Rullgård
mans@mansr.com

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  reply	other threads:[~2008-10-06  8:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-17 15:05 [PATCH] OMAP 2/3 V4L2 display driver on video planes Hardik Shah
2008-09-17 15:30 ` Sakari Ailus
2008-09-17 15:42   ` Hiremath, Vaibhav
2008-10-03 14:33 ` Hans Verkuil
2008-10-03 14:40   ` Shah, Hardik
2008-10-05 11:19     ` Mauro Carvalho Chehab
2008-10-05 11:57       ` Robert William Fuller
2008-10-05 12:05         ` Mauro Carvalho Chehab
2008-10-07 21:48         ` [Linux-fbdev-devel] " Krzysztof Helt
2008-10-06  6:06       ` Shah, Hardik
2008-10-06  6:29         ` Hans Verkuil
2008-10-06  8:41           ` Måns Rullgård [this message]
2008-10-06  8:50           ` Shah, Hardik
2008-10-06 11:22             ` [Linux-fbdev-devel] " Geert Uytterhoeven
2008-10-24  9:50           ` Shah, Hardik

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=yw1x63o6cdyr.fsf@thrashbarg.mansr.com \
    --to=mans@mansr.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-omap@vger.kernel.org \
    --cc=video4linux-list@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).