Thread Closed
OpenELEC Testbuilds for RaspberryPi (Kodi 16.0)
(2015-07-24, 12:06)popcornmix Wrote: In general you can update to a new milhouse and then replace the firmware.
Very occasionally there may be a new firmware feature that kodi relies on, or a bug fix that you would benefit from.
In that case, let me know and I can build a new firmware with the patch reverted.

Deborah is off for health reasons. I hope she will be back, but we have no definite date.
I will have a close look at the patch to see if I can find a way of fixing it for these files, but I'm not certain if that will be successful.
The other possibility is to revert it for everyone, but that may cause regressions elsewhere (possibly with MVC which is when the patch was added).
If I can't find any regressions with my test files, I may revert it for testing purposes and see if any problems emerge.

ok thanks. wanted only to know, if there are already plans for changes, that would cause the firmware stop working with newer builds.
but if you can build then a new one, its ok.

Can you tell me where the commit is or which files where changed by this? I would like to take a look at it, simply because i am interested. have been c++ developer in my previous job.

I looked a bit at the more detailled component log and at the kodi source. CMMALVideo::m_output_ready is empty. So the dec_input and dec_output callbacks get never called again.
You said the commit is a change with "userdata". As i can see this is passed to the callbacks.
  Thread Closed
 
Thread Rating:
  • 10 Vote(s) - 5 Average


Messages In This Thread
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - by michidg - 2015-07-24, 15:03
Bluetooth on #1003 - by cdvreede - 2015-10-13, 11:08
Re: RE: Bluetooth on #1003 - by Milhouse - 2015-10-13, 13:24


Logout Mark Read Team Forum Stats Members Help
OpenELEC Testbuilds for RaspberryPi (Kodi 16.0)510