yea... really??Originally Posted by chemstar
![[0_o] is offline](images/statusicon/user-offline.png)
yea... really??
Confirm - dfb hdmi activation ... DONE !
:respect-067: :respect-069:
rgs,
Keep up the good work!
Now for the next step...
Regards
Juka
fb device activate ?
/dev/fb ?
whats all these threads about plz,sorry to be dumb
To see if we can get the title of the thread: Enigma 2 - AZBox HD
What means, a step forward for dvbapi?
i want to ask sthng clear and straight.i am not a programmer.i just know how to use linux and nothing else.
Will this progress lead to a stable firmware?
Will we have azbox behave normally like other receivers?
Shall i keep my azbox instead selling it now?
Directfb will allow us to play directfb apps. It will also allow us to use an alternative mediaplayer to see if it improves opensat's one.
Furtermore this means that finally someone found the right settings for hdmi, which means we can build the mrua library to build with hdmi support.
Chemstar thank you very much for achieving this. It has cost me some days without succeeding, so i am glad someone did!
no mambofb is used to activate that. However it has its limitations.
really cool.
i would like to see new firmwares with directFB.
Well i am not 100% sure but opensat seems to use a different set of mrua libraries (see file size). Maybe same version but with changes. Not sure if directfb will run on opensats libraries..?
Any can confirm this?
:( no fb no enigma2.
well mambofb can already been built and provides framebuffer. Major problem till now is still dvbapi.
Good thing about directfb is that we should now be able to also built mambofb with hdmi support
What is the difference and which app need DirectFB.
Why without /dev/fb no E2?
Does Dvbapi need /dev/fb access?
What is missing in order to access the /dev/fb device?
Sorry for all these silly questions, but I think it will help to novice like me to follow the discussion.
Thanks
directfb is needed to display the image on the screen "fast" without jumps
dvbapi is needed to acces the tuner through the api that is used in linux, with standard's one not the sigma's one
i will ask better what is the difference between mambofb and directfb?
From Wikipedia, the free encyclopedia
From Wikipedia, the free encyclopedia
DirectFB stands for Direct Frame Buffer. It is a software library for GNU/Linux/UNIX based operating
system with a small memory footprint that provides graphics acceleration, input device handling and abstraction layer, and integrated windowing system with support for translucent windows and multiple display layers on top of the Linux framebuffer without requiring any kernel modifications[2].
DirectFB is free software licensed under the terms of the LGPL (GNU Lesser General Public License).
The library allows developers an alternative to a full X Window System (X11) server used in Unix-like operating systems. DirectFB allows applications to talk directly to video hardware through a direct API, speeding up and simplifying graphic operations.
It is often used by games and [COLOR="Dar*****ge"]embedded systems developers [/COLOR]to cir***vent the overhead of a full X Window
System server implementation. In 2006, a version of DirectFB was included in the software stack
for the CE Linux Forum's Audio/Video Graphics Specification V2. [3]
DirectFB can host XDirectFB, a rootless X server implementation that uses DirectFB windows for X11 top-level windows. XDirectFB is an interface that mimics the X11 interface through the DirectFB API to simplify running applications written for X11 on DirectFB.
DirectFBGL is an OpenGL extension for DirectFB/XDirectFB that uses DRI (Direct Rendering Infrastructure) in the Mesa 3D library to support OpenGL hardware acceleration.
Among the products that use DirectFB are LinuxTV, the unreleased Palm Foleo mobile companion and the webOS operating system.
:respect-055:
So to place everything together:
Sigma has it own library to display stuff on the screen (mrua/ehmlib) You can find this in the mrua samples. They directly talk to the hardware through mrua. This is great for video playback.
Mambofb:
To support displaying menus etc they have first build mambofb. Which emulates a framebuffer device --> like there is on most linux machines. Coding can be done according to famebuffer, and mambofb translates this to sigma/mrua language.
Directfb
As the normal frambuffer emulator was not good enough. And had no ability to display a very nice pictures with different layers directfb was developped. Normally this would be installed on top of the normal framebuffer. However with sigma (as far as I get it) they compiled directfb in such a way that it speaks directly to the sigma hardware (ehmlib).
Enigma is build on top of the normal framebuffer, in this case mambofb. The problem is that this is limited (according to some coders). Maybe they can work around. Enigma is not build on directfb. However some plugins use directfb to display picture.
The compilation of directfb for azbox lets us use directfb plugins from the popcornhour. Accessing the hdmi hardware also enables us to use sigma sample applications included with mrua (like video player, asf streamer) to the full extent. The sigma directfb package also includes sample code for another mediaplayer which could support perfect dvd menu and possibly BD-menu. BD menu however needs a lot of ram, and I am not sure wether this will be supported on the AZ.
For fb on azbox , it is under fb4 in /dev
rm -rf fb0
ln -s fb4 fb0
I can also confirm HDMI init, activation and play of dfb test by HDMI is now ok.
Some pictures....
Last edited by HighHD; 09-04-2010 at 11:46 AM.
@kanber_kav
Check qbox Enigma2 Source Repository, they use DFB.
Posting Permissions
Reply With Quote
Bookmarks