[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201003060736.18555.arvidjaar@mail.ru>
Date: Sat, 6 Mar 2010 07:36:18 +0300
From: Andrey Borzenkov <arvidjaar@...l.ru>
To: linux-hotplug@...r.kernel.org
Cc: Alan Stern <stern@...land.harvard.edu>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Oliver Neukum <oliver@...kum.org>,
"Linux-pm mailing list" <linux-pm@...ts.linux-foundation.org>,
linux-input@...r.kernel.org, USB list <linux-usb@...r.kernel.org>,
Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: Problems with remote-wakeup settings
On Saturday 06 of March 2010 07:16:20 Alan Stern wrote:
> On Fri, 5 Mar 2010, Rafael J. Wysocki wrote:
> > On Friday 05 March 2010, Oliver Neukum wrote:
> > > Am Freitag, 5. März 2010 21:59:31 schrieben Sie:
> > > > > I guess it's better if drivers don't set should_wakeup if
> > > > > unsure, but of course that's impossible to enforce.
> > > >
> > > > That's the real question. Ideally, drivers won't touch
> > > > should_wakeup. How do we get there from here?
> > >
> > > Enable it only for devices specifically designed for wakeup, that
> > > is keyboards, power buttons and WoL, perhaps also mice and
> > > modems. Are we far away from that?
> >
> > I don't think we're very far from that.
> >
> > Mice are known dangerous, especially the USB ones, though.
>
> I agree, especially for desktop systems. You don't want the system
> to wake up merely because you happened to jostle the mouse. That
> happened to me just a few days ago (and it was a PS/2 mouse, not
> USB).
I remember, my old desktop had BIOS option to wake up on mouse click
(and it had PS/2 mouse either) ignoring mouse move. I actually found it
useful.
Download attachment "signature.asc " of type "application/pgp-signature" (199 bytes)
Powered by blists - more mailing lists