Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752814Ab1BHVVA (ORCPT ); Tue, 8 Feb 2011 16:21:00 -0500 Received: from cpoproxy1-pub.bluehost.com ([69.89.21.11]:44199 "HELO cpoproxy1-pub.bluehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752178Ab1BHVU6 (ORCPT ); Tue, 8 Feb 2011 16:20:58 -0500 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=virtuousgeek.org; h=Received:Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References:X-Mailer:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=uSwdhRncqvSbt4KYUO1guPZ+20VnDemahVmKafDwrCXiHgWK7WE/pXp82MS44zRt4nnS/fyNBPf70PKtN8EUvSP/HUAjRcGX++icalAgBdoNyBoUQ6eWqurA/mnRycbX; Date: Tue, 8 Feb 2011 13:20:55 -0800 From: Jesse Barnes To: Jiri Slaby Cc: Bjorn Helgaas , Linus Torvalds , linux-pci@vger.kernel.org, linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, "David S. Miller" , Thomas Renninger Subject: Re: [PATCH 1/1] PCI: tune up ICH4 quirk for broken BIOSes Message-ID: <20110208132055.1c55ff93@jbarnes-desktop> In-Reply-To: <4D5112F5.8030700@gmail.com> References: <1294327066-23518-1-git-send-email-jslaby@suse.cz> <4D3025F4.6020001@gmail.com> <201101140910.07154.bjorn.helgaas@hp.com> <4D5112F5.8030700@gmail.com> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.18.9; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Identified-User: {10642:box514.bluehost.com:virtuous:virtuousgeek.org} {sentby:smtp auth 67.174.193.198 authed with jbarnes@virtuousgeek.org} Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2195 Lines: 51 On Tue, 08 Feb 2011 10:55:01 +0100 Jiri Slaby wrote: > On 01/14/2011 05:10 PM, Bjorn Helgaas wrote: > > On Friday, January 14, 2011 03:31:16 am Jiri Slaby wrote: > >> On 01/14/2011 01:15 AM, Linus Torvalds wrote: > >>> On Thu, Jan 13, 2011 at 3:19 PM, Bjorn Helgaas wrote: > >>>> > >>>> I think we're back to the question of why we have the ICH4 quirk in > >>>> the first place, and I don't know the answer to that. > >>> > >>> Iirc, there were several laptops that didn't have the ACPI region > >>> mentioned in any of the regular places, and we'd allocate the PCMCIA > >>> IO region on top of them. The machine would boot, but if anybody ever > >>> inserted a PCCard into the machine, the first access to the IO region > >>> would generally just halt it (because it was trying to read the > >>> PCCard, but the APCI region decodes first, and then the read from that > >>> usually put the CPU in a sleep state that it would never wake up from > >>> for obvious reasons). > >>> > >>> So we do want the ICH4 quirk. > >> > >> Yes, this is an "official" way how ICH4 (and later) advertises the region. > > > > The quirk is a bug workaround, *not* the "official, planned" way to > > deal with these regions. The official way is to use ACPI, because > > that's a generic way that doesn't require changes for new versions > > of ICH. > > Ok, I understand that. For non-ACPI setups this is probably the only > place to look at. > > Anyway, has anybody had a chance to look at the patches? Any comments, > nacks/acks? > > https://lkml.org/lkml/2011/1/14/115 > https://lkml.org/lkml/2011/1/14/113 > https://lkml.org/lkml/2011/1/14/114 I don't have a problem making the quirk quirkier, but it would be nice to get rid of the need for it entirely (though we can leave that to Bjorn :). Can you re-submit these three against my linux-next branch? Thanks, -- Jesse Barnes, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/