Thread Closed
OpenELEC Testbuilds for RaspberryPi (Kodi 16.0)
New OpenELEC Jarvis build #0812: RPi / RPi2
(Supercedes previous build)

Code:
# uname -a
Linux rpi512 4.1.4 #1 Thu Aug 13 01:08:47 BST 2015 armv6l GNU/Linux

# vcgencmd version
Aug 13 2015 00:10:56
Copyright (c) 2012 Broadcom
version 2fe75164bde8530ab8e9c384cc0fa4723757ddfa (clean) (release)

# lsb_release
OpenELEC (Milhouse) - Version: devel-20150813010757-#0812-gcac5a18 [Build #0812]

# vcdbg log msg 2>&1 | grep DTOK
001558.313: Kernel trailer DTOK property says yes

# Kernel device tree status: Enabled

Based on tip of OpenELEC master (cac5a18a, changelog) and tip of XBMC master (71e6731b, changelog) with the following modifications: Build Highlights:
  1. New firmware with GPU frequency boost to 300Mhz (+50Mhz over stock) when required - disable with "disable_auto_turbo=1" in config.txt
    popcornmix Wrote:This will give a gpu turbo boost to 300MHz when HD advanced deinterlace, HD MVC, or HD high framerate (> 45 fps) content is played.

    This will occur automatically without any config.txt settings needed.

    ...

    The logic is complicated.

    Basically for deinterlace v3d will be bumped to 300MHz, but due to PLL dependency all related clocks will be bumped (core, h264, isp by default, just h264 and isp if using avoid_pwm_pll). For the video decode h264 will be bumped (and dependent clocks will be bumped too).

    Now if you have your own gpu overclock settings things get more complicated. Each clock will be set to the max of user (e.g. h264_freq) and auto (call it h264_boost = 300). So if you have a big overclock on all gpu clocks, then the auto boost will have no effect (apart from enabling turbo at suitable times).

    If you have a partial gpu overclock (e.g. core_freq=500 and h264_freq=250), then it gets more complicated. The core_freq will get 500MHz, which gives a PLL of 2GHz, which means 300MHz is not possible, so h264 will be left at 250MHz. If core_freq was 400MHz, which gives a PLL of 2.4GHz, then 300MHz is possible, so h264 will be boosted to 300MHz.

    So, I think you will never be worse off than before, but some user overclocks may have the effect of disabling the auto boost frequency.
Build Details:
  1. Firmware (Aug 13):
    • firmware: arm_loader: Force turbo changes to first core. Changing sdram isn't safe from second core. See: link
    • firmware: arm_loader: Move the application of user parameters and overlays later. See: link
    • firmware: rtos: Remove breakpoint in zero exception handler
    • firmware: arm_loader: Fix some sanity asserts
    • firmware: di_adv: Update to use chained shaders with larger VPM DMA
    • firmware: arm_loader: Allow temporary gpu frequency boosts to be requested
    • firmware: video_decode: Request boost to 300MHz when playing HD MVC or HD high framerate video
    • firmware: di_adv: Request boost to 300MHz when doing full rate HD advanced deinterlace
    • firmware: arm_loader: Allow auto turbo to be disabled in config with disable_auto_turbo
    • firmware: dma_lib: Allow burst, waits and priority to be specified for 2d dma memcpy
  2. XBMC:
    • [infomanager] add Container(id).CurrentItem / NumItems for grouplists (PR:7768, 1 commit, 3 files changed)
    • [infomanager] add System.HasModalDialog info bool (PR:7776, 1 commit, 2 files changed)
    • [coverity] Add an additional check to prevent an only theoretical out-of… (PR:7724, 1 commit, 1 file changed)
    • cleanup ui sound system (PR:7684, 1 commit, 6 files changed)
    • [guilib] add Container(id).HasNext / HasPrevious for textbox controls (PR:7769, 2 commits, 3 files changed)
    • [gui] new ACTION_MENU key to focus sidebar menu (PR:3885, 3 commits, 21 files changed)
    • [setting] hunt missing setting id constants (PR:7790, 2 commits, 19 files changed)
  3. pvr.hts:
    • Improve connection handling on suspend/wakeup. (PR:90, 1 commit, 4 files changed)
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
  Thread Closed
 
Thread Rating:
  • 10 Vote(s) - 5 Average


Messages In This Thread
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - by Milhouse - 2015-08-13, 03:24
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