This adjusts the VESA fb driver to the new bus mapping API.
I think that this time this is providing the right replacement.... but
who knows
what DM had in mind once again...
At least this is working on my notebook without any glitch
--------------080909080006050100010108
Content-Type: text/plain;
name="vesafb.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="vesafb.patch"
diff -ur linux-2.5.4/drivers/video/vesafb.c linux/drivers/video/vesafb.c
--- linux-2.5.4/drivers/video/vesafb.c Mon Feb 11 02:50:09 2002
+++ linux/drivers/video/vesafb.c Thu Feb 14 13:17:02 2002
@@ -550,7 +550,7 @@
ypan = pmi_setpal = 0; /* not available or some DOS TSR ... */
if (ypan || pmi_setpal) {
- pmi_base = (unsigned short*)bus_to_virt(((unsigned long)screen_info.vesapm_seg << 4) + screen_info.vesapm_off);
+ pmi_base = (unsigned short*)isa_bus_to_virt(((unsigned long)screen_info.vesapm_seg << 4) + screen_info.vesapm_off);
pmi_start = (void*)((char*)pmi_base + pmi_base[1]);
pmi_pal = (void*)((char*)pmi_base + pmi_base[2]);
printk(KERN_INFO "vesafb: pmi: set display start = %p, set palette = %p\n",pmi_start,pmi_pal);
--------------080909080006050100010108--
-
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/