All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Pavel Machek <pavel@ucw.cz>,
	sean@mess.org, hverkuil-cisco@xs4all.nl,
	mchehab+samsung@kernel.org, sakari.ailus@linux.intel.com,
	linux-media@vger.kernel.org
Subject: Re: [PATCH] Minimal libv4l2 support for complex cameras
Date: Mon, 23 Mar 2020 13:59:33 +0100	[thread overview]
Message-ID: <20200323135933.6ddbe4c3@coco.lan> (raw)
In-Reply-To: <20200323122442.GD12103@pendragon.ideasonboard.com>

Em Mon, 23 Mar 2020 14:24:42 +0200
Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:

> Hi Pavel,
> 
> On Mon, Mar 23, 2020 at 01:22:17PM +0100, Pavel Machek wrote:
> > > On Mon, Mar 23, 2020 at 12:47:27PM +0100, Pavel Machek wrote:
> > >> Hi!
> > >> 
> > >> We now have easy-to-install support for complex camera in form of
> > >> Maemo Leste on N900.... Unfortunately we don't have anything in
> > >> userspace that can be used to work with the camera.
> > >> 
> > >> This attempts to be minimal solution to get libv4l2 to work.
> > > 
> > > libv4l2 is mostly deprecated.

Well, not really... I guess lots of userspace apps rely on it
(qv4l2, xawtv, tvtime, camorama, zbar, ...).

In order to be able to deprecate it, we need to add some code there
to let them bind via libcamera and test them with different hardware,
including the non-UVC ones.

> > > How about contributing an OMAP3 ISP
> > > pipeline handler to libcamera instead ? :-)
> > 
> > Why should it be instead?
> > 
> > I need something for kernel testing, and there is ton of apps using
> > it. Let me do this. libcamera might be future, but...
> 
> Sure, if it's useful for you, I won't prevent you from developing any
> code you want :-) But there's very little chance of getting it merged,
> and it would be useful to more people to have a support for that
> platform in libcamera. It's really your decision, and I'm not blaming
> you.

I created some time ago a fork of v4l-utils in order to be able to
merge the N900 work from Pavel. We can add the N900 work there - or 
on a separate branch at the main v4l-utils tree.

Thanks,
Mauro

  reply	other threads:[~2020-03-23 12:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23 11:47 [PATCH] Minimal libv4l2 support for complex cameras Pavel Machek
2020-03-23 11:57 ` Laurent Pinchart
2020-03-23 12:22   ` Pavel Machek
2020-03-23 12:24     ` Laurent Pinchart
2020-03-23 12:59       ` Mauro Carvalho Chehab [this message]
2020-03-23 13:43         ` Laurent Pinchart
2020-03-23 13:19       ` Pavel Machek
2020-03-23 13:52         ` Laurent Pinchart
2020-04-14  9:11           ` Hans Verkuil

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=20200323135933.6ddbe4c3@coco.lan \
    --to=mchehab@kernel.org \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=pavel@ucw.cz \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sean@mess.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.