From: Arjan van de Ven <arjanv@redhat.com>
To: Chris Abbey <linux@cabbey.net>, linux-kernel@vger.kernel.org
Subject: Re: PDC20268 TX2 support?
Date: Sat, 20 Apr 2002 18:43:25 +0100 [thread overview]
Message-ID: <3CC1A8BD.2899AB80@redhat.com> (raw)
In-Reply-To: <E16yqWt-0000QP-00@the-village.bc.nu> <Pine.LNX.4.33.0204201226530.25636-100000@tweedle.cabbey.net>
Chris Abbey wrote:
>
> Today, Alan Cox wrote:
> > > the 2.4.19 timeframe. I'm curious what level of support folks are
> > > expecting? Just basic IDE, or support for the hardware raid features?
> >
> > What hardware raid features ?
>
> The FastTraK 100 TX2 has hardware raid (stripe/mirror) support, they
> have a binary only driver (scsi/ft.o) which presents this array as
> a scsi device... this is the level of function I was hoping was being
> integrated.
that is not hardware raid but software raid.
>
> > AFAIK their only cards with hardware raid features are the supertrak 100 and
> > SX6000.
>
> The current 2.4.18 code recognizes the card and provides vanilla IDE
> access to the drives, unfortunately that isn't much use unless someone
> wants to try and RE their block allocation on the disks... a decidedly
> non-trivial endeavour I can assure you. ;(
It seems you missed the ATARAID stuff in the ide config..
next prev parent reply other threads:[~2002-04-20 17:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 6:06 PDC20268 TX2 support? Chris Abbey
2002-04-20 6:56 ` Andre Hedrick
2002-04-20 8:47 ` Alan Cox
2002-04-20 17:33 ` Chris Abbey
2002-04-20 17:43 ` Arjan van de Ven [this message]
2002-04-20 17:56 ` Chris Abbey
2002-04-23 9:58 ` Alan Cox
2002-04-23 13:34 ` Nicolae P. Costescu
[not found] <Pine.LNX.4.33.0204201253250.21092-100000@coffee.psychology.mcmaster.ca>
2002-04-20 17:37 ` Chris Abbey
[not found] <Pine.LNX.4.33.0204201226530.25636-100000@tweedle.cabbey.ne t>
2002-04-21 4:18 ` Nicolae P. Costescu
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=3CC1A8BD.2899AB80@redhat.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@cabbey.net \
/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