[MPlayer-dev-eng] Adding MAE-Au1200- support to MPlayer
bora.sahin at ttnet.net.tr
bora.sahin at ttnet.net.tr
Tue Nov 7 11:13:18 CET 2006
Merhaba,
In the previous mail, before finishing subject line, I just hit the send
button accidentally; sory for this...
> It makes definitly sense, especialy if you are CPU limited.
Yes, CPU(MIPS32) is limited. It has hardware mpeg decoding engine, which
supports some codecs like mpeg2, mpeg4, div-x, wmv... It has video decoding
capabilities but no hw audio decoding capability.
As far as I understood, the vendor supplied library roughly consist of two
parts.
- A kernel driver
- MAI engine(framework): file reader, demuxer/decrypt, decoder, renderer
The MAI components are connected by the multimedia engine in order to accept
media from an input source through the necessary decoders and output it to an
audio or video device.
> Depending on what codecs you want to decode you can
> either add the capabilities to the decoder itself
> (either mplayer internal or from ffmpeg/libavcodec)
> or you can use the same infrastructure as the
> dxr2/3 cards use (hardware mpeg decoder cards)
> that plug into the vo (video out) system.
> Maybe the best point to start would be to see
> whether the libvo/vo_dxr2.c resp libvo/vo_dxr3.c
> can be modified to use your SDK.
You suggest two methods. If I understand it correctly, the first method is
more complex and will replace MAI engine. The second method would try to use
MAI backend as is. In the light of above infos, is my understanding true?
> Something that you definitly also want to do is
> to later optimize the data transfere to your
> graphics card/video output device. This is together
> with the CPU the biggest bottleneck.
If I use the second method, is this needed? In the second method DMA is
already used by both MAE hw engine and LCD controller?
Thanks for your guidance...
--
Bora SAHIN
More information about the MPlayer-dev-eng
mailing list