8 replies to this topic

[Jomu]

First, disclaimer... I am rather new to "dreambox scene" and I have an exotic problem/need/wish...

My intent is to make non-TV related setup and for it I need newer kernel and few packages not present in default distribution. Also, some packages (like dvbsnoop, dvbnet) are present in source tree, looks like they are built, but when I flash my DM500s they are nowhere to be seen. Even as I make them "by hand" with "make .dvbsnoop" (for example) prior to ./make_cdk_image...

I know there is some voodoo I don't know - yet. Can somebody shed some light for me here? How can I upgrade this source tree to newer kernel (I need some ioctls and it looks they are not present, and I probably need newer DVB API...)

Thanks in advance.

[hemispherical1]

DMM never released the source for the drivers required to run the DB, that's the main reason why all the boxes were using ancient (6+ year old) kernels up until fairly recently. (If not somebody would've updated the kernels themselves.) Finally DMM updated the kernels on most of the newer boxes, but all the E1 boxes and even the 800 are still tied to ancient kernels.

Unfortunately that means when a needed feature finally appeared in a new kernel, the only real option is to attempt to backport it to the ancient kernels, with varying degrees of success.

--
hemi

[dAF2000]

And about dvbsnoop etc. :

I never compiled them and I wouldn't know if they really work. If you do a make .dvbsnoop you will find it in the directory "cdkroot". I think that directory is in cdk/root but I'm not sure. The directory "cdkflash" contains all the binaries which will be in the image and that one doesn't have the dvbsnoop binary.

[Jomu]

DMM never released the source for the drivers required to run the DB, that's the main reason why all the boxes were using ancient (6+ year old) kernels up until fairly recently. (If not somebody would've updated the kernels themselves.) Finally DMM updated the kernels on most of the newer boxes, but all the E1 boxes and even the 800 are still tied to ancient kernels.

Unfortunately that means when a needed feature finally appeared in a new kernel, the only real option is to attempt to backport it to the ancient kernels, with varying degrees of success.

With hardware widely cloned, schemes available and datasheets everywhere... And years gone... I am puzzled to see any driver not reverse engineered till now...

What devices/drivers are closed/specific? I am not a kernel hacker, but it would be nice to take a look.

Another question, what does dm500-chinese build path does/has over/compared to only dm500?

And about dvbsnoop etc. :

I never compiled them and I wouldn't know if they really work. If you do a make .dvbsnoop you will find it in the directory "cdkroot". I think that directory is in cdk/root but I'm not sure. The directory "cdkflash" contains all the binaries which will be in the image and that one doesn't have the dvbsnoop binary.

So, root/cdkroot is "buildroot" only and that is why binaries there are not stripped? And also why being there does not mean it is in flash? Some step strips binaries/copies to root/cdkflash...

Thank you for answers. I know more now .

[WanWizard]

The DM500-chinese version builts with chinese fonts, it's not an image for "chinese made clones"... It's a separate image due to size restrictions. Other then that there's no difference.

[Jomu]

The DM500-chinese version builts with chinese fonts, it's not an image for "chinese made clones"... It's a separate image due to size restrictions. Other then that there's no difference.

Thanks, good to know I am not missing anything there .

Where can I find cdkflash populate policy/code? For the moment I am lost in generated Makefile, it looks like at one step $(flashprefix)/root is removed, at next step basic /lib is created, and somehow at next step Makefile starts stripping installed binaries in $(flashprefix)/root/bin... No idea how these binaries got there...

Edited by Jomu, 17 September 2012 - 08:26.

[dAF2000]

The target "flash-dvbsnoop" (in case of dvbsnoop) is not build for dreamboximage_root. Check cdk/Makefile.am around line 2256. So, if you add flash-dvbsnoop to that target, it will copied from cdkroot to cdkflash.

[Jomu]

The target "flash-dvbsnoop" (in case of dvbsnoop) is not build for dreamboximage_root. Check cdk/Makefile.am around line 2256. So, if you add flash-dvbsnoop to that target, it will copied from cdkroot to cdkflash.

I've found this and few others...

Is there a reason for dvbnet to be disabled for targets other than DM7000? Does it work for dm500?

It looks like flash-dvbsnoop is not enough. I've added .dvbsnoop and make is working right now.

[dAF2000]

Is there a reason for dvbnet to be disabled for targets other than DM7000? Does it work for dm500?

I have no idea. It was a long time since I programmed for these boxes. I assume those programs were never in the build because they are not needed for "normal" use.