> We want to use h/w accelerated RFX decoder which is available in form of > OMX component on a specific h/w platform. We have integrated the OMX > component to client/X11 folder. Is this the right way of integrating a RFX > decoder implementation? Or is there a possibility of integrating the > decoder to libfreerdp-core module so that , on this h/w platform, the h/w > accelerated decoding functionality is available for both X11 and FB (and > possibly other) clients. Specifically we would like to know, why was the > decoder integration kept in client and not in libfreerdp-core folder. What > is the justification of keeping decoder as a client specific module and not > as a plugin to core module .
I think I can answer this. I think pathpartnertech mainly deals with TI and embedded systems where the CPU and the DSP / Video share memory. In this case you can run a hardware decoder and CPU on the same memory. Many systems separate the CPU memory and the display memory. This is the reason the decoder first goes to the UI. If you think about a PCI card with a RemoteFX decoder. If the decoding is done in the core, the compressed data has to be DMA'd into the card, decoded, then DMA'd back to system memory. Then when displayed, it has to DMA'd back into the card. Of course this does not make sense. By keeping the decoding in the UI, we have more efficient options available for all platforms. Jay ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
