Messages in this thread | | | Subject | Re: MTRR vesafb and wrong X performance | From | Alan Cox <> | Date | Mon, 29 Nov 2004 16:24:30 +0000 |
| |
On Llu, 2004-11-29 at 15:40, Dave Jones wrote: > which is an ugly hack for the above problem imo. > vesafb:nomtrr also fixes the problem, and leaves X free > to set things up correctly in my experience. > > If vesafb can't get it right, maybe it shouldn't be > attempted to do it in the half-assed way it currently does.
The problem is not vesafb its X. If someone would go fix the Xorg code to handle extending existing maps the problem will go away.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |