All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: Jeff Garzik <jeff@garzik.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Mark Lord <liml@rtr.ca>,
	Riki Oktarianto <rkoktarianto@gmail.com>,
	linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH] Add quirk to set AHCI mode on ICH boards
Date: Sat, 10 Nov 2007 12:20:29 +0100	[thread overview]
Message-ID: <20071110112029.GA25827@citd.de> (raw)
In-Reply-To: <47352095.4010502@garzik.org>

On 09.11.2007 22:08, Jeff Garzik wrote:
> Matthias Schniedermeyer wrote:
>> And on the topic of "broken" BIOSes. I have a little empathy for the MB 
>> manufactures as non-RAID AHCI royaly screws Windos, so not supporting it 
>> reduces their support costs enough to overlook screwing the non-windos 
>> faction.
>
> non-RAID AHCI works just fine on Windows.

Last i know is that Intel doesn't provide an AHCI driver for the 
non-RAID version. (For whatever political reason). That is even 
documented in the german "c't", they even had an articel about "patching 
in the Device-IDs" so the RAID-AHCI driver accepts the non-RAID AHCI 
chipsets.

And i can second that, when i configure my @home MB (ASUS P5B = non-RAID) 
to AHCI neither XP nor Vista work.

@work i tried to install Vista on an AHCI-configured machine and aborted 
that "expriment" after about 2 hours. In IDE-mode it took Vista about 3 
Minutes to reach the point where i aborted the AHCI experiment.


So i must say: My milage varies.




Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as 
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated, 
cryptic, powerful, unforgiving, dangerous.


  reply	other threads:[~2007-11-10 11:20 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09  2:02 [PATCH] Add quirk to set AHCI mode on ICH boards Riki Oktarianto
2007-11-09  2:31 ` Jeff Garzik
2007-11-09  3:29   ` Mark Lord
2007-11-09  3:46     ` Jeff Garzik
2007-11-09  4:44       ` Mark Lord
2007-11-09  4:57         ` Jeff Garzik
2007-11-09 15:02           ` Arjan van de Ven
2007-11-09 12:04       ` Alan Cox
2007-11-09 14:49         ` Török Edwin
2007-11-09 22:38           ` Riki Oktarianto
2007-11-09 23:32         ` Matthias Schniedermeyer
2007-11-10  3:08           ` Jeff Garzik
2007-11-10 11:20             ` Matthias Schniedermeyer [this message]
2007-11-10 11:26             ` Matthias Schniedermeyer
2007-11-10 18:01           ` Mark Lord
2007-11-10 18:38             ` Matthias Schniedermeyer
2007-11-11 14:05               ` Thorsten Leemhuis
2007-11-11 18:24                 ` Matthias Schniedermeyer
2007-11-10  3:05         ` Jeff Garzik
2007-11-10  3:54           ` Theodore Tso
2007-11-10  3:57             ` Jeff Garzik
2007-11-10  3:57               ` Jeff Garzik
2007-11-10 18:37           ` Allen Martin
2007-11-10 18:37             ` Allen Martin
2007-11-10 19:04             ` Jeff Garzik
2007-11-13  7:27               ` Allen Martin
2007-11-13  7:27                 ` Allen Martin
2007-11-13 15:27                 ` Alan Cox
2007-11-13 15:27                   ` Alan Cox
2007-11-14 18:35                   ` Allen Martin
2007-11-14 18:35                     ` Allen Martin
2007-11-14 18:46                     ` Mark Lord
2007-11-14 18:58                       ` Greg KH
2007-11-09 12:45   ` Riki Oktarianto

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=20071110112029.GA25827@citd.de \
    --to=ms@citd.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@suse.de \
    --cc=jeff@garzik.org \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkoktarianto@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.