mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: 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: Fri, 9 Nov 2007 07:02:30 -0800	[thread overview]
Message-ID: <20071109070230.73eb7be5@laptopd505.fenrus.org> (raw)
In-Reply-To: <20071109045748.GD25581@havoc.gtf.org>

On Thu, 8 Nov 2007 23:57:48 -0500
Jeff Garzik <jeff@garzik.org> wrote:

> On Thu, Nov 08, 2007 at 11:44:22PM -0500, Mark Lord wrote:
> > Jeff Garzik wrote:
> > >On Thu, Nov 08, 2007 at 10:29:37PM -0500, Mark Lord wrote:
> > >>And I might even privately patch my own kernels to map the ACHI
> > >>BAR in the cases where the BIOS didn't...
> > >
> > >The inability to do this in the general case is the main reason why
> > >AHCI was not unconditionally enabled, even in IDE mode, when it was
> > >originally added...  :/
> > ..
> > 
> > Yeah, that one's always puzzled me.
> > It's just software,  so why don't we do it?  In the PCI layer, that
> > is?
> 
> Ah, but it's not just software:  when trying to find bus address
> space for the BAR, we don't know if we are stomping on magic hardware
> resources the BIOS has conveniently failed to tell us about.
> 
> So while in all likelihood you will have no problem finding a
> suitable bus address to use, as a generalized rule it is a far more
> difficult proposition.
> 

another thing to test before doing this everywhere is suspend/resume.
This would use the hardware in a way the bios doesn't expect, and sadly
that kind of thing tends to royally b0rk the suspend/resume code often
(but of course not always).


-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2007-11-09 15:04 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09  2:02 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 [this message]
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
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=20071109070230.73eb7be5@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®