From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Rob Clark <rob@ti.com>
Cc: linux-fbdev@vger.kernel.org,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Idea of a v4l -> fb interface driver
Date: Fri, 28 May 2010 10:07:58 +0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1005280851000.32352@axis700.grange> (raw)
In-Reply-To: <4BFED8B0.8010504@ti.com>
(re-adding lists to CC)
On Thu, 27 May 2010, Rob Clark wrote:
> Hi Guennadi,
>
> Sounds like an interesting idea... but how about the inverse? A v4l2
> interface on top of fbdev. If v4l2 was more widely available as an output
> device, perhaps more userspace software would utilize it.
Don't see any advantage in doing this apart from "attracting user-space
developers to develop for v4l2 output interface," which doesn't seem like
a worthy goal in itself. Whereas with my translation you get access to
existing user-space applications and to a powerful in-kernel API, and
achieve a better interoperability with video-input streams.
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
next prev parent reply other threads:[~2010-05-28 10:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 14:09 Idea of a v4l -> fb interface driver Guennadi Liakhovetski
2010-05-27 0:21 ` Jaya Kumar
2010-05-27 6:56 ` Guennadi Liakhovetski
2010-05-27 11:05 ` Jaya Kumar
2010-05-27 12:48 ` Guennadi Liakhovetski
2010-05-27 19:55 ` Alex Deucher
2010-05-28 8:21 ` Guennadi Liakhovetski
2010-05-28 17:47 ` Alex Deucher
2010-05-28 19:15 ` Florian Tobias Schandinat
2010-05-28 19:25 ` Guennadi Liakhovetski
2010-05-28 19:58 ` Florian Tobias Schandinat
2010-05-28 19:41 ` Alex Deucher
2010-05-28 20:06 ` Ville Syrjälä
2010-05-30 11:15 ` Dave Airlie
[not found] ` <4BFED8B0.8010504@ti.com>
2010-05-28 10:07 ` Guennadi Liakhovetski [this message]
2010-05-27 6:56 ` Hiremath, Vaibhav
2010-05-27 7:35 ` Guennadi Liakhovetski
2010-05-27 19:00 ` Udo Richter
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=Pine.LNX.4.64.1005280851000.32352@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=rob@ti.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