[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080113044748.GY18741@parisc-linux.org>
Date: Sat, 12 Jan 2008 21:47:48 -0700
From: Matthew Wilcox <matthew@....cx>
To: Arjan van de Ven <arjan@...radead.org>
Cc: tcamuso@...hat.com, 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,
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
On Sat, Jan 12, 2008 at 08:42:48PM -0800, Arjan van de Ven wrote:
> Wanne bet there'll be devices that screw this up? THere's devices that even screwed
> up the 64-256 region after all.
I don't know if they 'screwed it up'. There are devices that misbehave
when registers are read from pci config space. But this was never
guaranteed to be a safe thing to do; it gradualy became clear that
people expected to be able to read random registers and manufacturers
responded accordingly, but I don't think you were ever guaranteed to be
able to peek at bits of config space arbitrarily.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
--
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