1748 replies to this topic

[zakalibit]

file handle leak fix https://sourceforge....ge-requests/18/

[zakalibit]

another leak https://sourceforge....ge-requests/19/

[Persian Prince]

so i guess it's not about contribution anymore it's about wishes

sorry i won't do it again

Here we go again. GPL requires forkers to submit their patches, but it doesn't require the one being forked from to apply them.

we're not forking your OE , we have a local OE

 

i just sent you some updates that can help you for new changes , that's all

 

anyway it takes my time and i don't wanna do it again as i can see it's not about contribution it's about your exact wishes

 

good luck

[WanWizard]

Sorry, but it is not a democracy here. We run the OpenPLi project, so we get to say what is accepted and what not.

Tomorrow someone sends us a patch that filps the screen 90 degrees. Or put the subtitles upside-down. We should accept it no questions asked?

 

Your reaction is childish. If you work in Open Source, you should know that what you think is a good idea, might not be a good idea to others. For whatever reason.

So some suggestions are accepted, some not. Thats how it works.

[zakalibit]

https://sourceforge....ge-requests/20/

[littlesat]

@zakalibit,

Looks good...

[zakalibit]

Another one, mostly cosmetic, it has some performance improvement aspects, but I do not think that will be noticeable by users, but every little helps

https://sourceforge....ge-requests/21/

[Taykun345]

Nice one, keep it going!

Edited by Taykun345, 17 October 2013 - 16:55.

[zakalibit]

https://sourceforge....ge-requests/22/

[zakalibit]

Nice one, keep it going!

 This is the warm-up before a big one

[kocus37]

Hello, i´ve notice update driver from duo2 but no update from solo2 or is the same.

 

http://sourceforge.n...32d366df0098cf/

 

 

Update driver

20131023

 - Support DVB T2 Tuner(uno, ultimo, duo2)

 - Support file transcoding(solo2, duo2 : needs an image update)

 - Fix delivery system bug in vtuner

 - Fix DDP passthrough(solo2, duo2)

[littlesat]

As far I know we have these drivers already included....

[kocus37]

these is what i see in meta-openpli/recipes-bsp/vuplus/vuplus-dvb-modules-vusolo2.bb:

 

+SRCDATE = "20130916"

+SRC_URI[md5sum] = "e24b61ecdf984ebd05a5ac22d8123ee4"

+SRC_URI[sha256sum] = "fe404da08a4dc32cb2001137a33dccd3301165165874bab704e263ddc12eb29c"

 

but the last drivers at vu+ update is:

 

+SRCDATE = "20131023" 

+SRC_URI[md5sum] = "802c9ccfa0dad19f6ebd628e291854e1"

+SRC_URI[sha256sum] = "afa9c5efd55928d7af7ff835baff4ae6bc195cb3313fbdfce461b2b1f19fe0b9"

Edited by kocus37, 2 November 2013 - 19:28.

[athoik]

They are commited on upstream (== OpenPLi 4) branch.

http://sourceforge.n...32d366df0098cf/

[kocus37]

Hi athoik

 

but these drivers are only for vu+ duo2 i think.

see post 291

 

thanks athoik,littlesat

[athoik]

Yes it seems you are right. There is different file for solo2 and it is not updated yet.

http://sourceforge.n...ules-vusolo2.bb

[zakalibit]

Hi there

 

Can I have for your attention a bit bigger chunk of changes in the httpstream, current implementation suffers from few issues, one of them is that it does not do media packet filtration, so when the stream is choking or the network layer did receive a partial packet, that gets thrown away so you see the mosaic on the screen, as well there is no chunked transfer support that is in use at some iptv providers.

 

https://sourceforge....ge-requests/25/

 

regards

[pieterg]

I see a lot of cosmetic modifications, combined with some functional modifications?
(and a few whitespace errors btw)

[zakalibit]

yes there are few cosmetics, and functional modifications as well as minor performance changes like calling data() on a std::string instead of c_str() that null terminates the string, we can go though a code review if you wish. could you point me to whitespace errors?

[Erik Slagter]

I guess pieterg means the commits need to be split up.

 

If you're using git from the command line, you can do that using git reset to the commit you started, and then add separate, little commits using git commit -p, where you split up both cosmetic and non-cosmetic patches and also split up each added/changed functionality.

 

We never apply such a huge patch, because (a.o.) it can take ages to find an error introduced by such a patch, git bisect is useless then.