[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <478B88FE.5020109@redhat.com>
Date: Mon, 14 Jan 2008 11:08:30 -0500
From: Tony Camuso <tcamuso@...hat.com>
To: Arjan van de Ven <arjan@...radead.org>
CC: Alan Cox <alan@...rguk.ukuu.org.uk>,
Ivan Kokshaysky <ink@...assic.park.msu.ru>,
Greg KH <greg@...ah.com>, Matthew Wilcox <matthew@....cx>,
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,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Martin Mares <mj@....cz>, Loic Prylli <loic@...i.com>,
Prarit Bhargava <prarit@...hat.com>,
"Chumbalkar, Nagananda" <Nagananda.Chumbalkar@...com>,
"Schoeller, Patrick (Linux - Houston, TX)" <Patrick.Schoeller@...com>,
Bhavana Nagendra <bnagendr@...hat.com>
Subject: Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver
opt-in
Arjan van de Ven wrote:
> it's not pci_enable_mmconf(), it's pci_enable_extended_config_space... it's independent of the mechanism!
>
Arjan, you would be foisting this call on device drivers running on
arches that don't need any such distinction between extended config
space and < 256 bytes.
I still think it's a bad policy.
Let's endeavor to confine arch-specific quirks to the arch-specific
code.
--
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