From: Bill Davidsen <davidsen@tmr.com>
To: gene.heskett@verizon.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: OT: Why is usb data many times the cpu hog that firewire is?
Date: Wed, 23 Feb 2005 18:28:41 -0500 [thread overview]
Message-ID: <421D11A9.1090708@tmr.com> (raw)
In-Reply-To: <200502211216.35194.gene.heskett@verizon.net>
Gene Heskett wrote:
> Greetings;
>
> Motherboard is a biostar with nforce2 chipset, 2800xp cpu, gig of ram.
>
> I've recently made the observation that while I can view 30fps video
> from my firewire equipt movie camera with a minimal cpu hit of 2-3%,
> but viewing the video from a webcam on a usb 1.1 circuit takes 30-40%
> of the cpu, at half the frame rate.
You have gotten most of an answer, unless someone make a fireware to
USB2 adaptor you are going to have to go slow or run firewire.
I would think the framerate could be quite slow and still be useful.
What software do you use to do the detection (curiousity only)? Of
course after you detect motion you probably want to up the framerate, so
you can see what's really happening.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-02-23 23:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 17:16 OT: Why is usb data many times the cpu hog that firewire is? Gene Heskett
2005-02-21 17:58 ` Oliver Neukum
2005-02-21 18:25 ` Gene Heskett
2005-02-21 18:29 ` Wichert Akkerman
2005-02-21 22:08 ` Gene Heskett
2005-02-22 23:10 ` Matt Mackall
2005-02-23 13:13 ` Paulo Marques
2005-02-23 17:15 ` Geert Uytterhoeven
2005-02-21 18:40 ` Paulo Marques
2005-02-21 18:46 ` Oliver Neukum
2005-02-24 11:52 ` David Ford
2005-02-22 8:53 ` Barry K. Nathan
2005-02-22 13:12 ` Gene Heskett
2005-02-23 23:28 ` Bill Davidsen [this message]
2005-02-24 23:50 ` H. Peter Anvin
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=421D11A9.1090708@tmr.com \
--to=davidsen@tmr.com \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@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