> On 29 May 00 at 13:58, Yuri Per wrote:
> > The check "con == currcon" is the same as in ALL other framebuffer drivers.
> > If this is wrong, all drivers should be changes, not only the ATI one.
> It depends... If driver can have more than one instance of hardware driven
> by same module, then check is wrong - you must have per-fb_info curcon
> (like matroxfb has). If you have different drivers, it is OK, as each
> driver has its own currcon (of course, you must mark 'currcon' static, not
> exported, otherwise it will not work as expected).
I prefere if the driver used info->display_fg->num to info->currcon because
we can easily make fbcon.c aware of info->display_fg since its already
in fb_info versus info->currcon which is only in a handful of drivers.
Q: Why did they deprecate a.out support in linux?
A: Because a nasty coff is bad for your elf.
James Simmons [jsimmons@linux-fbdev.org] ____/|
fbdev/console/gfx developer \ o.O|
http://www.linux-fbdev.org =(_)=
http://linuxgfx.sourceforge.net U
http://linuxconsole.sourceforge.net
-
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/
This archive was generated by hypermail 2b29 : Wed May 31 2000 - 21:00:23 EST