|
From: Andrey V. <av...@va...> - 2005-08-10 16:19:06
|
Antonino A. Daplas wrote: > Jon Smirl wrote: > >> On 8/10/05, Andrey Volkov <av...@va...> wrote: >> You are omit hwd cursor size problem - very few (possible no one) >> graphics chips could support cursor with any size. Usually they support >> 32x32/64x64 pixels cursors only. For kernel fb its have not meaning, >> 'cause we always could fallback to the soft_cursor (in the fbcon or >> directly in a driver), BUT what to do with such crazy user who will wish >> to use, ex. 100x100 pix cursor in user space? >> >> > > If cursor_capabilities() is called, it should return the maximum > dimensions supported by the hardware. > Meaning, we have to change it to: > > int (*cursor_capabilities)(int set, struct fb_cursor_caps *caps); > > so it passes struct fb_cursor_caps *caps instead of int caps. > And max_depth also must present in struct fb_cursor_caps. Why generate true_color image for monochrome hwd cursor? Conversion from true_color to monochrome, IMHO, usually very painful. -- Regards Andrey Volkov |