All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Dalecki <dalecki@evision.ag>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: Andries Brouwer <aebr@win.tue.nl>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@transmeta.com>,
	martin@dalecki.de
Subject: Re: [PATCH] 2.5.30 IDE 112
Date: Tue, 06 Aug 2002 14:23:00 +0200	[thread overview]
Message-ID: <3D4FBFA4.3030809@evision.ag> (raw)
In-Reply-To: 13C83160220@vcnet.vc.cvut.cz

Uz.ytkownik Petr Vandrovec napisa?:
> On  6 Aug 02 at 12:27, Andries Brouwer wrote:
> 
>>On Tue, Aug 06, 2002 at 10:50:42AM +0200, Marcin Dalecki wrote:
>>
>>>- Just removaing dead obscure xlate_1024 code.
>>
>>Command line options must be added to ask for what this
>>xlate_1024 code did earlier. So, some fragments of what you remove
>>in this patch will have to come back in some form.
> 
> 
> FYI I had to use hda=cyls,255,63 to repartition my HDD. BIOS refused
> to report proper size (120GB) when partition table was empty, or when
> it contained partitions created for xxx/16/63 geometry. It reported
> size ~600MB, and actively refused to allow access above this limit...
> 
> With removed (either completely, or just disabling as it is now) xlate_1024 
> code please talk to [cs]fdisk maintainer (and other) to print big fat
> warning and to allow specify BIOS heads/sectors, otherwise partitioning
> of empty disk in the way compatible with non-Linux OSes (Netware, Windows)
> is not an easy task.

Sidenote 1. - they can do the recalculation done by xlate_1024 themself 
of  course.

Sidenote 2. - Linux is thinking xxx/16/63 is the best way to deal with 
big disks. Phenix BIOS docu says xxxx/255/63 is the way to go.



  reply	other threads:[~2002-08-06 12:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-06 12:19 [PATCH] 2.5.30 IDE 112 Petr Vandrovec
2002-08-06 12:23 ` Marcin Dalecki [this message]
2002-08-06 18:17   ` Andre Hedrick
2002-08-06 14:10 ` Andries Brouwer
  -- strict thread matches above, loose matches on Subject: below --
2002-08-06 16:06 Petr Vandrovec
2002-08-06  8:50 Marcin Dalecki
2002-08-06 10:27 ` Andries Brouwer
2002-08-06 19:22 ` Linus Torvalds

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=3D4FBFA4.3030809@evision.ag \
    --to=dalecki@evision.ag \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=aebr@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@dalecki.de \
    --cc=torvalds@transmeta.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.