From: Jelle de Jong <jelledejong@powercraft.nl>
To: "linux-media@vger.kernel.org >> \"linux-media@vger.kernel.org\""
<linux-media@vger.kernel.org>
Subject: Re: offering bounty for GPL'd dual em28xx support
Date: Wed, 22 Jul 2009 12:10:38 +0200 [thread overview]
Message-ID: <4A66E59E.9040502@powercraft.nl> (raw)
In-Reply-To: <829197380907211842p4c9886a3q96a8b50e58e63cbf@mail.gmail.com>
Devin Heitmueller wrote:
<snip>
> 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.
Hi all,
So I felt like doing a field test, with my dvb-t test system.
Bus 001 Device 008: ID 2040:6502 Hauppauge WinTV HVR-900
Bus 001 Device 007: ID 2304:0226 Pinnacle Systems, Inc. [hex] PCTV 330e
Bus 001 Device 005: ID 0b05:173f ASUSTek Computer, Inc.
Bus 001 Device 003: ID 2304:0236 Pinnacle Systems, Inc. [hex]
Bus 001 Device 002: ID 15a4:9016
I have now three devices with dvb-t channels running with different
channels and audio on an atom based cpu without problems.
two:
dvb-usb-dib0700
and one:
dvb-usb-af9015
the dvb-usb-af9015 takes way more cpu interrupts because of the usb
block size.
prove:
http://imagebin.ca/img/xM9Q7_A.jpg
I will be demonstrating this at har2009 (see demonstration village)
Devin could you login onto the dvb-t test system and see if you can get
those em28xx device running with your new code?
I will probably make an other test system with some more cpu power to
see if even more usb devices are possible, or I may use my nice powerful
multiseat quad core system for it.
Best regards,
Jelle de Jong
next prev parent reply other threads:[~2009-07-22 10:10 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
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 [this message]
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=4A66E59E.9040502@powercraft.nl \
--to=jelledejong@powercraft.nl \
--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