c465e05a03
According to Jon Smirl, filling in the field fb_cursor with soft_cursor for drivers that do not support hardware cursors is redundant. The soft_cursor function is usable by all drivers because it is just a wrapper around fb_imageblit. And because soft_cursor is an fbcon-specific hook, the file is moved to the console directory. Thus, drivers that do not support hardware cursors can leave the fb_cursor field blank. For drivers that do, they can fill up this field with their own version. The end result is a smaller code size. And if the framebuffer console is not loaded, module/kernel size is also reduced because the soft_cursor module will also not be loaded. Signed-off-by: Antonino Daplas <adaplas@pol.net> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org> |
||
---|---|---|
.. | ||
g450_pll.c | ||
g450_pll.h | ||
i2c-matroxfb.c | ||
Makefile | ||
matroxfb_accel.c | ||
matroxfb_accel.h | ||
matroxfb_base.c | ||
matroxfb_base.h | ||
matroxfb_crtc2.c | ||
matroxfb_crtc2.h | ||
matroxfb_DAC1064.c | ||
matroxfb_DAC1064.h | ||
matroxfb_g450.c | ||
matroxfb_g450.h | ||
matroxfb_maven.c | ||
matroxfb_maven.h | ||
matroxfb_misc.c | ||
matroxfb_misc.h | ||
matroxfb_Ti3026.c | ||
matroxfb_Ti3026.h |