linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Ryan Earl" <heretic@clanhk.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Status of the sata_sil driver for the VT8237
Date: Sat, 27 Mar 2004 21:47:48 -0600	[thread overview]
Message-ID: <40664AE4.8010003@clanhk.org> (raw)
In-Reply-To: <406643A8.2050808@pobox.com>

Jeff Garzik wrote:

> J. Ryan Earl wrote:
>
>> I was wondering, what is the state of the sata_sil driver for the VIA 
>> VT8237 southbridge (ie the one used commonly on their K8T 
>> motherboards).  Is this still beta?  Any known problems with it?
>
>
> Well prior to the most recent version, calling it "beta" was putting 
> it kindly.  I would call it broken :) which was why it was marked with 
> CONFIG_BROKEN...
>
> As of the most recent 2.6.5-rc2-bk snapshots, libata and sata_sil 
> should be pretty happy with each other.

I meant sata_via, I dunno why I said sata_sil; Freudian typo.  I was 
thinking of the current sii3112 I use, which has been stable and 
blazingly fast for awhile with the IDE driver--and a little little patch 
I keep applying.  I'm looking to upgrade a server with 2 Raptors in it 
to an A64 running 64-bit Linux of course.  I wanna get the HDs off the 
PCI bus and onto the VT8237 southbridge.  I was wondering if the driver 
for -that southbridge- was still considered beta.

-ryan

  reply	other threads:[~2004-03-28  3:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-28  2:10 Status of the sata_sil driver for the VT8237 J. Ryan Earl
2004-03-28  3:16 ` Jeff Garzik
2004-03-28  3:47   ` J. Ryan Earl [this message]
2004-03-28  7:37     ` Stefan Smietanowski
2004-03-28  7:48       ` J. Ryan Earl
2004-03-28 20:22         ` Jeff Garzik
2004-03-28 20:40           ` J. Ryan Earl

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=40664AE4.8010003@clanhk.org \
    --to=heretic@clanhk.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).