From: Jon S. <jon...@gm...> - 2005-06-24 12:26:21
|
On 6/23/05, James Simmons <jsi...@ww...> wrote: > Now I was thinking instead of a massive move of the the software > cursor we add a flag FBINFO_HWACCEL_CURSOR to tell us if we are using a > hardware cursor. This way for the sysfs interface you can test to see if > it is a hardware cursor and only allow userland to access a hardware > cursor. Here is a patch for that. People please try it out. Your code will work, but it is conceptually what we want to do? Software cursors are application specific. The soft cursor implemented in fbdev really belongs to fbconsole. If we get another in-kernel user with a different update pattern (maybe they use the GPU) they will want a different soft cursor. Shouldn't we just move the current soft cursor into fbconsole? Given that software cursors are application specific fbdev should not contain one. --=20 Jon Smirl jon...@gm... |