All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+challenge-response@blue-labs.org>
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: Thu, 24 Feb 2005 06:52:20 -0500	[thread overview]
Message-ID: <421DBFF4.50301@blue-labs.org> (raw)
In-Reply-To: <200502211325.55013.gene.heskett@verizon.net>

use a minimum resolution until you detect motion then switch to high 
resolution.


  parent reply	other threads:[~2005-02-24 11:50 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 [this message]
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=421DBFF4.50301@blue-labs.org \
    --to=david+challenge-response@blue-labs.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.