[Meego-tv] about qtmediahub on MeeGo(Mer)

[Dominig ar Foll (Intel OTC)]

> What do you mean by "You are stuck with directFB"?
I just say that because that is the only standard backend that will be
supported by exsiting software.
> hi3716m provides 2D hardware acceleration interface(a ko file named
> "tde.ko") and supports
That's nice, but that means that you will have to create your own
support for it. I do not know how much common that componant is and what
has already been done for it.
> DirectFB and HIGO graphics compoment. Both DirectFB and HIGO are based
> on tde.ko.
> So Maybe I can do 2D haredware with Xorg in three ways:
> (1) write "X backend" using tde.ko;
> (2) wirte "X backend" using DirectFB(maybe XDirectFB??)
> (3) write "X backend" using HIGO.
> Since I am not familiar with X, Can you give me some advice?
In reality the main issue with X in TV is the management of transparency
that we have accelerated on the
CExxx but that is specific to each SoC and the by pass by the DRI. In
the later the use of OpenGL is the norm. Does not mean that you cannot
do well with an other model, but you will have little liverage from
exisiting project.
> Maybe my understanding is completely wrong(Maybe on hi3716m, it is
> impossilbe to accelerate X...)...
The good and bad thing with SW, is that it's alway possible. It might be
expensive and painful.
>
> If we forget about X11, then we cannot build our OS over MeeGo(Mer) or
> Tizen, then our TVOS may regress to some kind of TV/STB middleware....
> that means the failure of our project...
>  (We have products running webkit based on directfb and we have a
> dedicated browser team.  So using directfb+sawman/elf will not be a
> big problem)
>
> Looking forward to you advice!
We will move one day (I hope quite soon) to Wayland. If I were you I
would look at doing the jump now.

-- Dominig