From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] hdparm.mod - get/set ATA disk parameters
Date: Sat, 21 Feb 2009 20:51:42 +0100 [thread overview]
Message-ID: <20090221195142.GB18492@thorin> (raw)
In-Reply-To: <49A04126.3080008@t-online.de>
On Sat, Feb 21, 2009 at 07:00:06PM +0100, Christian Franke wrote:
>>
>> Very interesting. Do you think any of these features could be useful as a
>> default option in grub-mkconfig?
>>
>>
>
> At least the --health check and --security-freeze are IMO recommended
> for each disk. Both is also done by a typical PC BIOS. AAM and standby
> settings are more user specific. The problem is that this relies on
> native ATA support which is now only available for controllers supported
> by ata.mod.
>
> At least for the boot disk, such hdparm calls could be added by e.g.
> extending 'prepare_grub_to_access_device'.
But if the firmware already did, wouldn't this be a waste of boot time?
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-02-21 19:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 22:59 [PATCH] hdparm.mod - get/set ATA disk parameters Christian Franke
2009-02-07 21:38 ` Robert Millan
2009-02-07 22:46 ` Christian Franke
2009-02-07 22:59 ` Robert Millan
2009-02-07 23:12 ` Christian Franke
2009-02-08 0:32 ` Robert Millan
2009-02-09 19:42 ` Christian Franke
2009-02-12 22:21 ` Christian Franke
2009-02-14 14:13 ` Christian Franke
2009-02-21 13:05 ` Robert Millan
2009-02-21 18:00 ` Christian Franke
2009-02-21 19:51 ` Robert Millan [this message]
2009-02-21 20:38 ` Christian Franke
2009-02-21 20:46 ` Robert Millan
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=20090221195142.GB18492@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
/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.