path: root/drivers/misc/blink.c
diff options
authorLinus Torvalds <torvalds@woody.linux-foundation.org>2007-07-01 10:56:11 -0700
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-07-01 10:56:11 -0700
commit4710bcce8e02257c8a423b7a62ea81d0207582c8 (patch)
tree1a24a3f1dc4b6539b3a75beb70091cbe7da37594 /drivers/misc/blink.c
parentabdba717253382a669af9c719313ec602cc95a2d (diff)
i386: remove bogus mtrr range check
Commit 9215da33209b861b01c51382254b178a3fe92a30 "fixed" the MTRR range check to not allow any MTRR's under the 1MB mark (since that's where the fixed MTRR's are active). However, that was totally bogus, since it's normal (and almost required) to have a large variable MTRR that starts at 0, and covers some large percentage of the whole RAM, and then using the fixed MTRR's to override that large MTRR to handle the special ISA hole in the 640k-1M region. The old check was bogus too (checking that no variable MTRR is used that is entirely under the 1MB range), but at least it wasn't actively detrimental, because no sane situation would ever trigger such MTRR usage in the first place. That said, the whole notion of not allowing variable MTRR's in the low 1MB is just stupid, so rather than revert the commit, this just removes the whole sad and unnecessary check entirely. Cc: Jan Beulich <jbeulich@novell.com> Cc: Andi Kleen <ak@suse.de> Cc: Andrew Morton <akpm@linux-foundation.org> Tested-by: Luca Palermo <darkmage@sabayonlinux.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/misc/blink.c')
0 files changed, 0 insertions, 0 deletions