From: Pavel Machek <pavel@suse.cz>
To: Oliver Neukum <oliver@neukum.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
David Brownell <david-b@pacbell.net>,
Alan Stern <stern@rowland.harvard.edu>,
Dominik Brugger <ml.dominik83@gmx.net>,
kernel list <linux-kernel@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] Re: OHCI problems with suspend/resume
Date: Fri, 1 Aug 2003 11:33:24 +0200 [thread overview]
Message-ID: <20030801093324.GK2601@openzaurus.ucw.cz> (raw)
In-Reply-To: <200308010112.20514.oliver@neukum.org>
Hi!
> > Is not disk spin-down policy, and thus belonging to userspace? Having
> > daemon poll for inactivity of hubs once every 5 minutes and sending
> > them to sleep should not hurt, too...
> > Pavel
>
> Taking precedents into account it is the kernel's job.
> Screen blanking is done in kernel, as is afaik floppy
> motor control.
Floppy motor was not designed to be "always on", and screen gets physically damaged
if you don't turn it off. OTOH harddrives were designed for always on, and if you spin up/down
too much you shorten their lives...
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
next prev parent reply other threads:[~2003-08-05 22:11 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 22:08 OHCI problems with suspend/resume Pavel Machek
2003-07-24 1:19 ` [linux-usb-devel] " David Brownell
2003-07-24 10:24 ` Pavel Machek
2003-07-24 17:10 ` David Brownell
2003-07-24 22:10 ` Pavel Machek
2003-07-24 12:37 ` Dominik Brugger
2003-07-24 12:56 ` Dominik Brugger
2003-07-24 22:04 ` Pavel Machek
2003-07-24 22:46 ` Pavel Machek
2003-07-25 7:52 ` Dominik Brugger
2003-07-25 15:06 ` [linux-usb-devel] " Alan Stern
2003-07-25 17:20 ` Benjamin Herrenschmidt
2003-07-25 22:48 ` David Brownell
2003-07-26 16:02 ` Alan Stern
2003-07-26 21:01 ` Pavel Machek
2003-07-26 21:16 ` David Brownell
2003-07-27 14:57 ` Alan Stern
2003-07-31 3:27 ` David Brownell
2003-07-31 3:51 ` David Brownell
2003-07-31 9:42 ` Pavel Machek
2003-07-31 13:37 ` David Brownell
2003-07-31 14:09 ` Pavel Machek
2003-07-31 17:32 ` David Brownell
2003-07-31 17:31 ` Pavel Machek
2003-07-31 21:32 ` Benjamin Herrenschmidt
2003-07-31 21:30 ` Benjamin Herrenschmidt
2003-07-31 21:29 ` Benjamin Herrenschmidt
2003-07-31 9:47 ` Pavel Machek
2003-07-31 13:30 ` David Brownell
2003-07-31 16:06 ` Pavel Machek
2003-07-31 9:49 ` Pavel Machek
2003-07-31 13:23 ` David Brownell
2003-07-31 16:07 ` Pavel Machek
2003-07-31 21:25 ` Benjamin Herrenschmidt
2003-07-31 21:25 ` Benjamin Herrenschmidt
2003-07-31 22:08 ` Pavel Machek
2003-07-31 21:23 ` Benjamin Herrenschmidt
2003-07-31 21:55 ` David Brownell
2003-07-31 22:05 ` Benjamin Herrenschmidt
2003-07-31 22:09 ` Pavel Machek
2003-07-31 23:12 ` Oliver Neukum
2003-08-01 9:33 ` Pavel Machek [this message]
2003-07-31 22:03 ` Pavel Machek
2003-08-01 0:27 ` Benjamin Herrenschmidt
2003-08-04 19:25 ` Pavel Machek
2003-08-01 18:20 ` Dominik Brugger
2003-07-29 13:16 ` [linux-usb-devel] " David Brownell
2003-07-31 14:18 ` Pavel Machek
2003-08-01 17:41 ` David Brownell
2003-08-07 22:35 ` Pavel Machek
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=20030801093324.GK2601@openzaurus.ucw.cz \
--to=pavel@suse.cz \
--cc=benh@kernel.crashing.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=ml.dominik83@gmx.net \
--cc=oliver@neukum.org \
--cc=stern@rowland.harvard.edu \
/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.