From: Martin Dalecki <dalecki@evision-ventures.com>
To: Hank Yang <hanky@promise.com.tw>
Cc: arjanv@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Submitting PROMISE IDE Controllers Driver Patch
Date: Fri, 08 Mar 2002 09:12:42 +0100 [thread overview]
Message-ID: <3C88727A.5020108@evision-ventures.com> (raw)
In-Reply-To: <014701c1c5b6$a0dfb620$59cca8c0@hank> <3C873F96.C91E3591@redhat.com> <00b901c1c642$e7b6e9b0$59cca8c0@hank>
Hank Yang wrote:
> Hello.
>
> That's because the linux-kernel misunderstand the raid controller
> to IDE controller. If do so, The raid driver will be unstable when
> be loaded.
>
> So we must to prevent the raio controller to be as IDE controller
> here.
Dear Hank. Please let me elaborate a bit on this, to see whatever
I understand the issues.
The Promise controlled is NOT a true self hosted RAID controller.
It is just a bunch of ATA host chips, which a software add on
in some ROM exposed as BIOS to Win32 systems, making it possible
for them to view multiple configurations of the disks as once single
nice RAID.
However under linux we have the nice ataraid.c driver, which is
allowing one to use whichever ATA disks one wan't on whichever
channels as RAID. The overhead of running the RAID functionality code
from true nice RAMBUS RAM, in comparision to stincking flash RAM
on some PCI card behind two bridges is in fact negative ;-).
It doesn't therefore make any sense for a linux user to use
the PDC as something elese then a bunch of host chennel chips.
Or what are your concerns?
next prev parent reply other threads:[~2002-03-08 8:14 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-07 9:01 [PATCH] Submitting PROMISE IDE Controllers Driver Patch Hank Yang
2002-03-07 10:23 ` Arjan van de Ven
2002-03-08 1:45 ` Hank Yang
2002-03-08 2:10 ` Alan Cox
2002-03-08 3:01 ` Hank Yang
2002-03-08 8:19 ` Martin Dalecki
2002-03-08 8:23 ` arjan
2002-03-08 8:35 ` Martin Dalecki
2002-03-08 8:50 ` Arjan van de Ven
2002-03-08 9:14 ` Martin Dalecki
2002-03-08 13:12 ` Alan Cox
2002-03-08 19:25 ` Kelsey Hudson
2002-03-09 13:25 ` Martin Dalecki
2002-03-08 13:25 ` Alan Cox
2002-03-13 7:35 ` Hank Yang
2002-03-13 7:45 ` Arjan van de Ven
2002-03-08 2:54 ` Kelsey Hudson
2002-03-08 7:54 ` Arjan van de Ven
2002-03-08 8:12 ` Martin Dalecki [this message]
2002-03-07 13:15 ` Alan Cox
2002-03-08 3:49 ` Hank Yang
2002-03-08 13:14 ` Alan Cox
2002-03-13 6:52 ` Hank Yang
2002-03-13 16:39 ` Alan Cox
2002-05-22 9:38 ` Hank Yang
[not found] ` <039701c20892$3940ca30$c0cca8c0@promise.com.tw>
2002-05-31 14:33 ` [PATCH] Submitting PROMISE IDE " Alan Cox
2002-06-03 3:51 ` [PATCH] 2.4.19pre9 in pdc202xx.c bug Hank Yang
2002-06-03 15:48 ` Alan Cox
2002-06-06 2:31 ` Hank Yang
2002-06-06 12:17 ` Alan Cox
[not found] ` <3C876199.5000107@evision-ventures.com>
2002-03-08 2:00 ` [PATCH] Submitting PROMISE IDE Controllers Driver Patch Hank Yang
-- strict thread matches above, loose matches on Subject: below --
2002-03-10 14:23 Ed Tomlinson
2002-03-10 14:47 ` Alan Cox
2002-03-11 9:56 ` benh
[not found] <200203071331.g27DVi211087@sunrise.pg.gda.pl>
2002-03-07 13:36 ` Andrzej Krzysztofowicz
2002-03-07 6:46 Hank Yang
2002-03-09 21:23 ` Pavel Machek
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=3C88727A.5020108@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=arjanv@redhat.com \
--cc=hanky@promise.com.tw \
--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