From: Frans Pop <elendil@planet.nl>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] ide: add "ignore_hpa" module parameter
Date: Tue, 26 May 2009 00:27:38 +0200 [thread overview]
Message-ID: <200905260027.39330.elendil@planet.nl> (raw)
In-Reply-To: <200905252344.11826.bzolnier@gmail.com>
Bartlomiej Zolnierkiewicz wrote:
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
[...]
> + ide_core.ignore_hpa=
> + [HW] (E)IDE subsystem
> + Ignore HPA limit
Add a short explanation of what HPA is maybe (or at least expand the
acronym)?
It's also not obvious (at least not to a dumb user like me) that "ignore
HPA limit" is equivalent to "preserving the Host Protected Area" as the
commit commit says.
After reading the wiki page on HPA it looks like the actual meaning is to
"make the HPA visible to the OS"?
> + Format: { "0" | "1" }
> + 0 -- keep BIOS limits
> + 1 -- ignore limits, using full disk (default)
Hmm. This looks weird. Is "BIOS limits" a synonym for "HPA limit"?
Same goes for the MODULE_PARM_DESC.
Cheers,
FJP
next prev parent reply other threads:[~2009-05-25 22:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 21:44 [PATCH 1/3] ide: add "ignore_hpa" module parameter Bartlomiej Zolnierkiewicz
2009-05-25 22:27 ` Frans Pop [this message]
2009-05-25 22:36 ` Alan Cox
2009-05-25 23:06 ` Frans Pop
2009-05-26 12:23 ` Bartlomiej Zolnierkiewicz
2009-05-26 12:53 ` Frans Pop
2009-05-26 13:01 ` Alan Cox
2009-05-26 18:08 ` Andries E. Brouwer
2009-05-27 9:49 ` Alan Cox
2009-05-26 17:32 ` Bartlomiej Zolnierkiewicz
2009-05-26 23:49 ` Robert Hancock
2009-05-26 12:53 ` Alan Cox
2009-05-26 17:15 ` Bartlomiej Zolnierkiewicz
2009-05-27 10:38 ` Alan Cox
2009-05-27 11:41 ` Bartlomiej Zolnierkiewicz
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=200905260027.39330.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox