06/02/2010 11:55 PM
qnx graphics driver development issue
I met some issues when developing graphics driver for qnx.
1. It looks like that all the modules in driver has to be built as binary. Can client driver module be separted with
server modules(loaded by io-display)?
2. What's the usage of gf_display_devctl, in ddk there is no description about this api.
In my implementation there is a core driver which manages the hw resource including mode and memory management, kick off
command to hw by dma buffer, it is loaded by io-display.
Instead of standard protocol such as set mode, allocated surface, I need some customized protocols to talk to resource
management modules from 2d client driver .
2d client driver -> io_display -> (resource management modules driver)
I tried to use gf_display_devctl , and implement devctl of mode module.But it mets the deak lock.
gf_draw_begin() -->lock the hw_mutex
gf_draw_flush() ->gf_display_devctl() ->io_display() it will also try to lock hw_mutex
gf_draw_end() -->unlock the hw_mutex
Is there ay path to bypass this lock?