From: Arjan van de Ven <arjanv@redhat.com>
To: craigl@promise.com, linux-kernel@vger.kernel.org
Subject: Re: [craigl@promise.com: Getting A Patch Into The Kernel] (fwd)
Date: Wed, 13 Jun 2001 10:10:56 +0100 [thread overview]
Message-ID: <3B272E20.79E5472F@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10106122307580.9287-100000@master.linux-ide.org>
Dear Mr. Craig Lyons,
> Hello,
>
> My name is Craig Lyons and I am the marketing manager at Promise Technology.
> We have a question and are hoping you can point us in the right direction.
> In the 2.4 kernel there is support for some of our products (Ultra 66, Ultra
> 100, etc.). As you may or may not know, our Ultra family of controllers
> (which are just standard IDE controllers and do not have RAID) use the same
> ASIC on them as our FastTrak RAID controllers do. The 2.4 kernel will
> recognize our Ultra family of controllers, but there is a problem in that a
> FastTrak will not be recognized as a FastTrak, but as an Ultra.
> Consequently, the array on the FastTrak is not recognized as an array, but
> instead each disk is seen individually, and the users data cannot be
> properly accessed.
This is not correct. Kernel 2.4.5-ac13 and later have a driver to
support the Fasttrak
raid system. I wish Promise was more helpful during the development of
this driver,
as it is currently developed fully independent and without any help /
support or even
acknowledgement of Promise. As a result, not yet all RAID modes and
configurations are
fully supported.
Greetings,
Arjan van de Ven
prev parent reply other threads:[~2001-06-13 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-13 6:22 [craigl@promise.com: Getting A Patch Into The Kernel] (fwd) Andre Hedrick
2001-06-13 6:43 ` bert hubert
2001-06-13 7:06 ` Andre Hedrick
2001-06-13 10:51 ` Rob Landley
2001-06-13 17:57 ` Andre Hedrick
2001-06-13 9:10 ` Arjan van de Ven [this message]
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=3B272E20.79E5472F@redhat.com \
--to=arjanv@redhat.com \
--cc=arjanv@cambridge.redhat.com \
--cc=craigl@promise.com \
--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 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.