Craig, I haven't actually tried this, but here's the scoop:
The davinci driver acceleration is done using a custom kernel module that you have to integrate into your kernel build and enable in the kernel config. Then you have to modprobe that kernel module which loads the acceleration code into the DSP and sets up a shared memory queue between the kernel driver and the DSP acceleration code. Denis, please correct me if I'm wrong but: The major issue that I see with the acceleration driver for the davinci is that you can't use the TI Codec Engine and still maintain the driver code in the DSP because the first the Codec Engine does is wipe the DSP and load it's own framework and requested codecs. The obvious solution would be to make a version of the DFB acceleration driver that fits the codec engine framework so that it can be loaded by program before initializing DFB and then notifying DFB to use codec engine calls instead. It seems like a boat load of work it would have to be a collaborative effort on the part of the DFB dev community to get it working. On an off-topic note: I'd be real interested in hearing some trials and tribulations in getting a davinci system setup. Anyone may contact me privately if they wish to exchange non-DFB related davinci platform ideas. DAVID A. KONDRAD Software Design Engineer On-Q/Legrand www.onqlegrand.com _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
