From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756876Ab1BQQhG (ORCPT ); Thu, 17 Feb 2011 11:37:06 -0500 Received: from cavan.codon.org.uk ([93.93.128.6]:35335 "EHLO cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756819Ab1BQQhD (ORCPT ); Thu, 17 Feb 2011 11:37:03 -0500 Date: Thu, 17 Feb 2011 16:36:49 +0000 From: Matthew Garrett To: Jeff Garzik Cc: Joerg Dorchain , linux-ide@vger.kernel.org, LKML , linux-pci maillist Subject: Re: [Patch] enable AHCI mode on certain ich chipsets Message-ID: <20110217163649.GC20662@srcf.ucam.org> References: <20110216090548.GQ5778@Redstar.dorchain.net> <4D5C2974.4070608@garzik.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D5C2974.4070608@garzik.org> User-Agent: Mutt/1.5.18 (2008-05-17) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: mjg59@cavan.codon.org.uk X-SA-Exim-Scanned: No (on cavan.codon.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 16, 2011 at 02:45:56PM -0500, Jeff Garzik wrote: > How is the assignment of the AHCI BAR handled? Does this happen > automatically because it's an early fixup? > > That is traditionally the stumbling block... Yes, because it's an early fixup the kernel should allocate it itself. It's small enough that I'd hope we don't have trouble finding one... -- Matthew Garrett | mjg59@srcf.ucam.org