From: Martin Dalecki <dalecki@evision-ventures.com>
To: Arjan van de Ven <arjan@fenrus.demon.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: [PATCH] IDE clean 12 3rd attempt
Date: Sun, 24 Feb 2002 22:05:50 +0100 [thread overview]
Message-ID: <3C7955AE.3070605@evision-ventures.com> (raw)
In-Reply-To: <200202241954.g1OJsPA32151@fenrus.demon.nl> <3C7946D9.1020908@evision-ventures.com> <20020224204513.A32303@fenrus.demon.nl>
Arjan van de Ven wrote:
> On Sun, Feb 24, 2002 at 09:02:33PM +0100, Martin Dalecki wrote:
>
>>>it was about the i386 architecture, not just 80386 cpus. And yes 2.4 still
>>>runs on those; you'be surprised how many
>>>embedded systems run 80386 equivalents...
>>>
>>Interresting. But do they still incorporate ST509 and other
>>archaic controllers? Or do they have broken BIOS-es which don't
>>setup the geometry information properly? I don't think so.
>>
>
> You bet that embedded systems use controllers that emulate archaic ones.
> Oh and bios.... well......
>
>
>>Well now I'm quite convinced. We can point those people to the legacy
>>single host driver anyway... And then the tradeoff goes just in favour
>>of supporting more and more common new hardware - it will just make
>>more people happy than it will make people loose :-).
>>
>
> If you drop hardware support for no good reason.... you scare me. you
> really do. Now dropping hardware support (or moving support
> elsewhere) isn't always avoidable, but I'd think you need a pretty
> good reason to do so.
Yes right. But first please really really think again what ST509 and MFM
controllers are ;-). And after all I have already heard some time
before some real complains from real users around me about the
particular behaviour currently present, which tried to use software raid
on ATA disks. And after all please have a look at the note from Andires
inside the patch, which has been there for a long time now.
Hmm I will perhaps have just to check what distro-backed-kernels do
here... Becouse if my memmory is right, they are removing this
particular function too already...
If you have any objections please *point me* at a particular system
where this would really break things.
next prev parent reply other threads:[~2002-02-24 21:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-24 13:52 [PATCH] Re: [PATCH] IDE clean 12 3rd attempt Andries.Brouwer
2002-02-24 19:47 ` Martin Dalecki
2002-02-24 19:54 ` arjan
2002-02-24 20:02 ` Martin Dalecki
2002-02-24 20:45 ` Arjan van de Ven
2002-02-24 21:05 ` Martin Dalecki [this message]
2002-02-24 21:03 ` Vojtech Pavlik
2002-02-24 19:58 ` [PATCH] IDE clean 13 Martin Dalecki
2002-02-24 21:17 ` Martin Dalecki
2002-02-24 20:02 ` [PATCH] Re: [PATCH] IDE clean 12 3rd attempt Eric Krout
2002-02-24 20:41 ` Alan Cox
2002-02-28 9:44 ` Pavel Machek
2002-02-28 14:19 ` Martin Dalecki
2002-02-28 18:01 ` Jeff Garzik
2002-02-28 18:13 ` Martin Dalecki
2002-02-25 11:45 ` Paul Gortmaker
2002-02-25 12:03 ` Martin Dalecki
-- strict thread matches above, loose matches on Subject: below --
2002-02-25 1:29 Andries.Brouwer
2002-02-25 1:33 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=3C7955AE.3070605@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=arjan@fenrus.demon.nl \
--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