Opened 11 years ago
Closed 11 years ago
#2381 closed defect (invalid)
Port the VU+ fix to 1.10
| Reported by: | kess78 | Owned by: | |
|---|---|---|---|
| Priority: | minor | Component: | General |
| Severity: | low | Keywords: | |
| Cc: | Sensitive: | no |
Description
Hello guys, could you please port the VU+ fix from 1.20 to the stable release ?
1.10 stops working after a while on VU+ Uno, while 1.20 seems to work...
Thx a lot.
Bye K
Change History (2)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Dear Admin,
thank you for your polite and well explained reply. I didn't know about all of these radical changes, unfortunately I'm not a programmer.
I'll try to find another solution for doing everything needed.
Thank you a lot, bye K
Note:
See TracTickets
for help on using tickets.
The error that was fixed in 1.20 was a problem which only existed in this branch starting from a specific revision. It was a patch that can't be ported because the structure is completely different and the fixed code parts aren't even there. Vu+ Duo users wrote, that previous revisions and 1.10 worked. So you are probably experiencing something completely different; maybe it is some kind of driver/image problem. The only thing I currently know of is some dvbapi problem with some VTI images which does not exist on PLI images - but that's on all OSCam revisions including 1.20 as far as I read.
Unfortunately, we can't actively maintain two branches so you'll have to stick to 1.20 branch.