From: Steve Castellotti <sc@eyemagnet.com>
To: linux-media@vger.kernel.org
Subject: Re: offering bounty for GPL'd dual em28xx support
Date: Tue, 21 Jul 2009 19:19:33 -0700 [thread overview]
Message-ID: <4A667735.40002@eyemagnet.com> (raw)
In-Reply-To: <829197380907211842p4c9886a3q96a8b50e58e63cbf@mail.gmail.com>
On 07/21/2009 06:42 PM, Devin Heitmueller wrote:
> On Tue, Jul 21, 2009 at 9:09 PM, Steve Castellotti<sc@eyemagnet.com> wrote:
>> 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).
>>
>
> Hello Steve,
>
> The issue occurs with various different drivers. Basically the issue
> is the device attempts to reserve a certain amount of bandwidth on the
> USB bus for the isoc stream, and in the case of analog video at
> 640x480 this adds up to about 200Mbps. As a result, connecting
> multiple devices can result in exceeding the available bandwidth on
> the USB bus.
>
> Depending on your how many devices you are trying to connect, what
> your target capture resolution is, and whether you can put each device
> on its own USB bus will dictate what solution you can go with.
>
> I've done a considerable amount of work with the mainline em28xx
> driver, so if you would like to discuss your desired configuration
> further and what we might be able to do to accommodate those
> requirements (including possibly optimizing the driver to better
> support more devices), feel free to email me off-list.
>
> Regards,
>
> Devin
>
Devin-
Thanks for the quick response. Happy to take the conversation
off-list, but first, to clarify what may be useful to future web searchers:
So if I'm working with a USB 2.0 bus, which should have a
theoretical maximum of 480 Mbps, if the only two ports connected are
both em28xx capture devices running at (say) 640x480, shouldn't that be
sufficient for displaying both streams simultaneously?
Talking in the general sense of course, perhaps some details vary
from system to system - any idea what sort of variables might affect
that however?
I would assume most systems only have a single USB bus (regardless
of whether plugs are present on the front/back/side). If a given system
has a second USB bus or chipset, them perhaps plugging the second device
into that would solve the problem, but that surely that would be a rare
situation?
Most of the systems we use do not have expansion slots, so adding a
PCI USB board is not possible (in which case we would probably just add
a PCI TV Capture board anyway!).
That said, if you do have some thoughts or suggestions as to how we
might be able to investigate specific hardware, or there is some other
way you think you might be able to help address this particular problem
(ideally in a way that benefits the larger community too!) please let me
know.
Thanks again
Steve
--
Steve Castellotti
sc@eyemagnet.com
Technical Director
Eyemagnet Limited
http://www.eyemagnet.com
next prev parent reply other threads:[~2009-07-22 2:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 1:09 offering bounty for GPL'd dual em28xx support Steve Castellotti
2009-07-22 1:42 ` Devin Heitmueller
2009-07-22 2:19 ` Steve Castellotti [this message]
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=4A667735.40002@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