09:19 <npl> Hoi

09:20 <npl> Really weird question, I get max CPU Speed 1608MHz for Firefly RK3288. Is this a known issue?

09:22 <npl> Both Kernel 4.7.2 and 4.8rc2 show this. I found some reference to SAFETY_FREQ on the web

09:23 <mmind00> npl: why is that wired? The generic operating points in rk3288 do end at that frequency

09:24 <npl> It should be 1800, or not? Its advertised as such at least

09:24 <mmind00> npl: they were specified as safe for all use cases ... so everything else would be on a per-board basis

09:25 <mmind00> npl: i.e. Chromebooks do go higher (not yet in mainline devicetrees), but of course were extensively tested to not overheat there

09:39 <npl> I had my Board overheating and continously rebooting just yesterday, but the Firefly Board is advertised as "up to 1,8Ghz"

09:40 <npl> Im just doing some performance test for work, so these details matter at the moment =)

09:41 <npl> BTW. is there a way for mere mortals to get an RK3399 evalboard?

09:42 <npl> I take that the current kernel or dts is capped as 1608 for rk3288. Can live with that, just was really sure it was 1800 just a day ago =)

09:46 <npl> Just another question: thermal throttling seems to be independent of the cpufreq govenor? I had some drops to 1Ghz during benchmarks

11:34 <mmind00> npl: thermal throttling is tied into cpufreq, so when heat-levels are reached the max frequency gets capped

11:35 <mmind00> npl: the rk3399evbis not on sale

11:37 <mmind00> npl: and yes the rk3288 can reach these 1.8Ghz, but especially on devboards without any heat-management the chip can get quite hot

11:52 <npl> Yeah, not just the chip.. the entire platine was hot =)

16:20 <vagrantc> well, u-boot v2016.09-rc2 fixed my issues with firefly-rk3288 ... yay.

16:21 <vagrantc> still having troubles with veyron-speedy chromebook where the eMMC is detected maybe once out of every 10 boots

16:22 <vagrantc> curious how the boot commandline option rockchip.usb_uart is used ... the documentation i've found in the kernel and searching online is pretty sparse

17:06 <karlp> depthcharge?

17:07 <vagrantc> karlp: it's a bootloader used on chromebooks

17:09 <vagrantc> for one thing, depthcharge doesn't appear to have any way to specify alternate boot configurations at boot... which makes debugging ... interesting.

17:13 <karlp> sounds like a pretty deliberate attempt at killing uboot :)

20:10 <vagrantc> well, seemed to have figured out the eMMC issue on veyron-speedy ... basically needs the same patch applied for minnie: 984926781122f034d5bc9962815d135b6c4a8e1d ARM: dts: rockchip: temporarily remove emmc hs200 speed from rk3288 minnie

20:41 <mmind00> vagrantc: what do you need regarding rockchip.usb_uart? The rk3288 can use one of the usb ports (the otg one) to route uart signals to it

20:41 <mmind00> vagrantc: i.e. you'd get raw uart signals on the usb pins

20:42 <mmind00> vagrantc: for cabling see https://plus.google.com/+HeikoSt%C3%BCbner_x/posts/3guSYz4xXnm