[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.58.0812201812100.19510@shell2.speakeasy.net>
Date: Sat, 20 Dec 2008 18:23:23 -0800 (PST)
From: Trent Piepho <xyzzy@...akeasy.org>
To: "Darrick J. Wong" <djwong@...ibm.com>
cc: Jesse Barnes <jbarnes@...tuousgeek.org>,
Rolf Eike Beer <eike-kernel@...tec.de>,
Alex Chiang <achiang@...com>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-pci <linux-pci@...r.kernel.org>
Subject: Re: [PATCH] fakephp: Allocate PCI resources before adding the?device
On Tue, 16 Dec 2008, Darrick J. Wong wrote:
> On Tue, Dec 16, 2008 at 11:33:33AM -0800, Jesse Barnes wrote:
> > > I read it, but that's the way a kernel works: if you want to talk to a
> > > device, get a driver. You can write a rather minimal one that does only
> > > pci_enable_device() on probe and pci_disable_device() on remove. Try the
> > > one posted by Chris Wright in "[PATCH 2/2] PCI: pci-stub module to reserve
> > > pci device" as a starting point.
> >
> > Ok, so sounds like Darrick's original patch gets a NAK? I guess the fakephp
> > vs. dummyphp vs. new interface stuff can be dealt with in another thread...
>
While fakephp may be a mess, Darrick's patch does fix a problem with it.
> In any case, I gave 2.6.24 a whirl. 2.6.24 fakephp sets up the BARs
> correctly, so technically this is a regression fix too, even if only a
> stopgap.
I know 2.6.23 has the same problem with resources not being assigned
correctly to BARs as 2.6.27. It doesn't look like there are any patches in
2.6.24 that would have fixed it.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists