Messages in this thread | | | Subject | Re: [Linux-fbdev-devel] vesafb and *fb | From | Alan Cox <> | Date | Sun, 25 Apr 2004 16:29:28 +0100 |
| |
On Sul, 2004-04-25 at 14:13, Geert Uytterhoeven wrote: > > > if (!request_mem_region(vesafb_fix.smem_start, vesafb_fix.smem_len, "vesafb")) { > > > printk(KERN_WARNING > > > "vesafb: abort, cannot reserve video memory at 0x%lx\n", > > > vesafb_fix.smem_start); > > > /* We cannot make this fatal. Sometimes this comes from magic > > > spaces our resource handlers simply don't know about */
Various built-in video systems broke on that test because we didnt have resources for them so the resources couldnt be allocated. Probably if vesafb is enabled we should skip any primary video device (ie the one with VGA_EN at boot)
- 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/
| |