Messages in this thread | | | Date | Mon, 26 Apr 2004 11:10:06 +0200 (MEST) | From | Geert Uytterhoeven <> | Subject | Re: [Linux-fbdev-devel] vesafb and *fb |
| |
On Sun, 25 Apr 2004, Alan Cox wrote: > 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)
But vesafb is meant to be used as a fallback, if no chipset-specific driver is found.
Gr{oetje,eeting}s,
Geert
-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds - 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/
| |