<diederik>
Is CONFIG_CRYPTO_DEV_ROCKCHIP only useful in rk3288 devices? "modinfo rk_crypto" lists rockchip,rk3288-crypto[C*] as aliases
<diederik>
I did the following test on Debian's 5.10.0-6-arm64 kernel and one whereby the CONFIG_CRYPTO_DEV_ROCKCHIP was enabled, but the results were the same
<diederik>
"for i in `ssh -Q cipher`; do dd if=/dev/zero bs=1M count=100 2> /dev/null | ssh -c $i test@localhost "(time -p cat) > /dev/null" 2>&1 | grep real | awk '{print "'$i': "100 / $2" MB/s" }'; done"
<macc24>
diederik: it looks like rockchip crypto is only supported for rk3288
<diederik>
ah yeah, I did find that one (earlier). But it looks to be 'above my paygrade'
<macc24>
"above your paygrade"?
<diederik>
too difficult for me to (properly) understand it (and do sth with that info)
<macc24>
you can always pay someone to do it for you :P
<diederik>
haha, yeah, that's an option. But for now I'll focus on other things
<diederik>
like getting audio working in a Debian kernel with a rock64
<diederik>
and I tried the CRYPTO thing, but that didn't bring benefits with which I could persuade Debian kernel maintainers
stikonas has joined #linux-rockchip
yann has joined #linux-rockchip
<macc24>
macromorgan: o/
vagrantc has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
stikonas has quit [Read error: Connection reset by peer]
stikonas_ has joined #linux-rockchip
stikonas_ is now known as stikonas
superherointj has joined #linux-rockchip
unrelentingtech has quit [Ping timeout: 250 seconds]
unrelentingtech has joined #linux-rockchip
unrelentingtech has quit [Max SendQ exceeded]
tucanae47 has quit [Ping timeout: 250 seconds]
daniels has quit [Ping timeout: 258 seconds]
unrelentingtech has joined #linux-rockchip
daniels has joined #linux-rockchip
tucanae47 has joined #linux-rockchip
<macc24>
ugh, so hardkernel just hardcoded a linear lookup table for battery
<macc24>
and they or rockchip wrote 3 costly functions that could have been out = (vol - 3500)/6
superherointj has quit [Quit: Leaving]
<macc24>
why is getting accurate percentage value from li ion battery so hard :(
<macc24>
idea
<macc24>
to calculate open circuit voltage by approximating resistance of battery and traces to battery and then using ohm's law to simulate what it would be
<urjaman>
the fun part is that the resistance of the battery changes with ... pretty much everything
<urjaman>
state of charge, temperature, age of battery
<macc24>
:(
<macc24>
fuck it, users will see either "no", "low", "medium", "high" or "full"
<urjaman>
yeah "we're good", "worry", "oh no" is often actually a fine scale to me :P
<macc24>
psp was fine with this
<macc24>
so odroid go super will be too
<urjaman>
it's more a problem when you have a technically accurate mAh counter counting down mA's that cannot be delivered before hitting the voltage cutoff because something changed
<macc24>
huh?
<urjaman>
and then the device does a "we're good" *power out*
<macc24>
oh
<macc24>
battery will probably be [|||]+, [||
<macc24>
-> [|||]+ [|| ]+ [| ]+ [ ]+
<urjaman>
like my worse C201 with a bit wonky battery ... it turns off at about 60% left, according to the gauge
<macc24>
oh shot
<macc24>
this battery is bad
<macc24>
rk817 has mah counter and coulomb counter
<macc24>
but they are too complicated for my brain :(
<urjaman>
and that "oh shoot too low voltage bye" also happens in situations with high internal resistance (=cold) if you suddenly increase the power use... (=turn on the screen)
<macc24>
uh oh
<urjaman>
i once had a phone play music for a good hour with no problem when i was working on my car, and then something prompted me to use the phone (=turn the screen on)... it turned on the screen and powered off