Re: profiling the resume path

2007-09-03 Thread Marcelo Tosatti
On Mon, Sep 03, 2007 at 12:40:43PM +0100, David Woodhouse wrote: > On Mon, 2007-09-03 at 09:27 +0100, David Woodhouse wrote: > > On Mon, 2007-09-03 at 04:05 -0400, Marcelo Tosatti wrote: > > > > This interrupt scheduled for 233-40ms is what sounds wrong. It should > > > > just continue to blaze of

headtracker / mag lens / macro lens

2007-09-03 Thread linaccess
Hello, am searching for a cheap mag lens to improve the resolution of the headtracker. http://www.olpcaustria.org/mediawiki/index.php/Headtracker What I have found is a very cheap macro lens. I took it from a one-way-camera and put it directly in front of the web cam lens. The difference is obvi

Re: profiling the resume path

2007-09-03 Thread David Woodhouse
On Mon, 2007-09-03 at 09:27 +0100, David Woodhouse wrote: > On Mon, 2007-09-03 at 04:05 -0400, Marcelo Tosatti wrote: > > > This interrupt scheduled for 233-40ms is what sounds wrong. It should > > > just continue to blaze off the EHCI resume path. > > > > ... after 20ms have passed, not almost 20

Re: profiling the resume path

2007-09-03 Thread David Woodhouse
On Mon, 2007-09-03 at 04:05 -0400, Marcelo Tosatti wrote: > > This interrupt scheduled for 233-40ms is what sounds wrong. It should > > just continue to blaze off the EHCI resume path. > > ... after 20ms have passed, not almost 200. Ah, right. Sorry, I missed the order of magnitude discrepancy.

Re: profiling the resume path

2007-09-03 Thread Marcelo Tosatti
On Sun, Sep 02, 2007 at 01:03:12PM -0400, Marcelo Tosatti wrote: > On Sun, Sep 02, 2007 at 12:50:03PM +0100, David Woodhouse wrote: > > On Sun, 2007-09-02 at 04:10 -0400, Marcelo Tosatti wrote: > > > Note: ohci_pci_resume does msleep 20. > > > > Hm. It's just waiting for the hardware to settle, r