public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wichert Akkerman <wichert@wiggy.net>
To: Gene Heskett <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: Mon, 21 Feb 2005 19:29:52 +0100	[thread overview]
Message-ID: <20050221182952.GF6722@wiggy.net> (raw)
In-Reply-To: <200502211325.55013.gene.heskett@verizon.net>

Previously Gene Heskett wrote:
> Thats what I was afraid of, which makes using it for a motion detected 
> burgular alarm source considerably less than practical since the 
> machine must be able to do other things too.

Dependin on the type of compression used you might be able to detect
motion by analyzing the compressed datastream.

Wichert.

-- 
Wichert Akkerman <wichert@wiggy.net>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.

  reply	other threads:[~2005-02-21 18:29 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 [this message]
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
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=20050221182952.GF6722@wiggy.net \
    --to=wichert@wiggy.net \
    --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