public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <p_gortmaker@yahoo.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk,
	andre@linux-ide.org
Subject: Re: [PATCH] clipped disk reports clipped lba size
Date: Fri, 01 Feb 2002 07:10:45 -0500	[thread overview]
Message-ID: <3C5A85C4.55E9FA38@yahoo.com> (raw)
In-Reply-To: <UTC200201302012.UAA81755.aeb@cwi.nl>

Andries.Brouwer@cwi.nl wrote:

> Some disk types fake LBA at 33.8GB, but allow access past this point.
> Some disks actually give I/O errors past the 33.8GB (when jumpered),
> and a SETMAX command is needed to make the rest accessible.
> 
> Two years ago I wrote a tiny utility setmax that does this.
> If I am not mistaken this stuff is now part of the 2.5 kernel.
> No doubt some of it will eventually be backported to 2.4 / 2.2 / 2.0.
> It is in 2.4.18-pre7-ac1.

Alan has said (quite reasonably) that he is not interested in inclusion
of the big IDE patch that exists for 2.2.x -- however, a minimal cut and 
paste backport from 2.4.x IDE to just support HDIO_DRIVE_CMD_AEB (and thus
support setmax) is only about a 100 line diff which I did a while ago.

If there is any interest in this I can check it still applies cleanly to 
current 2.2 pre kernel and send it along for inclusion.

Paul.




  reply	other threads:[~2002-02-01 12:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 20:12 [PATCH] clipped disk reports clipped lba size Andries.Brouwer
2002-02-01 12:10 ` Paul Gortmaker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-02 13:38 Andries.Brouwer
2002-02-01 21:55 Andries.Brouwer
2002-02-02  0:20 ` Andre Hedrick
2002-02-02 11:11 ` Paul Gortmaker
2002-01-30 15:02 Eduardo Trápani
2002-01-30 15:34 ` Alan Cox
2002-01-30 17:04 ` Andre Hedrick

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=3C5A85C4.55E9FA38@yahoo.com \
    --to=p_gortmaker@yahoo.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andre@linux-ide.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