(05-04-2016, 01:56 AM)Manilow Wrote: Thanks for all your information, which helped me a lot, to understand some more dependencies.
Great that you keep up. Normally if one comes up with information and suggestions quite the opposite happens here.
Regarding the issues: Can you please try out 'interactive' cpufreq governor and see if that helps also (if so for whatever reasons another governor must have been used by default that didn't increase clockspeeds when needed)?
Regarding 1200 MHz: If you have an hour please read through the whole story. In short words: If you know what you do you can increase that but we as the few people that looked into decided against since reliability would be concerned. Means: We stay at the default 1152 MHz (I've no idea why Pine64 has been advertised to be able to run at 1200 MHz, same applies to the promoted consumption and thermal values -- everything a bit or way off compared with reality)
Now to .dts modifications. I hope longsleep corrects if I'm (again) wrong: But it seems for these changes to take effect you would've to setup a cross compile environment, adjust .dts settings, create u-boot-with-dtb.bin and overwrite it on SD card as can be seen below:
https://github.com/longsleep/build-pine6...ther-parts
https://github.com/longsleep/build-pine6...ot_only.sh
I automated the whole process back in the days we tried to optimise cpufreq/dvfs settings and I doubt it's possible to deal in another way with this if you really have to test through a couple of different delay settings. But since longsleep reports pretty good throughput numbers (that are in sync with the numbers I get on H3 equipped Orange Pis also that share nearly the same driver code but use a different Fast Ethernet PHY) with the defaults I would suspect the real reason is somewhere else.