- 18 Feb, 2013 2 commits
-
-
Siarhei Siamashka authored
Actually they are converted to 32x32 with 256 color palette. In the case if we have more than 256 unique colors, the color components of the pixels are reduced from 8-bit to 7-bit, then to 6-bit if necessary and so on (until we reduce the number of unique colors so that they can fit the palette). In the worst case we may theoretically end up with just 2 bits per A, R, G and B channels, but in practice 7 or 6 bits seem to be enough. Signed-off-by: Siarhei Siamashka <siarhei.siamashka@gmail.com>
-
Siarhei Siamashka authored
The modern desktops may use ARGB cursors. As the current sunxi display controller support code can't handle this type of cursor yet, the X server fallbacks to a software cursor which is not visible under layers and ruining user experience. This patch adds empty implementations for "UseHWCursorARGB" and "LoadCursorARGB" functions which just return error for now (so that the X server still fallbacks to software cursor). However we also introduce callback functions responsible for notifying the DRI2 code about enabling/disabling the use of hardware cursor. So that now hardware overlays are disabled when switching to software cursor and re-enabled again when switching back to hardware cursor. Signed-off-by: Siarhei Siamashka <siarhei.siamashka@gmail.com>
-
- 20 Jan, 2013 1 commit
-
-
Siarhei Siamashka authored
Hardware cursor is necessary because it is also visible on top of sunxi disp layers, while software cursor is not. FIXME: there is one minor problem with negative cursor positions. The hardware does not support them, so such positions are just set to 0 for now. In the future this can be solved better by changing the cursor picture and showing only the parts which are visible on screen.
-