Linux ATA/IDE development
 help / color / mirror / Atom feed
From: "Dâniel Fraga" <fragabr@gmail.com>
To: Robert Hancock <hancockrwd@gmail.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-ide@vger.kernel.org
Subject: Re: ICH10 not working with AHCI kernel option
Date: Thu, 8 Apr 2010 23:22:10 -0300	[thread overview]
Message-ID: <4bbe8f84.1502be0a.0f89.0f16@mx.google.com> (raw)
In-Reply-To: <n2x51f3faa71004081909la494824ds60fcb5d26b53027a@mail.gmail.com>

On Thu, 8 Apr 2010 20:09:29 -0600
Robert Hancock <hancockrwd@gmail.com> wrote:

> Think you meant sata_nv or something there, forcedeth is the network
> driver :-) In that case that's not really legacy mode though, it's

	Oh yeah, sorry for my confusion ;) sata_nv. ;)

> some chipset-specific enhanced mode like SWNCQ or ADMA in the NVIDIA
> case, or the newer Silicon Image controllers which support the fancy
> features with an entirely different interface from AHCI. In the case
> of Intel controllers, though, IDE mode is basically the same as a PATA
> controller with no real SATA-specific features (NCQ, 64-bit DMA,
> hotplug, etc.)

	Very interesting and thanks again for the excellent explanation
Robert!

	Ps: I imagine how many people are running their servers or
desktop computers using the legacy PIIX driver, just because the BIOS
setting is wrong (IDE instead of AHCI). In my case I just ignored the
"RAID mode" option because I don't ever use RAID.

	Don't you think it would be nice to add a warning message
when the kernel detects  AHCI capable system like ICH10 and the kernel
is misconfigured using the legacy PIIX driver? It could be
something like that: "AHCI capable chipset: use ahci driver instead".

	Ps2: sorry sending 2 times (forget to send to the list)

-- 

  reply	other threads:[~2010-04-09  2:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08 13:36 ICH10 not working with AHCI kernel option Dâniel Fraga
2010-04-08 13:45 ` Alan Cox
2010-04-08 13:46   ` Dâniel Fraga
2010-04-08 13:59     ` Alan Cox
2010-04-08 14:02       ` Dâniel Fraga
2010-04-08 14:09         ` Alan Cox
2010-04-08 14:15           ` Dâniel Fraga
2010-04-08 23:54             ` Robert Hancock
2010-04-09  2:00               ` Dâniel Fraga
2010-04-09  2:09                 ` Robert Hancock
2010-04-09  2:22                   ` Dâniel Fraga [this message]
2010-04-09  2:52                     ` Robert Hancock
2010-04-09  3:16                       ` Dâniel Fraga
2010-04-09 10:12                       ` Tim Small
2010-04-09 14:47                         ` Robert Hancock
2010-04-09 15:07                           ` Alan Cox
2010-04-09 16:37                             ` Tim Small
2010-04-09 18:53                               ` Alan Cox
2010-04-09 23:04                               ` Robert Hancock
2010-04-09  4:28                 ` Jeff Garzik
2010-04-09  9:16                 ` Alan Cox
2010-04-09  9:08               ` Alan Cox
2010-04-09  9:12                 ` Dâniel Fraga

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=4bbe8f84.1502be0a.0f89.0f16@mx.google.com \
    --to=fragabr@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hancockrwd@gmail.com \
    --cc=linux-ide@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