[MPlayer-dev-eng] Adding MAE-Au1200- support to MPlayer

[bora.sahin at ttnet.net.tr]

Merhaba,

> Please do not CC people on this list.

Sory, I did it because of convention...

> > 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.
>
> Sounds like a standard framework.

Yes...

> > 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?
>
> Yes, replacing a decoder completely is more complicated
> than just writing a new vo module. But it might be worth
> the effort depending on what you want to acheive.

What's the reasons which justify those efforts? Doing it at the decoder level 
is more stable? If possible, can you supply more details?

> But it will not replace the MAI engine, it will make
> use of it. Ie you pick out the modules of the MAI engine
> what you need to feed the decoder and leave the rest
> to mplayer/ffmpeg.

I see...

> > > 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?
>
> It depends on how the data is transfered from the
> decoder hardware to the display hardware.

If I recall correctly, it is transferred via DMA.

--
Bora SAHIN