Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752555AbXI0AlN (ORCPT ); Wed, 26 Sep 2007 20:41:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751946AbXI0Ak4 (ORCPT ); Wed, 26 Sep 2007 20:40:56 -0400 Received: from gate.crashing.org ([63.228.1.57]:58282 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753543AbXI0Akz (ORCPT ); Wed, 26 Sep 2007 20:40:55 -0400 Subject: Re: [PATCH]PCI:disable resource decode in PCI BAR detection From: Benjamin Herrenschmidt Reply-To: benh@kernel.crashing.org To: Robert Hancock Cc: Ivan Kokshaysky , Greg KH , Matthew Wilcox , Shaohua Li , lkml , linux-pci , Andrew Morton In-Reply-To: <46FAE4CE.10801@shaw.ca> References: <46FAE4CE.10801@shaw.ca> Content-Type: text/plain Date: Thu, 27 Sep 2007 10:40:33 +1000 Message-Id: <1190853633.11034.6.camel@pasglop> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 697 Lines: 18 > How is this a change in behavior as far as this device is concerned? If > we are doing BAR sizing and moving the base address around, it's going > to cause problems if you try to access the device during this time > whether we disable decode or not. True. The window is smaller tho if the upper bridge decode hasn't been disabled. I suppose I'll have to find a way to "pin" those devices and generate the BAR info from the firmware data. Ben. - 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/