From: Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Tejun Heo <htejun@gmail.com>
Subject: Re: [patch ide-dev 3/9] merge LBA28 and LBA48 Host Protected Area support code
Date: Thu, 24 Feb 2005 17:30:55 +0100 [thread overview]
Message-ID: <200502241730.56015.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <87f94c370502240810583e3a4a@mail.gmail.com>
On Thursday 24 February 2005 17:10, Greg Freemyer wrote:
> I have generic question about HPA, not the patch.
>
> I have noticed with a SUSE 2.6.8 vendor kernel, the HPA behavior is
> not consistent.
Please retry with vanilla kernel.
> ie. With exactly the same computer/controller, but with different disk
> drives (models/manufacturers) the HPA behavior varies.
>
> In all my testing the HPA was always properly detected, but sometimes
> the max_address is set to the native_max_address during bootup and
> sometimes it is not.
Please be more precise.
What do you mean by 'sometimes'?
What are the exact differences between machines?
Are there any differences in software configurations
(i.e. kernel parameters) between this machines?
> Is there some reason for this behavior or is one case or the other a bug?
Dunno, not enough info.
> Does this patch somehow address the inconsistency?
No.
> Am I right in assuming this behavior also exists in the vanilla
> kernels?. ie. I doubt that vendors are patching this behavior.
Recent vanilla kernels always set maximum available capacity.
next prev parent reply other threads:[~2005-02-24 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 14:39 Bartlomiej Zolnierkiewicz
2005-02-24 16:10 ` Greg Freemyer
2005-02-24 16:30 ` Bartlomiej Zolnierkiewicz [this message]
2005-02-24 20:19 ` Greg Freemyer
2005-02-25 21:38 ` Greg Freemyer
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=200502241730.56015.bzolnier@elka.pw.edu.pl \
--to=bzolnier@elka.pw.edu.pl \
--cc=greg.freemyer@gmail.com \
--cc=htejun@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
all inboxes | Powered by JetHome®