From: Henrik Gustafsson <henrik.gustafsson@fnord.se>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Promise SATA driver
Date: Tue, 24 Feb 2004 18:31:00 +0100 [thread overview]
Message-ID: <opr3vxlywuuwbm4s@localhost> (raw)
In-Reply-To: <403B8587.3030009@pobox.com>
On Tue, 24 Feb 2004 12:10:31 -0500, Jeff Garzik <jgarzik@pobox.com> wrote:
> Henrik Gustafsson wrote:
>> On Tue, 24 Feb 2004 11:47:36 -0500, Jeff Garzik <jgarzik@pobox.com>
>> wrote:
>>
>>> Andrew Walrond wrote:
>>>
>>>> I take it the software raid thing wasn't part of the gpl'ed driver,
>>>> and isn't something that is likely to happen?
>>>
>>>
>>>
>>> In 2.4, RAID0 and RAID1 are supported via the pdcraid driver.
>>>
>>> In 2.6, Promise software RAID support does not exist. In
>>> conversations with Promise, we all agreed to encourage and support the
>>> standard Linux RAID, md.
>>>
>>> Jeff
>>
>>
>> Does that apply to the FastTrack S150 SX4 aswell? The hardware
>> XOR-engine will not be used?
>> What about the onboard cache?
>
>
> I'm glad you asked.
>
> The SX4 is a very different story. The hardware XOR engine and on-board
> cache are not currently used, but they will be in the future.
>
> For the TX series, there is no on-board cache, so hardware XOR engine
> isn't very useful. For the SX series, it is very useful.
>
> Promise did some neat stuff with the SX4... so neat it takes some
> thinking to figure out how to best implement it in Linux :)
>
> Jeff
>
I'm glad for that particular response :)
I happen to have such a card in a computer here. Right now it's not used
for anything in particular (waiting for things to stabilising a bit) so
I can test out patches without worrying about any data on it, so feel
free to suggest things to try.
Is there any active development done on it?
My current working conditions (and lack of specs for the card) prevents me
from doing much work on it myself atm, but is there perhaps another way of
following the development on that part a bit more closely?
I have done my (small, but still... :) ) share of driver development and
low-level coding (company I work for makes me write code for their embedded
devices and sometimes drivers for the PC-interfaces) so I might just be
able to pitch in with an idea or two.
// Henrik Gustafsson
next prev parent reply other threads:[~2004-02-24 17:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 11:10 Promise SATA driver Andrew Walrond
2004-02-24 15:21 ` Jeff Garzik
2004-02-24 15:44 ` Pekka Pietikainen
2004-02-24 15:55 ` Jeff Garzik
2004-02-24 16:30 ` Andrew Walrond
2004-02-24 16:47 ` Jeff Garzik
2004-02-24 17:00 ` Henrik Gustafsson
2004-02-24 17:10 ` Jeff Garzik
2004-02-24 17:31 ` Henrik Gustafsson [this message]
2004-02-24 18:15 ` Jeff Garzik
2004-02-24 22:37 ` Miquel van Smoorenburg
[not found] ` <mit.lcs.mail.linux-kernel/403B8028.1060700@pobox.com>
2004-02-26 4:06 ` Patrick J. LoPresti
2004-02-26 4:17 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2003-06-11 9:49 promise " Manuel Sabban
2003-06-11 15:05 ` David van Hoose
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=opr3vxlywuuwbm4s@localhost \
--to=henrik.gustafsson@fnord.se \
--cc=jgarzik@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox