OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Raspberry Pi (https://forum.kodi.tv/forumdisplay.php?fid=166) +---- Thread: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 (/showthread.php?tid=224025) |
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - popcornmix - 2015-05-30 (2015-05-30, 13:23)HiassofT Wrote: My understanding is that the old spi-bcm2708 should eventually go away (and CONFIG_SPI_BCM2708 can be disabled) but I think it's best to have both available for now in case something doesn't work fine with spi-bcm2835. Correct. Where possible we are switching to the upstream drivers (like spi-bcm2835) and deprecating the drivers from Pi tree (spi-bcm2708). So CONFIG_SPI_BCM2835=m is correct for now. Leave CONFIG_SPI_BCM2708=m in for now in case people have difficulties with the upstream driver, but that will eventually be removed. Assuming this build works okay, then official OE build should also enable CONFIG_SPI_BCM2835. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - Milhouse - 2015-05-30 Thanks both. Not really sure why SPI is being built in-kernel rather than as modules, is it worth testing SPI as modules (I can upload a new test build - let me know if you need RPi or RPi2 so I don't waste bandwidth on a build nobody needs). RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - popcornmix - 2015-05-30 (2015-05-30, 13:31)Milhouse Wrote: Thanks both. Not really sure why SPI is being built in-kernel rather than as modules, is it worth testing SPI as modules (I can upload a new test build - let me know if you need RPi or RPi2 so I don't waste bandwidth on a build nobody needs). We use modules (=m) on raspbian and most people don't need SPI, so I'd say building as modules makes more sense. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - fab67 - 2015-05-30 About H.264 10bit files ( animes ) . we can't use existing hardware acceleration and software is sometimes to slow for decoding 720p. Is it (in theory) possible to do something with the VPU/GPU/Shaders.... optimizations like that what we see for HEVC ? or is it a definitive problem with 10bit ? RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - HiassofT - 2015-05-30 No idea either why SPI is built into the kernel in OpenELEC. I also think having both SPI drivers built as modules makes more sense and IMHO that should be safe. The last 2 days I did various tests with my cirrus OpenELEC build having SPI drivers built as modules and haven't noticed any issues. Just did another test with the cirrus dtoverlay removed from config.txt so it's very near to your build: With dtparam=spi=on /dev/spidev0.{0,1} show up fine and lsmod/dmesg show that the new driver is used Code: OpenELEC:~ # lsmod | grep spi When also adding dtoverlay=spi-bcm2708 to use the old driver the device nodes show up fine again and lsmod/dmesg output is also as expected Code: OpenELEC:~ # lsmod | grep -i spi I think you should be safe switching to modules in you next regular testbuild, don't think we'll need another intermediate build. so long, Hias RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - Milhouse - 2015-05-30 Thanks @HiassofT, I'm seeing the same lsmod/dmesg results when building SPI as modules so that all looks fine - I'll keep it this way for future builds. I did however have to enable CONFIG_BCM2708_POWER=y when building CONFIG_SPI_BCM2835=m and CONFIG_SPI_BCM2708=m - if I used CONFIG_BCM2708_POWER=m, the Pi/Pi2 wouldn't boot successfully. Assuming all is well over the next few days then I'll submit a pull request to build SPI as modules for RPi/RPi2. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - Forage - 2015-05-30 (2015-05-13, 03:46)Milhouse Wrote:Love it! (yeah, it's been a while since I've updated ) Just how does one add/try others? Can it be done without compiling? I love the following stuff in case you are still looking for improving the list:
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - HiassofT - 2015-05-30 (2015-05-30, 14:42)Milhouse Wrote: I did however have to enable CONFIG_BCM2708_POWER=y when building CONFIG_SPI_BCM2835=m and CONFIG_SPI_BCM2708=m - if I used CONFIG_BCM2708_POWER=m, the Pi/Pi2 wouldn't boot successfully.Ah, sorry, I totally forgot about the power option. I had SPI set to modules before and enabled BCM2708_POWER=Y yesterday evening, as a consequence of kernel PR#980 - Kconfig has it as "default y". Quote:Assuming all is well over the next few days then I'll submit a pull request to build SPI as modules for RPi/RPi2.OpenELEC master hasn't updated the RPi kernel patch in quite a long time and some of the stuff like new power option or the need for the mailbox driver came after that. I think it might be best to submit a PR with the updated kernel patch and linux.arm.confs. Here's the full config diff (minus the cirrus changes) I'm using in my build - it's in line with your config except I haven't enabled BCM_VC_SM Code: diff --git a/projects/RPi/linux/linux.arm.conf b/projects/RPi/linux/linux.arm.conf so long & thanks for your great work! Hias RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - Milhouse - 2015-05-30 (2015-05-30, 15:31)HiassofT Wrote: Ah, sorry, I totally forgot about the power option. I had SPI set to modules before and enabled BCM2708_POWER=Y yesterday evening, as a consequence of kernel PR#980 - Kconfig has it as "default y". Thanks for that, so it looks like we also need an updated mkknlimg script. It's probably easiest for @sraue etc. to integrate the extra config options when they move to the latest kernel patches. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - popcornmix - 2015-05-30 (2015-05-30, 14:57)Forage Wrote: Love it! (yeah, it's been a while since I've updated ) Are you talking about visualisations or screensavers? None of the shadertoy links you gave were for visualisations (you want shaders with an audio input like this for visualisations). In theory you can just edit the glsl file (e.g. /usr/share/kodi/addons/visualization.shadertoy/resources/silexarst.frag.glsl) and the visualisation/screensaver will update on next use (even without relaunching kodi). But, as OpenELEC is readonly, you will have to copy it somewhere writable. E.g. Code: cp -a /usr/share/kodi/addons/screensaver.shadertoy /storage/.kodi/addons/ You'll need to change the id of the new addon. Change: id="screensaver.shadertoy" to id="screensaver.shadertoy" name="ShaderToy" to name="ShaderToy2" Restart kodi (e.g. systemctl restart kodi) and you should see ShaderToy in list of screensavers. Now you can edit, e.g. Code: nano .kodi/addons/screensaver.shadertoy/resources/silexarst.frag.glsl Try changing "p-=.5;" to "p-=.25;" and you should see a less centred version of the effect. (all this applies to visualisations too - just change the path). Note: on Pi1/Pi2 you can handle about 1000 cycles worth of work per pixel and have a decent framerate. Complex operations like sin/cos/sqrt will take dozens of cycles. Shaders that have loops with high iterations are likely to struggle. From your list the first one is probably out (loop of 40, then several calls to complex operations inside that loop). The others look more plausible. Also, the textures used by shaders are in the code so needs recompiling to change. If shader doesn't use textures (many don't - look at the iChannel0, iChannel1, iChannel2, iChannel3 below the shader code on shadertoy site) then no problem. If it does then modify a shader that uses a similar texture (often the exact texture isn't critical). RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - Milhouse - 2015-05-30 New OpenELEC Isengard build #0530: RPi / RPi2 (Supercedes previous build) Code: # uname -a Based on tip of OpenELEC master (78ad7dc6, changelog) and tip of XBMC master (fa2bd087, changelog) with the following modifications:
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - OurJermain - 2015-05-31 Thank God they fixed 15995: Unsoliticed demuxer seek at the beginning of video playback (PR:7202) It was driving me nuts. Thank you RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - Milhouse - 2015-05-31 (2015-05-30, 17:17)popcornmix Wrote: But, as OpenELEC is readonly, you will have to copy it somewhere writable. E.g. Longer term, both the visualizer and screensaver will hopefully become binary addons that are downloaded and installed by the user, which will make modifying the Shadertoys that bit easier (not to mention significantly reducing the size of the OpenELEC SYSTEM file) . But for now, you'll need to copy the existing addons. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - illiac4 - 2015-05-31 On rpi v1 there is always warning for under voltage shown in latest version. RE: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2 - MrNice - 2015-05-31 Hi Milhouse Hi popcornmix I run the last testbuild #0529 OpenELEC-RPi.arm-6.0-Milhouse-20150530210144-#0530-g78ad7dc Regarding the bug "Audio Dropout playing HD multichannel music", I still have hdmi_mai_thresh=0x1412 in config.txt to fix it. Do I need to keep it? Thanks |