From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Adrian Fiergolski <adrian.fiergolski@fastree3d.com>,
niklas.soderlund+renesas@ragnatech.se,
linux-media@vger.kernel.org, vishal.sagar@xilinx.com
Subject: Re: v4l: status of 'add support for multiplexed streams' patch
Date: Mon, 1 Feb 2021 03:28:06 +0200 [thread overview]
Message-ID: <YBdZJpTfgiipt3IK@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20210129222654.GL32460@paasikivi.fi.intel.com>
Hello,
On Sat, Jan 30, 2021 at 12:26:54AM +0200, Sakari Ailus wrote:
> On Mon, Jan 25, 2021 at 03:08:56PM +0100, Adrian Fiergolski wrote:
> > Dear Niklas,
> >
> > Thank you for your 'v4l: add support for multiplexed streams' patch [1].
> >
> > What is the status of merging your development with v4l-utils? Version
> > 1.16.5 doesn't provide --get/set-routing options. Also in the master of
> > v4l-utils I haven't found your code.
> >
> > What is the current way of changing routing the video switches (e.g.
> > xilinx-axis-swtich which is not yet in the mainstream kernel)?
> >
> > [1] https://lwn.net/Articles/782479/
>
> I seem to have something here:
>
> <URL:https://git.retiisi.eu/?p=~sailus/v4l-utils.git;a=shortlog;h=refs/heads/routing>
>
> It hasn't been tested for some time though. The header update patches need
> to be reworked but the media-ctl + libv4l2subdev patches probably rebase
> just fine.
I've recently rebased the latest version of the patches (exclusing the
changes to the Renesas drivers) that was posted to the linux-media
mailing list, and have pushed the result to
git://linuxtv.org/pinchartl/media.git muxed-streams
This has only been compile-tested so far, and I hope to test it on real
hardware soon.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2021-02-01 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 14:08 v4l: status of 'add support for multiplexed streams' patch Adrian Fiergolski
2021-01-29 22:26 ` Sakari Ailus
2021-02-01 1:28 ` Laurent Pinchart [this message]
2021-02-01 8:57 ` Adrian Fiergolski
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=YBdZJpTfgiipt3IK@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=adrian.fiergolski@fastree3d.com \
--cc=linux-media@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=sakari.ailus@linux.intel.com \
--cc=vishal.sagar@xilinx.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 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.