Well, alrighty then. Your patch worked. At least, /proc/mtrr is now
there, and can be interfaced with. How to verify that X takes
advantage of it? I saw some docs on framebuffer stuff with mtrr, but
can't remember where...
Anyhow, the patch applied smoothly to 2.2.6 except for vesafb.c.
Here's what I used:
--- vesafb.c.orig Sun Apr 18 02:26:11 1999
+++ vesafb.c Sun Apr 18 23:29:32 1999
@@ -635,10 +635,10 @@
video_cmap_len = 256;
}
request_region(0x3c0, 32, "vga+");
-#ifdef CONFIG_MTRR
- if (mtrr)
+// #ifdef CONFIG_MTRR
+// if (mtrr)
mtrr_add((unsigned long)video_base, video_size, MTRR_TYPE_WRCOMB, 1);
-#endif
+//#endif
strcpy(fb_info.modename, "VESA VGA");
fb_info.changevar = NULL;
I'm not sure how much of a difference that change makes, but it's
working ok, now, so...
Is Linus just waiting for stability reports on the AMD/Cyrix code
before he includes it in the kernel? If so, what types of tests could
I run and submit to test it's stability?
-- Matthew Vanecek Course of Study: http://www.unt.edu/bcis Visit my Website at http://people.unt.edu/~mev0003 For answers type: perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);' ***************************************************************** For 93 million miles, there is nothing between the sun and my shadow except me. I'm always getting in the way of something...
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/