Linux Media Controller development
 help / color / mirror / Atom feed
From: "forum::für::umläute" <zmoelnig@umlaeute.mur.at>
To: linux-media@vger.kernel.org
Subject: Re: v4l2loopback and kernel-3.7
Date: Thu, 24 Jan 2013 17:36:33 +0100	[thread overview]
Message-ID: <51016311.6030202@umlaeute.mur.at> (raw)
In-Reply-To: <51015A68.50808@umlaeute.mur.at>

On 2013-01-24 16:59, forum::für::umläute wrote:
> hi all,

just in case: please CC me, as i'm not subscribed to this list (yet).

gfadmsr
IOhannes

> 
> i'm currently maintainer of the "v4l2loopback" device [1], a virtual
> video device that allows applications to share video-streams via the
> v4l2 API (each device being V4L2_CAP_VIDEO_CAPTURE | V4L2_CAP_VIDEO_OUTPUT).
> 
> now (unfortunately for someone maintaining a driver) i have not been
> following development of the linux-kernel very closely (mainly using
> debian unstable kernels myself), but some of my users do.
> it seems that with newer kernel-versions the functionality for
> video-output modules have been somehow removed from the kernel (3.7.1
> has been confirmed to make troubles, whereas 3.6.10 still works).
> 
> i'd like to inquire, what happened in/to the mainstream kernel, and
> what's the supposed way to proceed for a virtual video device like mine.
> (i naively ask the question here, as i'm a bit afraid of kernel-dev
> mailing list :-))
> 
> what's more, if the v4l2-taskforce would be interested to take over a
> kernel-module that - to my knowledge - is currently the only feasible
> way on linux to exchange live video streams between applications, we
> might talk about that :-)
> 
> fgasdmr
> IOhannes
> 
> 
> 
> 
> [1] https://github.com/umlaeute/v4l2loopback/


  reply	other threads:[~2013-01-24 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24 15:59 v4l2loopback and kernel-3.7 forum::für::umläute
2013-01-24 16:36 ` forum::für::umläute [this message]
2013-01-24 16:47 ` 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=51016311.6030202@umlaeute.mur.at \
    --to=zmoelnig@umlaeute.mur.at \
    --cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox