From: Jeff Garzik <jgarzik@pobox.com>
To: Denis Leroy <denis@poolshark.org>
Cc: Mark Lord <liml@rtr.ca>,
sander@humilis.net, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
lkml@rtr.ca
Subject: Re: Some sata_mv error messages
Date: Tue, 21 Mar 2006 14:37:13 -0500 [thread overview]
Message-ID: <442055E9.4010708@pobox.com> (raw)
In-Reply-To: <44205513.8030109@poolshark.org>
Denis Leroy wrote:
> This is great news. Is there any relationship between the development of
> this driver and the one maintained by Marvell that's available from
> their web site ? Their latest version (3.6.1) is released under the GPL,
> and is a very solid driver based our experience with it over the past
> few years, though it's targeted at older versions of the linux kernel
> and needs some porting to 2.6.16 (and contains redundant stuff like its
> own scsi-ata layer).
There is a we-use-that-driver-as-documentation-sometimes relationship.
It's quite un-Linux for a Linux driver, and others have reported that
sata_mv in its current state is more stable for them than the Marvell
behemoth GPL driver.
Jeff
next prev parent reply other threads:[~2006-03-21 19:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060318044056.350a2931.akpm@osdl.org>
2006-03-18 15:10 ` sata_mv success on 2.6.16-rc6-mm2 (was: Re: 2.6.16-rc6-mm2) Sander
2006-03-18 19:57 ` Andrew Morton
2006-03-20 13:33 ` Some sata_mv error messages " Sander
2006-03-21 1:02 ` Some sata_mv error messages Jeff Garzik
2006-03-21 2:25 ` Dave Jones
2006-03-21 2:35 ` Jeff Garzik
2006-03-21 16:06 ` Peter Jones
2006-03-21 4:48 ` Mark Lord
2006-03-21 7:28 ` Sander
2006-03-21 19:33 ` Denis Leroy
2006-03-21 19:37 ` Jeff Garzik [this message]
2006-03-21 19:42 ` Mark Lord
2006-03-21 7:26 ` Sander
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=442055E9.4010708@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=denis@poolshark.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=sander@humilis.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;
as well as URLs for NNTP newsgroup(s).