11 replies to this topic

[scp]

I created a bsp for DM800 HD (dm800) for OpenPLi 3.0 based on files from OpenPLi 2.1 and OpenDreambox 2.0
With this files I am able to build a working image, tested on my dreambox.

oe-openpli-3.0-bsp-dm800.tar.gz contains the aditional files
oe-openpli-3.0-mod-dm800.tar.gz contains the modified files
oe-openpli-3.0-mod-dm800.patch contains a git diff of the modified files

There maybe still some changes in the structure required, also some source download links maybe broken. But I hope this makes it easier to integrate support for this model again.

Attached Files

•  oe-openpli-bsp-dm800.zip   242.19KB   19 downloads

[Erik Slagter]

And what exactly might a "bsp" be?

[scp]

A bsp is a "Board Support Package" which means it contains all files which are required for a specific model.
Currently OpenPLi 3.0 only supports dm800"se" and not the older model. With my package the older model also works.

Edited by scp, 21 June 2012 - 18:38.

[WanWizard]

With this you're able to run the closed source 2.6.18 drivers on a 3.x kernel?

[Erik Slagter]

Apparently that is not the issue, because we have OpenPLi for the dm8000 just as much and that also only features 2.6.18 kernel drivers.

[pieterg]

but the whole point is we want to get rid of all that old backward compatible stuff (external v4l-dvb, external wifi drivers, etc)

[scp]

The image for dm800 will be built with the Linux 2.6.18 Kernel, yes it has a bunch of "backward compatible stuff".
But I think it would be nice if OpenPLi still supports all Dreambox HD STBs in the upcoming build environment.
Maybe you can tag it as "legacy" or "unsupported" to state out that it has a lower priority.

The DM800 ist still a good peace of hardware with many useful features. And in combination with such a good image like OpenPLi is, its even better :-)

[littlesat]

But what is the problem when the DM800 stays on OpenPli2.1? It just results in a clean OpenPli3.0....

Edited by littlesat, 22 June 2012 - 06:39.

[scp]

If OpenPLi 2.1 will be maintained in future, even after OpenPLi 3.0 leaves alpha/beta stadium then it is OK for me.
But what is the advantage of keeping an older version of a full build system only for one model instead of transfering a handful of files to the new one?

As you can see above, I only had to modify 3 files of OpenPLi 3.0. The other files are additional, so they don't harm the build chain of the other STB models.

[littlesat]

3.0 is required to be able to continue compiling and building new stuff in future... That new stuff could not be proted to DM800HD and DM7025 due to the old kernel.... I guess...

[scp]

Yes, I understand that DM7025 is not part of the new Image anymore, because it may be a bit to much legacy. But I don't know much enough about this model.
But for DM800HD: OpenDreambox 2.0 also still supports it and the files above show, that it can be ported to OpenPLi 3.0 without much effort.

Edited by scp, 22 June 2012 - 17:34.

[scp]

Now I optimized the package a little bit, removed some patches and files which are not needed and using MACHINE_FEATURE kernel26-legacy instead of DREAMBOX_KERNEL_VERSION.
If it is still not intended to add it to GIT I will just keep it on my local GIT clone and see how it works with "new stuff in future".

By the way: Thank you all for working on OpenPLi, without your work the diversity of E2 STBs would not be possible like it is.

Attached Files

•  oe-openpli-bsp-dm800.zip   237.7KB   35 downloads