From: Xose Vazquez Perez <xose@wanadoo.es>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: syn uw <syn_uw@hotmail.com>,
linux-kernel@vger.kernel.org, marcelo.tosatti@cyclades.com.br,
atulm@lsil.com, linux-megaraid-devel@dell.com
Subject: Re: Megaraid does not work with 2.4.22
Date: Wed, 01 Oct 2003 17:23:47 +0200 [thread overview]
Message-ID: <3F7AF183.5050900@wanadoo.es> (raw)
In-Reply-To: Pine.LNX.4.44.0310011017440.3343-100000@dmt.cyclades
Marcelo Tosatti wrote:
> Having two drivers for the same controller is not a good thing from a user
this doesn't is first time:
e100/eepro100 aic7xxx/aic7xxx_old sym53c8xx_2/sym53c8xx+ncr53c8xx ...
> point of view. I just asked Atul privately but will do so again here: Why
> do we need "megaraid2" ?
megaraid 1.xx gets *very bad* performance. But like 2.4 is stable serie, it
shouldn't be deleted.
megaraid 2.xx gets correct performance, it's stable and it adds support
for _present_ hardware, MegaRAID Ultra320 RAID boards(518, 520, 531, 532).
-thanks-
--
:x
next prev parent reply other threads:[~2003-10-01 15:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 11:01 Megaraid does not work with 2.4.22 syn uw
2003-10-01 13:21 ` Marcelo Tosatti
2003-10-01 15:23 ` Xose Vazquez Perez [this message]
2003-10-01 16:08 ` Marcelo Tosatti
2003-10-07 17:44 ` Xose Vazquez Perez
2003-10-08 0:51 ` Marcelo Tosatti
2003-10-08 1:09 ` Xose Vazquez Perez
2003-10-08 1:49 ` Erik Andersen
2003-10-08 10:27 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2003-10-01 23:33 Tomita, Haruo
2003-10-01 21:40 syn uw
2003-10-01 0:11 Tomita, Haruo
2003-09-30 19:34 Matt_Domsch
2003-09-30 19:21 Xose Vazquez Perez
[not found] <0E3FA95632D6D047BA649F95DAB60E570185F531@exa-atlanta.se.lsil.com>
2003-09-26 9:07 ` Marcelo Tosatti
2003-08-28 11:08 Krzysztof Olędzki
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=3F7AF183.5050900@wanadoo.es \
--to=xose@wanadoo.es \
--cc=atulm@lsil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-megaraid-devel@dell.com \
--cc=marcelo.tosatti@cyclades.com \
--cc=marcelo.tosatti@cyclades.com.br \
--cc=syn_uw@hotmail.com \
/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.