public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory Maxwell <greg@linuxpower.cx>
To: Erik van Asselt <e.van.asselt@planet.nl>
Cc: Andre Hedrick <andre@linux-ide.org>,
	"Henning P. Schmiedehausen" <hps@tanstaafl.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Promise RAID controller howto?
Date: Thu, 29 Mar 2001 08:25:50 -0500	[thread overview]
Message-ID: <20010329082550.B4681@xi.linuxpower.cx> (raw)
In-Reply-To: <Pine.LNX.4.10.10103270806300.16125-100000@master.linux-ide.org> <3AC31147.6035E09C@planet.nl>
In-Reply-To: <3AC31147.6035E09C@planet.nl>; from e.van.asselt@planet.nl on Thu, Mar 29, 2001 at 12:41:11PM +0200

On Thu, Mar 29, 2001 at 12:41:11PM +0200, Erik van Asselt wrote:
> Hmmmmm i have the Promise raid source for 2.2 kernel modules so what do you mean
> by opensource signatures
> 
> i have it working for 2.2 kernels but i can't get it to work properly in 2.4
> So if someone want to look at the source !!!
> it can be found on www.promise.com

The promise controller is not a hardware raid board, it is a regular IDE
controller with a bios overlay. Their marketing is deceiving and fraudulent.

Their software raid is less flexible then Linuxes, and it's performance is
inferior. The only advantages of a promise 'raid' controller is cross-OS
compatibility and a simplified booting process.

Promises Linux 'drivers' are proprietary and a violation of the GPL. Because
their drivers are closed source, you can not debug any kernel with it loaded
and you will not be compatible with future upgrades to your kernel without
promises good will.

Because of these reasons, it would be advantageous for Linux to understand
promises boot signature and allow Linuxes built in raid driver to be used on
promises 'raid' disk. Allowing for the cross-os compatibility and easy
booting but retaining the flexible, high performance and open source of the
Linux code.

Unfortunately, promise is more concerned with living their lie then providing
a high quality product to their customers and refuses to provide the tiny
bit of needed information.

      parent reply	other threads:[~2001-03-29 13:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-27 12:36 Promise RAID controller howto? Henning P. Schmiedehausen
2001-03-27 16:32 ` Andre Hedrick
2001-03-29 10:41   ` Erik van Asselt
2001-03-29 10:50     ` Henning P . Schmiedehausen
2001-03-29 13:25     ` Gregory Maxwell [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=20010329082550.B4681@xi.linuxpower.cx \
    --to=greg@linuxpower.cx \
    --cc=andre@linux-ide.org \
    --cc=e.van.asselt@planet.nl \
    --cc=hps@tanstaafl.de \
    --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