Re: Advice on extending libv4l for media controller support

[Laurent Pinchart <laurent.pinchart@ideasonboard.com>]

Hi Hans,

On Thursday 10 May 2012 16:20:42 Hans de Goede wrote:
> Hi,
> 
> I somehow missed the original mail. This is in essence the same problem
> as with the omap3 and Laurent and Sakari and I did a design for that
> in Brussels in the last quarter of 2011, Laurent and Sakari would work
> on fleshing that out, so it is probably best to talk to them about this.

Let's get Sakari into the loop then. I think he's the most knowledgeable about 
this, even though no implementation has been released (Nokia killing MeeGo 
obviously didn't help).

> On 05/10/2012 03:54 PM, Sergio Aguirre wrote:
> > +Atsuo
> > 
> > On Wed, May 9, 2012 at 7:08 PM, Sergio Aguirre wrote:
> >> Hi Hans,
> >> 
> >> I'm interested in using libv4l along with my omap4 camera project to
> >> adapt it more easily to Android CameraHAL, and other applications, to
> >> reduce complexity of them mostly...
> >> 
> >> So, but the difference is that, this is a media controller device I'm
> >> trying to add support for, in which I want to create some sort of plugin
> >> with specific media controller configurations, to avoid userspace to
> >> worry about component names and specific usecases (use sensor resizer, or
> >> SoC ISP resizer, etc.).
> >> 
> >> So, I just wanted to know your advice on some things before I start
> >> hacking your library:
> >> 
> >> 1. Should it be the right thing to add a new subfolder under "lib/",
> >> named like "libomap4iss-mediactl" or something like that ?
> >> 2. Do you know if anyone is working on something similar for any other
> >> Media Controller device ?
> >> 
> >> Thanks in advance for your inputs.
> >> 
> >> Regards,
> >> Sergio

-- 
Regards,

Laurent Pinchart