Thanks for your update.
my apps is not using any sigma stuff, all i need is a working fbdirect (best HW accelerated) and a mediaplayer, which can be called by command line.
Does this mean, that there is no directfb in enigma. Thought there is some!
Is the compiler available somewhere for download?
Originally Posted by The_Ripper
The_Ripper Hello I'm happy for your great work you are doing I have a question to make it with a HDD instead of a Dom firmware installed on the decoder like me who is an Elite would AzboxHD ability to record directly into it and not have to be putting a usb. Because the original firmware partition like a Sun and not the hard disk partition or it does not record anything you always said No valid recording device.
@thica
Like I said there will be no DirectFB(DccHD package from Sigma) for E2 on smp8634 chip because their libs are compiled against Uclibc and not Glibc.
On new chips from Sigma it's possible because their SDK libs are based/compiled for Glibc usage and not like on smp8634 chip for Uclibc.
Regarding compiler ,download Makefile-opendreambox-1.5 and compile OE for dm800, you will have full compiler and rootfs we are using for E2 Azbox currently.
@bawin
If I understand you , you want possibility to install E2 on HDD and not on internal DOM ?
Would that mean that SMP8655/54 boxes would be easier to make E2 for? I have seen that there is a He@d that uses this CPU, and that CPU shuold be 1,5 X faster also. Is there big difference to make SW for this CPU?
Best regards!
DOM right now I do not take it out because I have him as eh ide to sata adapter and a 160GB HDD Internal 2.5 eh you install the firmware and it works very well the problem that you can not record on the HDD as the firmware automatically partition you need a USB to record as I have understood you need to make a link from any two USB devices to record to HDD installed my question that would happen in the Enigma2.
Here the partitions that makes me the original firmware on the 160GB HDD 2.5.
AZBox[~]$ df -k|grep hd
/dev/hda1 139999 112711 20059 85% /MMP
/dev/hda2 23332 9146 12982 41% /PLUGINS
/dev/hda3 15553 3671 11079 25% /DISK2
/dev/hda4 153654248 82744 145766324 0% /Download
AZBox[~]$
What this means to record directly to the Internal HDD installed without the need for USB.
Last edited by bawin; 21-08-2010 at 04:30 PM.
@digihoe
I dont have access to 865x do***entations/SDK so I dont know whats difference in API if any regarding old chips/new chps, but MRUA libs for new chips are compiled against Glibc, so it will be easy to use MRUA libs in any based glibc rootfs(that include OE and E2).
@bawin
It should be no problem recording to internal HDD even it's acting as replaced DOM, but to be clear till I finish demux/tuners part and test we will not know.
Are you making progress on these drivers? as was said that it might be very difficult to get the demux and video output dvbapi compliant?
Thnx
@sattommy
Audio driver is finished, and it's DVB API compilant for most parts or better to say it handle allmost all IOCTL calls it should, but I added few more IOCTL calls to Audio DVB API so applications that will use "audio" can send all necessary infos regarding audio data so I can set required Codec for Sigma HW decoding.
Video driver is on the way, still coding it, so it should be soon finished. Like in audio , video DVB API will be expanded too.
For demux/tuners till I get there I will know, right now I dont have any problems or obstacles regarding the code I finished for DVB driver.
Ok this sound perfect. This would mean that we are not dependent any more on rua libs? For example for a movieplayer they can send audio/video over your kernel modules which will pass things to sigma HW decoding?
Thank you very much for all of your hard work.
@sattomy
Yes I communicate over low level API with Sigma chip and not over MRUA libs.Ok this sound perfect. This would mean that we are not dependent any more on rua libs?
Movieplayer just need to open audio0/video0 path, send infos regarding what audio/video codec is used in file that needs to be played, set up other stuff over ioctl call and thats all. Ofcourse application must demuxing file and send RAW datas to audio/video driver.For example for a movieplayer they can send audio/video over your kernel modules which will pass things to sigma HW decoding?
Regarding the Video decoding,I would like to remind you that some feeds we can see can be MPEG2 HD 4:2:2,and would be great to keep getting them.
The reason I am posting is because you might not have any such feed available in order to set correct video decoding parameters,and in such case,some of us can provide you with samples.
Let us know.
Thank you for all your work and info. Would it be possible to release image with audio and vidio drivers when they are finished, before you start working on demux/tuners? Or maybe just the kernel modules which we can use with the old install. This way maybe someone can already start developping music/video player executables
This is sounding great, I think
Keep the great work my friend!
It may put a USB-TDT2 in our azboxhd because they have two tuners such as I of (dvb-s2 and dvb-c2) in the decoder to have the dvb-usb tdt2 by the three tuners also have in the decoder.
@sattommy
Yes it's plan, when I finish video part and E2/Python code is adjusted, to release new test, now with better protection for upgrading back to original FW. Last time my kernel didnt have RAM disk rootfs, now it has, etc ...
@bawin
On Elite/Premium model, 2 tuners cant work in same time, regarding of the type S/S2/C/T
Premium+ is different case ...
@kebien
Can you upload few seconds/minutes of MPEG2 HD 4:2:2 stream somewhere.
Thx.
@The_Ripper
When do you think that will be ready the tuner/demux part??
And all emus will work well like in dream without any patch??
I know because I is that I have two tuners and a dvb-s2 dvb-c2 and the decoder to put third tuner to a USB port TDT.
And so have all three tuners in the decoder.
Here is a short file with 4:2:2 and 720p.
Posting Permissions
Reply With Quote
Bookmarks