Hi.
I just got involved into this theme in vdr-portal.de. Since then i have an idea how to proceed.
To make sure you can prove if i understood it right here is what i assume about the surrounding conditions:
- "HCW_COMPATIBLE_VERSION and HCW_BUILD_VERSION in the kernel patch file" determine the versioning *only* in vompclient's dongle.bin.
- dongle.bin.ver is created after installation from dongle.bin.
- the versioning in dongle.bin.ver ist just a means to force the OS of MediaMVP to load dongle.bin.
If the above is true we should avoid mixing up problems. Let HCW_COMPATIBLE_VERSION and HCW_BUILD_VERSION in the kernel patch file be dedicated to whatever they are now. Maybe vompclient needs to know it's own version number perhaps at least to display it?
Doing so reduces the problem on how to built a usable dongle.bin.ver. This could be done be the attached script. (Cross-posted in vdr-portal.de.) I hope it will prove to be usable for everybody.
Have fun
ekluba.
I just got involved into this theme in vdr-portal.de. Since then i have an idea how to proceed.
To make sure you can prove if i understood it right here is what i assume about the surrounding conditions:
- "HCW_COMPATIBLE_VERSION and HCW_BUILD_VERSION in the kernel patch file" determine the versioning *only* in vompclient's dongle.bin.
- dongle.bin.ver is created after installation from dongle.bin.
- the versioning in dongle.bin.ver ist just a means to force the OS of MediaMVP to load dongle.bin.
If the above is true we should avoid mixing up problems. Let HCW_COMPATIBLE_VERSION and HCW_BUILD_VERSION in the kernel patch file be dedicated to whatever they are now. Maybe vompclient needs to know it's own version number perhaps at least to display it?
Doing so reduces the problem on how to built a usable dongle.bin.ver. This could be done be the attached script. (Cross-posted in vdr-portal.de.) I hope it will prove to be usable for everybody.
Have fun
ekluba.