[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <479F53B1.9000101@redhat.com>
Date: Tue, 29 Jan 2008 11:26:25 -0500
From: Tony Camuso <tcamuso@...hat.com>
To: Arjan van de Ven <arjan@...radead.org>
CC: Greg KH <greg@...ah.com>, Matthew Wilcox <matthew@....cx>,
Grant Grundler <grundler@...isc-linux.org>,
Loic Prylli <loic@...i.com>, Adrian Bunk <bunk@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Ivan Kokshaysky <ink@...assic.park.msu.ru>,
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>
Subject: Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver
opt-in
Arjan van de Ven wrote:
> On Tue, 29 Jan 2008 10:15:45 -0500
> Tony Camuso <tcamuso@...hat.com> wrote:
>
>> specific to legacy x86 hardware is, IMNSHO, a kludge.
>
> in addition to pci_enable(), pci_enable_msi(), pci_enable_busmaster() they already need to do
> to enable various features?
>
These calls are related to generic aspects of the PCI* landscape itself and are
not related to any arch-specific hardware, nor were they devised to address
chipset-specific or BIOS-specific problems.
For the good of all, we should endeavor to avoid putting arch-specific fixes into
the generic code whenever possible.
And in this case, not only is it possible, it's been done and tested.
--
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