On Tue, 9 Sep 2003, Petr Vandrovec wrote:

On Mon, Sep 08, 2003 at 10:57:34PM +0200, Geert Uytterhoeven wrote:

quoted

On Mon, 8 Sep 2003, Petr Vandrovec wrote:

quoted

And whole fb subsystem changed semantic, so do not build both
vesafb & matroxfb into the kernel - either one or another, or
you'll be definitely surprised what will happen (and I'm almost
sure that blank screen is not what you want).

What's wrong with the resource system that prevents this from working?

vesafb ignore failures... for framebuffer it just prints warning only, and
for 0x3C0 region it just completely ignores warning (due to vgacon
clash). But it should not be serious, user should just get console 
on matroxfb, and vesafb on /dev/fb1 doing nothing.

OK.

Main thing which prevents this from working as users expects is that
modular fbdevs cannot be used by fbcon. So people cannot create
initrd scripts which load proper fbdev driver anymore, after detecting
hardware and making sure that hardware & user wishes & driver are
compatible. They now have to build fbdevs to the kernel, and hope for
the best...

Ugh, didn't know that...

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