From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id F3E84474FB for ; Wed, 7 Jan 2009 09:02:57 +1100 (EST) Subject: Re: [QUESTION] 440EPx with PCI to PCIe bridge error From: Benjamin Herrenschmidt To: "Steven A. Falco" In-Reply-To: <4963CF68.3040808@harris.com> References: <496268E7.5090907@harris.com> <1231190318.14860.17.camel@pasglop> <49627D33.8030605@harris.com> <1231223634.14860.18.camel@pasglop> <4963C1DE.6020007@harris.com> <4963CF68.3040808@harris.com> Content-Type: text/plain Date: Wed, 07 Jan 2009 09:02:20 +1100 Message-Id: <1231279340.14860.31.camel@pasglop> Mime-Version: 1.0 Cc: "linuxppc-dev@ozlabs.org" , Wolfgang Denk List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 2009-01-06 at 16:38 -0500, Steven A. Falco wrote: > But this has no effect on Linux. So, I also changed the sequoia.dts > to make the outbound range larger, and now Linux is happy too. I now > have ranges for the device: > > # cat 0000:01:00.0/resource > 0x0000000190000000 0x000000019007ffff 0x0000000000020200 > 0x0000000180000000 0x000000018fffffff 0x0000000000020200 So your problem is fixed ? I didn't have a chance yet to look at your logs, but it could just have been that you didn't have enough space allocated to PCI for your card... Cheers, Ben.