Re: pci-disable-decode-of-io-memory-during-bar-sizing.patch

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Jesse Barnes <jbarnes@...>
Cc: Arjan van de Ven <arjan@...>, Robert Hancock <hancockr@...>, Greg KH <greg@...>, <akpm@...>, <ak@...>, <rajesh.shah@...>, linux-kernel <linux-kernel@...>
Date: Tuesday, October 30, 2007 - 6:22 pm

On Tue, 30 Oct 2007, Jesse Barnes wrote:

Trust me, it is.

The particular problem _you_ had with it is only a small small part of the 
bugs we have had.


No. You really don't see the big picture. There's been tons of problems 
with MMCONFIG. Like the fact that other devices have their IO regions 
registered on top of it, because the MMCONFIG thing was done as a hidden 
resource. Or the fact that the area claimed was too small. Or too large. 
Or not listed at all.

The whole thing is a total disaster. I told Intel engineers literally 
*years* ago to not do that idiotic "hidden IO resources that are described 
by firmware that then inevitably gets things wrong", and yet what happens? 
Every single time.

			Linus
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: pci-disable-decode-of-io-memory-during-bar-sizing.patch, Linus Torvalds, (Tue Oct 30, 11:15 am)
Re: pci-disable-decode-of-io-memory-during-bar-sizing.patch, Arjan van de Ven, (Tue Oct 30, 12:47 pm)
Re: pci-disable-decode-of-io-memory-during-bar-sizing.patch, Arjan van de Ven, (Tue Oct 30, 7:52 pm)
Re: pci-disable-decode-of-io-memory-during-bar-sizing.patch, Linus Torvalds, (Tue Oct 30, 6:22 pm)
Re: pci-disable-decode-of-io-memory-during-bar-sizing.patch, Arjan van de Ven, (Tue Oct 30, 1:28 pm)
Re: pci-disable-decode-of-io-memory-during-bar-sizing.patch, Arjan van de Ven, (Thu Nov 1, 10:08 am)