From: Zack Smith <plinius@comcast.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Adding overlays
Date: Thu, 10 Feb 2005 11:23:32 -0800 [thread overview]
Message-ID: <420BB4B4.9060804@comcast.net> (raw)
In-Reply-To: <20050210145634.34525.qmail@web53606.mail.yahoo.com>
Which display controller is this that you're speaking of?
Komal Shah wrote:
> Hi All,
>
> I am a newbie into this overlay stuff. Let me explain
> my confusion first:
>
> 1. I have a display controller hardware which support
> "primary buffer window", "video1 window", "video2
> window". video2 on top of -> video 1 on top of ->
> primary.
>
> Now primay buffer window is used by /dev/fb for normal
> framebuffer support.
>
> 2. Now I want to utilize overlay support given by
> "video1 and 2", to have two playbacks/previews.
>
> What should I do/use the interface to get this overlay
> support given my video1 and video2 windows?? Ofcourse
> I need to get around by setting lots of hardware
> specific values...
>
> 1. Should I modify the frambuffer driver and adding
> new ioctl to implement this overlay.
>
> 2. Should I implement separate character device driver
> and "mmap", "write" on the same?? e.g /dev/overlay1
> /dev/overlay2 .
>
> So that a user application can give/write YUV 422 to
> the driver and overlay will handle its conversion to
> RGB 565 and display on the LCD in my case.
>
> 3. Should I implement /dev/video0 interace?? Here I am
> confused a much, because I am already having capture
> device - camera driver(v4l2), which implements the
> overlay stuff for previewing while capture. Means it
> supports the overlay and capture but *no* playback.
>
> Any pointers or drivers source code which will help me
> to device strategy and the get the implementation
> done. I am having working framebuffer and camera
> driver.
>
> Let me know if you want more information.
>
> Thanx.
>
> =====
> ---Komal Shah
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - now with 250MB free storage. Learn more.
> http://info.mail.yahoo.com/mail_250
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Linux-fbdev-devel mailing list
> Linux-fbdev-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
>
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-10 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 14:56 Adding overlays Komal Shah
2005-02-10 19:23 ` Zack Smith [this message]
2005-02-11 5:08 ` Komal Shah
2005-02-11 15:50 ` Zack Smith
2005-02-11 13:14 ` Komal Shah
2005-02-11 5:32 ` Ville Syrjälä
2005-02-11 6:36 ` Komal Shah
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=420BB4B4.9060804@comcast.net \
--to=plinius@comcast.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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.