public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andre Tomt <andre@tomt.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [sata] new driver -- AHCI
Date: Thu, 29 Apr 2004 16:24:52 +0200	[thread overview]
Message-ID: <40911034.4040404@tomt.net> (raw)
In-Reply-To: <409073B1.1020901@pobox.com>

Jeff Garzik wrote:
>> Quick questions:
>>
>> Is the Intel 6300ESB ("Hence Rapids") AHCI based? So far this looks 
>> like ICH6 too me, but I may be mistaken.
> 
> The only Hance Rapids stuff I've seen was ICH5-R, but maybe it's carried 
> forward to the ICH6-R as well.
> 
> I don't know, I mainly know the underlying chipsets not the boards they 
> wind up being shipped on...

Ahh, ok. I'll try to dig a bit deeper, but finding such details on 
vendor websites is not always easy. Anyway, the board I'm looking at has 
a 64bit 66Mhz PCI-X bus & slot (it's a low-end server/workstation board, 
Intel E7210 Canterwood ES/MCH+6300ESB+FWH chipset), so the controller 
can easily be replaced with something else without losing out to much on 
the performance side of things. Like the Marvell, wich is on the PCI-X 
bus, onboard.

>> What about the Marvell 88SX5040 PCI-X SATA Controller?
> 
> Coming RSN.  That's my next priority, but I'm not as thrilled because 
> Marvell isn't an open design like AHCI.  I'm much more happy to promote 
> AHCI's sane, open design.

Sounds like a plan :-)

      parent reply	other threads:[~2004-04-29 14:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-25 20:27 [sata] new driver -- AHCI Jeff Garzik
2004-04-25 21:29 ` Sven Köhler
2004-04-29  1:25 ` Andre Tomt
2004-04-29  3:17   ` Jeff Garzik
2004-04-29  8:16     ` Marc Bevand
2004-04-29  8:56       ` Jeff Garzik
2004-04-29 14:24     ` Andre Tomt [this message]

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=40911034.4040404@tomt.net \
    --to=andre@tomt.net \
    --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