From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from g1t0029.austin.hp.com (g1t0029.austin.hp.com [15.216.28.36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "bastion.smtp.hp.com", Issuer "RSA Data Security, Inc." (verified OK)) by ozlabs.org (Postfix) with ESMTP id E7107DDE9E for ; Tue, 19 Feb 2008 15:52:19 +1100 (EST) Message-Id: <20080219043952.845136014@ldl.fc.hp.com> Date: Mon, 18 Feb 2008 21:39:52 -0700 From: Bjorn Helgaas To: linux-pci@atrey.karlin.mff.cuni.cz To: linux-arch@vger.kernel.org Subject: [patch 0/4] RFC: PCI: consolidate several pcibios_enable_resources() implementations Cc: Chris Zankel , Grant Grundler , linux-parisc@vger.kernel.org, Matthew Wilcox , Kyle McMartin , linuxppc-dev@ozlabs.org, Paul Mackerras , linux-arm-kernel@lists.arm.linux.org.uk, Russell King List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , There are many implementations of pcibios_enable_resources() that differ in minor ways that look more like bugs than architectural differences. This patch series consolidates most of them to use the x86 version. This series is for discussion only at this point. I'm interested in feedback about whether any of the differences are "real" and need to be preserved. ARM and PA-RISC, in particular, have interesting differences: - ARM always enables bridge devices, which no other arch does - PA-RISC always turns on SERR and PARITY, which no other arch does Should other arches do the same thing, or are these somehow related to ARM and PA-RISC architecture? Bjorn --