Hi!
> > > > You should have /proc/acpi/battery/*/state ; it shows current power
> > > > consumption.
> > >
> > > Yes, that works. Cool :-)
> >
> > Good... so how much power is it saving for you?
>
> Nothing USB:
> present rate:1874 mA
>
> Mouse in use:
> present rate:20
Hi1
> > Measurements on x60:
>
> What strange architectures is that?
It is thinkpad x60. i386 architecture.
> > Feb 1 15:58:14 amd kernel: Added idle timer for firing in 10 seconds
> > ^[ Feb 1 15:58:24 amd kernel: state is 0
> > Feb 1 15:58:24 amd kernel: Modded idle timer for firing in 10
Am Donnerstag, 1. Februar 2007 15:43 schrieb Pavel Machek:
> Hi!
>
> > > You should have /proc/acpi/battery/*/state ; it shows current power
> > > consumption.
> >
> > Yes, that works. Cool :-)
>
> Good... so how much power is it saving for you?
>
Am Donnerstag, 1. Februar 2007 16:03 schrieb Pavel Machek:
> Measurements on x60:
What strange architectures is that?
[..]
> When I actually use the mouse
>
> Feb 1 15:58:14 amd kernel: Added idle timer for firing in 10 seconds
> ^[ Feb 1 15:58:24 amd kernel: state is 0
> Feb 1 15:58:24 amd
Hi!
>
> this preliminary patch should suspend your mouse, if it supports remote
> wakeup. In fact it should do this to all devices which are HID, claimed by
> the input layer and support remote wakeup.
>
> It works for me with my mouse. I've tested letting it autosuspend and
> resume. It survives
Hi!
> > You should have /proc/acpi/battery/*/state ; it shows current power
> > consumption.
>
> Yes, that works. Cool :-)
Good... so how much power is it saving for you?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(
02/01/2007 11:22 AM, Oliver Neukum wrote/a écrit:
> Am Donnerstag, 1. Februar 2007 11:09 schrieb Eric Piel:
>
>> Hi,
>>
>> I can report success for my mouse automatically turning off (and waking
>> up when I click). However I wonder how good it is in a pure user
>> interface view: suddenly the m
Am Donnerstag, 1. Februar 2007 11:09 schrieb Eric Piel:
> Hi,
>
> I can report success for my mouse automatically turning off (and waking
> up when I click). However I wonder how good it is in a pure user
> interface view: suddenly the mouse turns off. That needs to be more
> configurable and
01/31/2007 04:56 PM, Oliver Neukum wrote/a écrit:
> Hi,
>
> this preliminary patch should suspend your mouse, if it supports remote
> wakeup. In fact it should do this to all devices which are HID, claimed by
> the input layer and support remote wakeup.
>
> It works for me with my mouse. I've tes
Am Mittwoch, 31. Januar 2007 17:44 schrieb Pavel Machek:
> You should have /proc/acpi/battery/*/state ; it shows current power
> consumption.
Yes, that works. Cool :-)
Regards
Oliver
-
Take Surveys. E
Am Mittwoch, 31. Januar 2007 17:55 schrieb Jiri Kosina:
> A first example that comes to mind - suppose that you have two keyboards,
> at least one of them being HID. Now when the timer expires, the HID
> keyboard will be suspended. Then when you hit a capslock/numlock/...
> (basically anything c
On Wed, 31 Jan 2007, Oliver Neukum wrote:
> In fact it should do this to all devices which are HID, claimed by the
> input layer and support remote wakeup.
>From a quick look, in addition to Alan's comments, it seems to me that you
don't handle a case in which the hid driver decides to send an
Hi!
> this preliminary patch should suspend your mouse, if it supports remote
> wakeup. In fact it should do this to all devices which are HID, claimed by
> the input layer and support remote wakeup.
>
> It works for me with my mouse. I've tested letting it autosuspend and
> resume. It survives g
Hi,
this preliminary patch should suspend your mouse, if it supports remote
wakeup. In fact it should do this to all devices which are HID, claimed by
the input layer and support remote wakeup.
It works for me with my mouse. I've tested letting it autosuspend and
resume. It survives going to a te
14 matches
Mail list logo
