linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Kuzminsky <seb@highlab.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: sata_mv important note
Date: Tue, 17 Jan 2006 09:24:26 -0700	[thread overview]
Message-ID: <E1EytdC-0006DE-IS@highlab.com> (raw)
In-Reply-To: <43CD07D5.30302@pobox.com>

Jeff Garzik <jgarzik@pobox.com> wrote:
> For sata_mv users, you should be aware of three things:
> 
> 1) The Marvell driver is experimental, and not yet considered ready for 
> production use.  As Kconfig notes: HIGHLY EXPERIMENTAL.

Right, understood.

Can anyone recommend a 4xSATA (or more) controller on a PCI-X card that
_is_ ready for production use?  eSATA ports are prefered but not required.
Support for hotplug, power management (spindown) and SMART is prefered
but not required.

Anyone?


> Rest assured that all problem reports are read, even if you don't 
> receive a reply.  After enough feedback is received, the exact problem 
> becomes more clear.

Thanks Jeff!


-- 
Sebastian Kuzminsky

  reply	other threads:[~2006-01-17 16:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 15:05 sata_mv important note Jeff Garzik
2006-01-17 16:24 ` Sebastian Kuzminsky [this message]
2006-01-17 19:34   ` Mark Lord
2006-01-18 10:53     ` Erik Slagter
2006-01-18 16:14       ` Jeff Garzik
2006-01-18 19:45         ` Erik Slagter
2006-01-19 17:05           ` Mark Lord
2006-01-19 17:08             ` Randy.Dunlap
2006-01-19 17:11               ` Mark Lord
2006-01-19 17:13                 ` Erik Slagter
2006-01-19 17:09             ` Erik Slagter

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=E1EytdC-0006DE-IS@highlab.com \
    --to=seb@highlab.com \
    --cc=akpm@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).