From: Steve Castellotti <sc@eyemagnet.com>
To: linux-media@vger.kernel.org
Subject: offering bounty for GPL'd dual em28xx support
Date: Tue, 21 Jul 2009 18:09:32 -0700 [thread overview]
Message-ID: <4A6666CC.7020008@eyemagnet.com> (raw)
Hello everyone-
Apologies in advance for spamming the list, but we're after adding
dual device support for the existing, GPL'd em28xx tuner driver
currently in the mainline Linux kernel. We do not have this development
resource in house and had hoped perhaps someone on the list might be
capable and interested (or able to point us in the appropriate direction).
By way of more detail, it seems that multiple times in the past,
other users have also requested this feature, but it is still not
currently available in the current GPL'd driver. For some time support
may have been present in the "em28xx-new" driver, provided by Markus
Rechberger, but I have since been told it is "discontinued, and does not
compile anymore with the latest kernels."
This message thread as recently as April 9th, 2009, seems to
indicate interest is still present at the community level, but no
resolution was reached by the tail of the conversation:
http://www.mail-archive.com/linux-media@vger.kernel.org/msg04245.html
Going further back, it does seem that the em28xx-new driver at one
point successfully addressed this issue, so supporting multiple devices
should be possible with driver modification:
http://mcentral.de/pipermail/em28xx/2008-November/002111.html
We can confirm that a development system running Fedora 11 with the
latest stable kernel (2.6.29.5-191.fc11.i686.PAE), with identical em28xx
devices connected still exhibits the error message "v4l2: ioctl queue
buffer failed: No space left on device" when attempting to display video
input on two identical em28xx devices simultaneously.
On the other hand, display is successful through either device when
trying to display individually (with both still connected).
We are a small company, which relies on the Linux platform for the
core of our products and services. Occasionally a situation presents
itself for us to contribute back to the Open Source community (in
however small a fashion), either by releasing existing code or
contracting a small amount of work to be performed and subsequently
released under the GPL. This is one such instance.
If anyone is interested in contributing such work and is prepared
to quote for what they feel their time would be worth, please do not
hesitate to contact me.
Again, apologies if this message appears to be a misuse of the
mailing list, hopefully our intentions are understandable!
Cheers
--
Steve Castellotti
sc@eyemagnet.com
Technical Director
Eyemagnet Limited
http://www.eyemagnet.com
next reply other threads:[~2009-07-22 1:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 1:09 Steve Castellotti [this message]
2009-07-22 1:42 ` offering bounty for GPL'd dual em28xx support Devin Heitmueller
2009-07-22 2:19 ` Steve Castellotti
2009-07-22 2:32 ` Devin Heitmueller
2009-07-22 3:47 ` Steve Castellotti
2009-07-22 5:42 ` Devin Heitmueller
2009-07-22 5:43 ` Mauro Carvalho Chehab
2009-07-22 16:02 ` Devin Heitmueller
2009-07-22 16:18 ` Mauro Carvalho Chehab
2009-07-22 18:54 ` Steve Castellotti
2009-07-22 18:54 ` Steve Castellotti
2009-07-22 10:10 ` Jelle de Jong
2009-07-22 14:48 ` Mauro Carvalho Chehab
2009-07-22 14:55 ` Markus Rechberger
2009-07-22 14:48 ` Devin Heitmueller
2009-07-22 15:01 ` Jelle de Jong
2009-07-22 15:06 ` Devin Heitmueller
2009-07-22 16:22 ` Mauro Carvalho Chehab
2009-07-30 3:45 ` Mike Isely
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=4A6666CC.7020008@eyemagnet.com \
--to=sc@eyemagnet.com \
--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