From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gateway-1237.mvista.com (gateway-1237.mvista.com [63.81.120.158]) by ozlabs.org (Postfix) with ESMTP id 741BDDDF16 for ; Thu, 17 May 2007 04:06:35 +1000 (EST) Subject: Re: [PATCH 5/5] PCI fixes for the MPC8641 Rev 2.0 silicon and Rev 1.02 hardware From: Wade Farnsworth To: Jon Loeliger In-Reply-To: <1179333883.7018.20.camel@ld0161-tx32> References: <1179245829.8132.100.camel@rhino> <1179247809.8132.138.camel@rhino> <1179333883.7018.20.camel@ld0161-tx32> Content-Type: text/plain Date: Wed, 16 May 2007 11:06:34 -0700 Message-Id: <1179338794.8132.209.camel@rhino> Mime-Version: 1.0 Cc: linuxppc-dev List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 2007-05-16 at 11:44 -0500, Jon Loeliger wrote: > On Tue, 2007-05-15 at 11:50, Wade Farnsworth wrote: > > +static void __devinit early_mpc86xx_pcie(struct pci_dev *dev) > > +{ > > + dev->class = PCI_CLASS_BRIDGE_PCI << 8 | 0x1; > > +} > > What'd we decide on that 0x1 in there? > > Thanks, > jdl > > I originally thought that it the 0x1 was necessary, but it was pointed out to me that it should not be. If I remove the 0x1 I get some I/O resource allocation failures on the P2P bridge and its child devices. I'm currently investigating what the cause of this is. --Wade