On Wed, 23 May 2007, Jesse Barnes wrote:
> On Wednesday, May 23, 2007 1:20 pm Linus Torvalds wrote:
> > On Wed, 23 May 2007, Jesse Barnes wrote:
> > > Fixed it (finally). I don't think moving the 64 bit probing around
> > > would make a difference, since we'd restore its original value
> > > anyway before moving on to the 32 bit probe which is where I think
> > > the problem is.
> >
> > Well, the thing is, I'm pretty sure there is at least one northbridge
> > that stops memory accesses from the CPU when you turn off the MEM bit
> > on it. Oops, you just killed the machine.
>
> Wow, that sounds like a pretty lame host bridge.
Umm. Why? Think about it.
You ASKED it to stop forwarding memory.
So who is lamer: the chip that does what it is told, or the software that
tells it to do it?
I'd vote for the software. Any programmer who expects the hardware to
"just do what I mean, not what I say" is not a programmer, but a dreamer.
You told it to not forward memory. Why complain when it does as told?
> > Quite frankly, if we just didn't use mmconfig, the whole issue would
> > go away. Isn't _that_ the much better solution?
>
> Not for systems with PCIe... and the platforms I've been having trouble
> with have PCIe slots, so I'd really like mmconfig to be used at least
> on machines with PCIe bridges. For other machines, it probably doesn't
> matter much. I don't know of any regular PCI devices offhand that
> really need extended config space.
Ehh. Even for PCIe, why not use the normal accesses for the first 256
bytes? Problem solved.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
