public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark <mark@harddata.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Serial ATA (SATA) status report
Date: Fri, 27 Feb 2004 11:56:08 -0700	[thread overview]
Message-ID: <200402271156.08829.mark@harddata.com> (raw)
In-Reply-To: <200402261423.56448.m.watts@eris.qinetiq.com>

On February 26, 2004 07:23 am, Mark Watts wrote:
> > Mark Watts wrote:
> > > Which one of these chips are the 3Ware cards based on?
> >
> > None of them. 3ware has its own chip, supported by the 3w-xxxx driver in
> > mainline 2.4 and 2.6. It's basicly exports the logical arrays as SCSI
> > devices.
>
> Neat. Are there any known issues with these cards? (Do they work with
> AMD-64?)

We have build Raid boxes with 3ware on x86_64. We have not had to run a 32bit 
OS to get it working and it works fine. There were some issues with more than 
4GB of memory but I believe 3ware has resolved them now.

-- 
Mark Lane, CET mailto:mark@harddata.com 
Hard Data Ltd. http://www.harddata.com 
T: 01-780-456-9771   F: 01-780-456-9772
11060 - 166 Avenue Edmonton, AB, Canada, T5X 1Y3
--> Ask me about our Excellent 1U Systems! <--

  parent reply	other threads:[~2004-02-27 19:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-26  2:34 Serial ATA (SATA) status report Jeff Garzik
2004-02-26  2:54 ` Mike Fedyk
2004-02-26  3:09   ` Jeff Garzik
2004-02-26  9:13 ` Mark Watts
2004-02-26 13:19   ` Andre Tomt
2004-02-26 14:23     ` Mark Watts
2004-02-26 15:33       ` Terje Kvernes
2004-02-26 15:55         ` Mark Watts
2004-02-26 20:11           ` Terje Kvernes
2004-02-27 18:56       ` Mark [this message]
2004-02-26 16:00   ` Jeff Garzik
2004-02-28 14:49 ` Justin Cormack
2004-03-01  8:05   ` Michael Knigge
  -- strict thread matches above, loose matches on Subject: below --
2004-02-26  6:28 Kyle Wong
2004-02-26 19:08 Adam Radford

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=200402271156.08829.mark@harddata.com \
    --to=mark@harddata.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