Graphics ddk

bridged with qdn.public.ddk.graphics
Post Reply
madoda

Graphics ddk

Post by madoda » Tue Feb 19, 2002 7:28 am

hallo people,
l'm a bit confused about how a graphics driver comunicates with the
neutrino system. all l know is that a graphics driver (resmgr) is made
up of a collection of DLL's. so can someone explain to me how a graphics
driver differs from a standard resource manager(frame work from roberts
book) with more emphasis on the inter process communication. Can l drive
a graphics card with this standard frame framework and if ja , how do
l create these shared objects (*.so) since the resource manager compiles
to an *.exe or *.elf data.

does it make sence to write a graphics driver using the stardard
resource manager ? advantages or disadvantages.

thanks in advance

madoda

Hardware Support Account

Re: Graphics ddk

Post by Hardware Support Account » Thu Feb 21, 2002 6:11 pm

io-graphics is the actual executable that loads the
required dlls which include the specific graphics chipset driver
dll.

Have you downloaded the graphics DDK? The docs in the DDK should
answer most of the questions you have about the frame work of the graphics
drivers. You can obtain the ddk's from here:

http://commercial.qnx.com/


Erick.



madoda <bongani.masuku@soft-gate.de> wrote:
hallo people,
l'm a bit confused about how a graphics driver comunicates with the
neutrino system. all l know is that a graphics driver (resmgr) is made
up of a collection of DLL's. so can someone explain to me how a graphics
driver differs from a standard resource manager(frame work from roberts
book) with more emphasis on the inter process communication. Can l drive
a graphics card with this standard frame framework and if ja , how do
l create these shared objects (*.so) since the resource manager compiles
to an *.exe or *.elf data.

does it make sence to write a graphics driver using the stardard
resource manager ? advantages or disadvantages.

thanks in advance

madoda

Post Reply

Return to “qdn.public.ddk.graphics”