From: Marcin Dalecki <dalecki@evision.ag>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.29 IDE 110
Date: Thu, 01 Aug 2002 22:21:54 +0200 [thread overview]
Message-ID: <3D499862.6070305@evision.ag> (raw)
In-Reply-To: C917933AE2@vcnet.vc.cvut.cz
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.
next prev parent reply other threads:[~2002-08-01 20:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 16:54 [PATCH] 2.5.29 IDE 110 Petr Vandrovec
2002-08-01 20:21 ` Marcin Dalecki [this message]
2002-08-01 21:47 ` Alan Cox
2002-08-01 21:16 ` Marcin Dalecki
-- strict thread matches above, loose matches on Subject: below --
2002-08-01 21:45 Petr Vandrovec
2002-08-01 21:57 ` Marcin Dalecki
2002-08-01 17:37 Adam J. Richter
2002-08-01 0:40 Marcin Dalecki
2002-08-01 18:51 ` Albert D. Cahalan
2002-08-01 20:13 ` Marcin Dalecki
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=3D499862.6070305@evision.ag \
--to=dalecki@evision.ag \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
/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