I have a few basic questions, i'm sure you will help me:
What's the HEAD branch? What's the relation between the CDK CVS HEAD, and the PC "Technotrend" DVB linux HEAD driver? The same API? Is this 'HEAD' run on a DreamBox? Is the VDR software runs on a Dreambox?
Finally I successfully compiled the CDK under i386 Linux. I got a 550MB stuff under dbox2/cdkroot. What should I do? Upload to the Dreambox's HD? How can I boot this kernel and use these applications?
first, there were dvb-drivers from convergence. We used their API and made drivers for the dbox2.
dream multimedia made drivers for the dreambox, compatible to that api.
Then there was NEWSTRUCT, a branch in convergence's CVS with a new api. NEWSTRUCT finally became HEAD (i.e., the main version, not just a branch). at that point, the dbox2/dreambox was incompatible to the main branch on the PC.
So there were attempts to rewrite the dbox2 drivers to HEAD, but since this was much work, we created a branch called "rel_1_0_0", which uses still the old api.
so:
- PCs normally use the new api ("v3")
- dbox2 in the HEAD branch uses the new api, too
- dbox2 in the rel_1_0_0-branch uses the old api
- the dreambox, at least the public images, use the old api, too, and is thus (application binary) compatible to the dbox2 in the rel_1_0_0-branch.
(there are dreambox-v3 drivers in the development but they are not finished nor actively developed)
so if you want to develop for the dreambox, checkout the rel_1_0_0-branch. Enigma is developed in this branch, since the dreambox still uses this api (and we don't want to change this yet because of stability reasons). enigma-HEAD is most probably older than enigma-rel (yes).
compile the cdk, and you get a cdkroot, which is very big. The best thing for developing is to use nfs booting. replace the dbox2 drivers and the kernel by the dreambox kernel and drivers, and boot via network (bootp/nfs)
there are surely some FAQs about that...
so, the only thing for the dreambox NOT contained in the tuxbox cvs is the kernel and the drivers. both are available (the kernel as a kernel-patch, the drivers binary only) from dream multimedia tv.
you CAN use a normal dreambox image, and just copy your (new) apps to the hdd, and start them from there, assuming that the right libraries are available.
but for developing, nfs boot is your choice.
at the end you can produce an image out of the stuff.
Many thanx for the answers, especially about the API informations. I know the old convergence's API and the HEAD (v3) too in PC. That means for me, that I can use (compile) softwares which made for the old API in the PC world.
But it's also means that the newer applications (which has source at tuxbox.berlios.de) cannot compile for dreambox. (for example vdr)
Is this true?
Finally I compiled the whole CVS (rel_1_0_0 branch) and I got the cdkroot, which is really big (about 550MB). Strange for me, there are binaries (statically linked?) which are very big, for example, the 'enigma' binary file is about 50MB. Why? And how can I make a little (max. 8 MB for the dreambox Flash) from this?
Is there a make option for this?
And finally a question: how can I compile stuffz for dreambox, which are not in the CVS. (for example an iptraf, or midnight commander or other things)
I compiled the dvbtune for dreambox with cdk. Won't work, because cannot open demuxer (FD: demux error like error message). I noticed, that dvbtune compiles with NEWSTRUCT definition (i cvs downloaded the rel_1_0_0 branch, which is for API2, and not NEWSTRUCT). If i comment out NEWSTRUCT definition it won't compile (for the older API). So I use now newer API? I don't know how to check. Is it possible to compile dvbtune and use dreambox's DVB interface like a network interface, to catch DVB/IP packets? (dvbtune can do it, but I can't compile and run a dvbtune for dreambox )
I don't understand something. The rel_1_0_0 branch uses the old API, is it?
When i downloaded the cvs there's a dvbtune tar.gz contains sources which are default compiled for NEWSTRUCT. So, it's look strange. I can compile it with CDK (another strange thing, as I see, in the rel_1_0_0 cdk there are the includes for DVB driver API v3 not for v2 - (ost/*.h)) but I can't use that binary on dreambox (cannot open demuxer) which is looks OK, I compiled for NEWSTRUCT so doesn't work with the dreambox driver. OK, but I can't compile dvbtune sources for API v2 with CDK, because CDK rel 1_0_0 doesn't contain the ost/*.h (API v2) header files.
I tried a lot of trick to compile and run dvbtune on DreamBox, but without any success.
And i don't understand something. You told me, that Dreambox (DM DVB driver) supports DVB API V2. As I know, this API uses /dev/ost/* devices. And the newer (NEWSTRUCT) uses /dev/dvb/* devices. But I have a /dev/ost/demux0 device (only this!) on my Dreambox and some device files on the /dev/dvb/ directory. What's this?
Of course if i compile dvbtune for oldstruct it cannot open network devices. (/dev/ost/network0 or something like this as i remember).
So how does it work? Is it possible to open a network device on Dreambox with dvbtune? Or some other way?
