[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080114230448.GL9847@does.not.exist>
Date: Tue, 15 Jan 2008 01:04:48 +0200
From: Adrian Bunk <bunk@...nel.org>
To: Matthew Wilcox <matthew@....cx>
Cc: Arjan van de Ven <arjan@...radead.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Ivan Kokshaysky <ink@...assic.park.msu.ru>,
Greg KH <greg@...ah.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg KH <gregkh@...e.de>, linux-kernel@...r.kernel.org,
Jeff Garzik <jeff@...zik.org>,
linux-pci@...ey.karlin.mff.cuni.cz, Martin Mares <mj@....cz>,
Tony Camuso <tcamuso@...hat.com>, Loic Prylli <loic@...i.com>
Subject: Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver
opt-in
On Mon, Jan 14, 2008 at 03:52:26PM -0700, Matthew Wilcox wrote:
> On Sun, Jan 13, 2008 at 09:01:08AM -0800, Arjan van de Ven wrote:
>...
> > > - pci_conf1_read(0, 0, PCI_DEVFN(0,0), 0xce, 2, &win);
> > > + pci_direct_conf1.read(0, 0, PCI_DEVFN(0,0), 0xce, 2, &win);
> >
> > couldn't this (at least in some next patch) use the vector if it exists?
>
> I thought so, but due to the way that things are initialised, mmconfig
> happens before conf1. conf1 is known to be usable, but hasn't set
> raw_pci_ops at this point. Confusing, and not ideal, but fixing this
> isn't in scope for 2.6.24.
>...
*ahem*
I don't think anything of what was discussed in this thread would be in
scope for 2.6.24 (unless Linus wants to let the bunny that brings eggs
release 2.6.24).
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--
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