public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: avl@logic.at
Cc: Alan <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Allow turning off hpa-checking.
Date: Tue, 28 Nov 2006 21:24:15 +0900	[thread overview]
Message-ID: <456C2A6F.9020406@gmail.com> (raw)
In-Reply-To: <20061128120916.GG2352@gamma.logic.tuwien.ac.at>

Andreas Leitgeb wrote:
[--snip--]
> This theory is backed by my observation of a nearly-broken disk,
> that the quantity "3)" gradually goes down one step after some time.
> The first such step was, when I noticed the problem about half a
> year ago, and just recently it stepped down by another one.

Okay, if that happens on your drive, you gotta burn that foul thing and 
run away as fast/far away as you can.  ;-)

[--snip--]
> The point I'm really trying to make is, that there should be a
> boot option, to disable the query for "1)".  This *must* be a
> boot option, because the querying that I want to be able to
> prevent happens at boot time.
> My broken drive surely doesn't justify the option (or even this
> thread), but the third one of the "uses for 3)" mentioned above
> does. Once the native size is read, I no longer know how many
> sectors were previously "hidden away" by HPA, except by checking
> the kernel-log.
> 
> While Alan has already said, why he thought that this was the
> wrong approach, the reasoning was based on a misunderstanding
> of my question, which I here tried to clear up.

Dunno about IDE layer.  It has been done that way for long time and not 
sure whether adding such option will happen, but for libata, hpa 
handling is still not implemented and it will have to be optional when 
it gets implemented.  So, libata will have such option when it finally 
receives implementation for hpa handling.

-- 
tejun

  reply	other threads:[~2006-11-28 12:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20 14:51 possible bug in ide-disk.c (2.6.18.2 but also older) Andreas Leitgeb
2006-11-20 15:25 ` Alan
2006-11-20 16:56   ` Andreas Leitgeb
2006-11-20 17:28     ` Alan
2006-11-20 17:57       ` Andreas Leitgeb
2006-11-20 18:12         ` Alan
2006-11-21 11:51       ` Andreas Leitgeb
2006-11-21 12:06         ` Alan
2006-11-22 10:57           ` Andreas Leitgeb
2006-11-23 17:05             ` Andreas Leitgeb
2006-11-27 13:09               ` hpa-problem in ide-disk.c - new insights Andreas Leitgeb
2006-11-27 13:30                 ` Alan
2006-11-27 16:01                   ` Allow turning off hpa-checking Andreas Leitgeb
2006-11-27 16:33                     ` Alan
2006-11-27 17:56                       ` Andreas Leitgeb
2006-11-27 18:10                         ` Alan
2006-11-27 18:29                           ` Andreas Leitgeb
2006-11-27 19:59                             ` Alan
2006-11-28  9:29                               ` Andreas Leitgeb
2006-11-28  9:46                                 ` Tejun Heo
2006-11-28 12:09                                   ` Andreas Leitgeb
2006-11-28 12:24                                     ` Tejun Heo [this message]
2006-12-14 14:45                                       ` Andreas Leitgeb

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=456C2A6F.9020406@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=avl@logic.at \
    --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