Re: [linux-usb-devel] bmAttribute NO_REMOTE_WAKEUP

2007-03-17 Thread David Brownell
On Saturday 17 March 2007 3:32 pm, Jon Smirl wrote: > > > Two devices I have that also have NO_REMOTE_WAKEUP are both Wifi > > > adapters. Wifi has it's own power saving scheme that allows it to poll > > > for activity without being fully powered. Right, but that still consumes power. And WiFi i

Re: [linux-usb-devel] bmAttribute NO_REMOTE_WAKEUP

2007-03-17 Thread Alan Stern
On Sat, 17 Mar 2007, Jon Smirl wrote: > I was wondering if this was a hint that the wifi devices aren't > supposed to be suspended either. Most wifi devices have an embedded > processor that would need to keep running. Wifi has a mode where it > says: I'm going to shut down for xx ms and then wake

Re: [linux-usb-devel] [PATCH] iforce: Use usb_kill_urb instead of usb_unlink_urb.

2007-03-17 Thread Dmitry Torokhov
Hi Johann, On Saturday 17 March 2007 17:50, johann deneux wrote: > A note about that patch: Apparently Anders Fugmann submitted a patch to use > usb_kill_urb to linux-usb-devel for version 2.6.10. > I don't know if this patch got lost, or if it was rejected. Since every other USB dirver uses usb_

Re: [linux-usb-devel] bmAttribute NO_REMOTE_WAKEUP

2007-03-17 Thread Jon Smirl
On 3/17/07, Alan Stern <[EMAIL PROTECTED]> wrote: > On Sat, 17 Mar 2007, Jon Smirl wrote: > > > I just noticed that the PSC805 USB sound device has NO_REMOTE_WAKEUP > > set it it's configuration bits. Most of my other devices allow > > REMOTE_WAKEUP. > > > > Does this have anything to do with why t

Re: [linux-usb-devel] bmAttribute NO_REMOTE_WAKEUP

2007-03-17 Thread Alan Stern
On Sat, 17 Mar 2007, Jon Smirl wrote: > I just noticed that the PSC805 USB sound device has NO_REMOTE_WAKEUP > set it it's configuration bits. Most of my other devices allow > REMOTE_WAKEUP. > > Does this have anything to do with why the device won't come back from > a suspend? No, or at least,

[linux-usb-devel] bmAttribute NO_REMOTE_WAKEUP

2007-03-17 Thread Jon Smirl
I just noticed that the PSC805 USB sound device has NO_REMOTE_WAKEUP set it it's configuration bits. Most of my other devices allow REMOTE_WAKEUP. Does this have anything to do with why the device won't come back from a suspend? Two devices I have that also have NO_REMOTE_WAKEUP are both Wifi ada

Re: [linux-usb-devel] is gadgetfs driver so hard that no one can answer me?

2007-03-17 Thread Alan Stern
On Sat, 17 Mar 2007, nesta wrote: > hi all, > i m very astonished why isnt there anyone who can answer me about how to use > the gadgetfs i m gonna be made? > i begin to wonder is it very too hard ? > again all what i wanna do is: > make my computer and my kit communicate with each other

[linux-usb-devel] [PATCH] ati_remote2: Add channel support

2007-03-17 Thread Ville Syrjälä
From: Peter Stokes <[EMAIL PROTECTED]> Add logical channel support for ATI Remote Wonder II The ATI Remote Wonder II can be configured with one of 16 unique logical channels. Allowing up to 16 remotes to be used independently within range of each other. This change adds functionality to configu

Re: [linux-usb-devel] [patch 03/05] ti_usb, device setup: without any artificial errors, use configuration changing

2007-03-17 Thread Oleg Verych
Hallo, Al. On Wed, Mar 14, 2007 at 03:32:47AM -0500, Al Borchers wrote: > Oleg -- > > I tried this on 3410 and 5052 with and without firmware--worked > great. > > Please > > 1) Change return value to 1, rather than 0xO1E and 0xA1B. >(Clever, but it will just confuse readers.) > > 2) Drop (

[linux-usb-devel] is gadgetfs driver so hard that no one can answer me?

2007-03-17 Thread nesta
hi all, i m very astonished why isnt there anyone who can answer me about how to use the gadgetfs i m gonna be made? i begin to wonder is it very too hard ? again all what i wanna do is: make my computer and my kit communicate with each other through usb cable? is so hard or impossible thi