Message-ID: <3D499862.6070305@evision.ag>
Date: Thu, 01 Aug 2002 22:21:54 +0200
From: Marcin Dalecki <dalecki@evision.ag>
Reply-To: martin@dalecki.de
User-Agent: Mozilla/5.0 (X11; U; Linux i686; pl-PL; rv:1.1b) Gecko/20020722
MIME-Version: 1.0
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
CC: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.29 IDE 110
References: <C917933AE2@vcnet.vc.cvut.cz>
Content-Type: text/plain; charset=US-ASCII;
Content-Transfer-Encoding: 7BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1442
Lines: 31

Uz.ytkownik Petr Vandrovec napisa?:
> On  1 Aug 02 at 2:40, Marcin Dalecki wrote:
> 
>>- Eliminate support for "sector remapping". loop devices can handle
>>    stuff like that. All the custom DOS high system memmory loaded
>>    BIOS workaround tricks are obsolete right now. If anywhere it should
>>    be the FAT filesystem code which should be clever enough to deal with
>>    it by adjusting it's read/write methods.
> 
> 
> Hi Marcin,
>   I'm using this on one system here - it has BIOS without LBA32, and
> without support for >30GB disks, but I needed to put large disk with
> already existing system to it, and using some disk manager was only
> choice (EZDrive, using 0_to_1 remap)... I know that 0_to_1 remap
> is broken for nr_sectors > 1, but it is hard to use loop device if
> system does not come up without boot manager at all.

Maybe not a loop device? But how about handling this at partition scan
time then? Partitions are after all nothing else then devices
with remapped sectors in first place. Could you manage to insert
at the proper place in paritions/*.c the magical + 1.
It could then be turned in no instant in to a global kernel
option - whch it what it is after all.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/