devg-tnt driver is in use, cursor is disabled and set to 0,0, then function gf_cursor_set() is called with following 
parameters:

gf_cursor_set(display, 0, internal_cursor);

Dump of internal_cursor:
internal_cursor->type=0
internal_cursor->hotspot.x=8
internal_cursor->hotspot.y=8
internal_cursor->cursor.bitmap.w=16
internal_cursor->cursor.bitmap.h=16
internal_cursor->cursor.bitmap.color0=FF000000
internal_cursor->cursor.bitmap.color1=FFFFFFFF
internal_cursor->cursor.bitmap.stride=2

Next dump:
internal_cursor->type=0
internal_cursor->hotspot.x=0
internal_cursor->hotspot.y=0
internal_cursor->cursor.bitmap.w=16
internal_cursor->cursor.bitmap.h=16
internal_cursor->cursor.bitmap.color0=FF000000
internal_cursor->cursor.bitmap.color1=FFFFFFFF
internal_cursor->cursor.bitmap.stride=2

type 0 is value GF_CURSOR_BITMAP of enum gf_cursor_type_t.

gf_cursor_set() always returns GF_ERR_PARM. These parameters are standard, the same data working with devg-tnt using 
Photon.

Derek, could you trace gf_cursor_set() with these parameters and say me what is wrong ? Looks like it is not a driver 
problem, it is a GF problem.