mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Szakacsits Szabolcs <szaka@sienet.hu>,
	Andries Brouwer <Andries.Brouwer@cwi.nl>
Cc: "Patrick J. LoPresti" <patl@users.sourceforge.net>,
	bug-parted@gnu.org, Steffen Winterfeldt <snwint@suse.de>,
	Thomas Fehr <fehr@suse.de>,
	linux-kernel@vger.kernel.org, Andrew Clausen <clausen@gnu.org>,
	buytenh@gnu.org, msw@redhat.com
Subject: Re: Restoring HDIO_GETGEO semantics for 2.6 (was: Re: [RFC] Restoring HDIO_GETGEO semantics)
Date: Mon, 5 Jul 2004 15:13:48 +0200	[thread overview]
Message-ID: <200407051513.48334.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <Pine.LNX.4.21.0407041920480.11076-100000@mlf.linux.rulez.org>

On Monday 05 of July 2004 14:14, Szakacsits Szabolcs wrote:

>     - the old HDIO_GETGEO code still exists, just the values are thrown
>       away, as Andries wrote recently

No, the code (ide-geometry.c) is gone.

>     - nobody could point out any _technical_ benefit why the new
> HDIO_GETGEO code is better than the old one (the _way_ Andries wanted to

Andries pointed it many times but you seem to completely ignore it
(see comments in ide-geometry.c):

 * I did this, but it doesn't work - there is no reasonable way to find the
 * correspondence between the BIOS numbering of the disks and the Linux
 * numbering. -aeb
 *
 * The code below is bad. One of the problems is that drives 1 and 2
 * may be SCSI disks (even when IDE disks are present), so that
 * the geometry we read here from BIOS is attributed to the wrong disks.
 * Consequently, also the former "drive->present = 1" below was a mistake.
 *
 * Eventually the entire routine below should be removed.

I also pointed out that IDE driver _doesn't_ need BIOS geometry et all.

> push the code to user space was quite "unlucky")

Yep.

>     - nobody complained if anything would break if HDIO_GETGEO were
> restored
>
>     - returning 0 values have an unpredictable impact. Hence perhaps the
>       change shouldn't be done in the 2.6 kernels to avoid yet another
>       brown paper bag.

Yes, it won't help.

We need new ioctl for a get_start_sect() (first sector of a partition).

> Considering all the above points, it seems logical from practical point
> of view, that the restoration of the old HDIO_GETGEO functionality (or
> something that's very close to its behaviour) _temporarily_ for 2.6
> kernels makes sense.

We can restore ide-geometry.c or try to return values obtained from
EDD code through IDE driver.  Alternatively we can add new ioctl for
start of partition and remove HDIO_GETGEO from IDE driver completely
but probably it is too late for this for 2.6 (we should do it early
in 2.7 then).  Andries?

Bartlomiej


  parent reply	other threads:[~2004-07-05 13:08 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <s5gwu1mwpus.fsf@patl=users.sf.net>
2004-07-02 16:17 ` [RFC] Restoring HDIO_GETGEO semantics (was: Re: workaround for BIOS / CHS stuff) Szakacsits Szabolcs
2004-07-02 16:50   ` Andries Brouwer
2004-07-02 18:28     ` dwm
2004-07-02 21:12       ` parted maintainership Andries Brouwer
2004-07-02 17:04   ` [RFC] Restoring HDIO_GETGEO semantics (was: Re: workaround for BIOS / CHS stuff) Andries Brouwer
2004-07-02 18:12     ` Szakacsits Szabolcs
2004-07-02 18:45       ` Patrick J. LoPresti
     [not found]         ` <Pine.LNX.4.60.0407022025200.28638@hermes-1.csi.cam.ac.uk>
2004-07-02 19:57           ` Patrick J. LoPresti
2004-07-03  0:17             ` Szakacsits Szabolcs
2004-07-03  0:42               ` Bartlomiej Zolnierkiewicz
2004-07-03  0:56                 ` Andries Brouwer
2004-07-03  1:57                   ` Szakacsits Szabolcs
2004-07-03 13:59                   ` Patrick J. LoPresti
2004-07-05 12:14                   ` Restoring HDIO_GETGEO semantics for 2.6 (was: Re: [RFC] Restoring HDIO_GETGEO semantics) Szakacsits Szabolcs
2004-07-05 13:10                     ` Steffen Winterfeldt
2004-07-05 13:12                     ` Andries Brouwer
2004-07-05 13:13                     ` Bartlomiej Zolnierkiewicz [this message]
2004-07-05 14:00                       ` Andries Brouwer
2004-07-05 19:05                         ` Bartlomiej Zolnierkiewicz
2004-07-05 21:08                           ` Andries Brouwer
2004-07-05 21:52                             ` Bartlomiej Zolnierkiewicz
2004-07-06  0:17                               ` Szakacsits Szabolcs
2004-07-06  1:56                                 ` Andries Brouwer
2004-07-06 18:56                                   ` Szakacsits Szabolcs
2004-07-07  1:28                                     ` Andries Brouwer
2004-07-07 11:14                                       ` Roman Zippel
2004-07-07 11:51                                         ` Szakacsits Szabolcs
2004-07-06  8:33                                 ` Steffen Winterfeldt
2004-07-05 18:09                       ` Szakacsits Szabolcs
2004-07-05 18:58                         ` Bartlomiej Zolnierkiewicz
2004-07-03  3:00             ` [RFC] Restoring HDIO_GETGEO semantics (was: Re: workaround for BIOS / CHS stuff) Andrew Clausen
2004-07-02 23:55         ` Szakacsits Szabolcs
2004-07-03 13:56           ` Patrick J. LoPresti
2004-07-03  2:54         ` Andrew Clausen
     [not found]           ` <Pine.LNX.4.60.0407030843400.2415@hermes-1.csi.cam.ac.uk>
2004-07-03 12:44             ` Andrew Clausen
     [not found]               ` <Pine.LNX.4.60.0407031535230.6149@hermes-1.csi.cam.ac.uk>
2004-07-03 15:02                 ` Andrew Clausen
2004-07-03 14:42           ` Patrick J. LoPresti
2004-07-03  1:35   ` Andrew Clausen
2004-07-03 12:33     ` Andries Brouwer
2004-07-03 14:15     ` Patrick J. LoPresti
2004-07-03 14:45       ` Andrew Clausen
2004-07-03 15:00         ` Patrick J. LoPresti
2004-07-03 20:12         ` Andries Brouwer

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=200407051513.48334.bzolnier@elka.pw.edu.pl \
    --to=b.zolnierkiewicz@elka.pw.edu.pl \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=bug-parted@gnu.org \
    --cc=buytenh@gnu.org \
    --cc=clausen@gnu.org \
    --cc=fehr@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msw@redhat.com \
    --cc=patl@users.sourceforge.net \
    --cc=snwint@suse.de \
    --cc=szaka@sienet.hu \
    /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®