linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Theodore Tso <tytso@mit.edu>, Jeff Garzik <jeff@garzik.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>, Mark Lord <liml@rtr.ca>,
	Riki Oktarianto <rkoktarianto@gmail.com>, linux-kernel@vger.
Subject: Re: [PATCH] Add quirk to set AHCI mode on ICH boards
Date: Fri, 09 Nov 2007 22:57:28 -0500	[thread overview]
Message-ID: <47352C28.4070604@garzik.org> (raw)
In-Reply-To: <20071110035424.GB28975@thunk.org>

Theodore Tso wrote:
> On Fri, Nov 09, 2007 at 10:05:05PM -0500, Jeff Garzik wrote:
>> By forcing AHCI, your PATA devices will be inaccessible, in a common 
>> configuration.  It also means shuffling users from one driver to another, 
>> which induces breakage.
>>
>> I was speaking wishfully.  Real life intrudes, alas.
> 
> Not even as boot-time option?  I'm curious whether it might allow me
> to use AHCI mode on a T60p laptop; right now I can't because in AHCI
> mode the Ultrabay hard drive device becomes invisible to Linux
> (although not to Windows, interestingly).  I'm currently travelling
> and I don't carry the T60 around anymore, so I can't do the experiment
> right this moment, but given that this would allow the T60 to take
> advantage of ALPM if this works, it would be awfully tempting....

Oh sure, a boot-time option would be fine.

I want to spread AHCI far and wide; it is vastly superior to ata_piix in 
many ways.

I was mainly talking about unconditionally changing behavior from the 
current default, which presents several problems.

	Jeff




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

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071109020235.GA2031@ceren>
2007-11-09  2:31 ` [PATCH] Add quirk to set AHCI mode on ICH boards 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
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 [this message]
2007-11-10 18:37           ` Allen Martin
2007-11-10 19:04             ` Jeff Garzik
2007-11-13  7:27               ` Allen Martin
2007-11-13 15:27                 ` Alan Cox
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=47352C28.4070604@garzik.org \
    --to=jeff@garzik.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=liml@rtr.ca \
    --cc=linux-kernel@vger. \
    --cc=rkoktarianto@gmail.com \
    --cc=tytso@mit.edu \
    /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).