OpenELEC Testbuilds for RaspberryPi (Kodi 17.0)
(2016-03-07, 11:08)Saner Wrote: How can you test to make sure sdtweak is working?

If I use dtovetlay=mmc I can grep Overclock with sdtweak I get nothing by grepping overclock

The sdhost driver is the default now so if you have just "dtoverlay=sdtweak" or "dtoverlay=sdhost" in config.txt, they can be removed and you will be using the sdhost driver, not mmc.

If you have "dtoverlay=sdhost,overclock_50=xxx" then a better alternative would be "dtoverlay=sdtweak,overclock_50=xxx".

You won't see any referecnce to "overclock" in dmesg unless you are specifying an overclocked value for overclock_50.

If you execute "dmesg | grep mmc1" and see no results then you're using the mmc driver. If you see results similar to the following, then you're using the sdhost driver:
Code:
[    1.652834] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    1.654353] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.655842] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.658559] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    1.744430] mmc1: new high speed SDIO card at address 0001
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.


Messages In This Thread
RE: OpenELEC Testbuilds for RaspberryPi (Kodi 17.0) - by Milhouse - 2016-03-07, 18:41
RPI 3 no internet access on wifi - by b1m1 - 2016-03-09, 14:44
Logout Mark Read Team Forum Stats Members Help
OpenELEC Testbuilds for RaspberryPi (Kodi 17.0)6