zoums has quit [Read error: Connection reset by peer]
zoums has joined #linux-sunxi
zoums has quit [Ping timeout: 240 seconds]
zoums has joined #linux-sunxi
zoums has quit [Ping timeout: 246 seconds]
<wens>
willmore: I know opi and bpi use slightly elevated voltages lol
zoums has joined #linux-sunxi
zoums has quit [Ping timeout: 250 seconds]
<willmore>
wens, what I had heard was more like "we used the closest resistors we had on hand and *oops*, it turned out to be a bit off what we were supposed to do..."
<willmore>
elevated should help. :)
<wens>
that sounds more like what would happen at the factory :/
<wens>
not in the design
zoums has joined #linux-sunxi
zoums has quit [Ping timeout: 246 seconds]
zoums has joined #linux-sunxi
zoums has quit [Ping timeout: 246 seconds]
zoums has joined #linux-sunxi
<lvrp16>
i have a friend whose brother worked at foxconn, they put the wrong capacitor on 60k iphone 5s, it still worked so nobody said anything and shoved it under a rug
<lvrp16>
happens more often than you think in China
zoums has quit [Ping timeout: 246 seconds]
zoums has joined #linux-sunxi
marcodiego has quit [Quit: Leaving]
zoums has quit [Ping timeout: 250 seconds]
<wens>
lol
zoums has joined #linux-sunxi
zoums has quit [Ping timeout: 240 seconds]
zoums has joined #linux-sunxi
zoums has quit [Ping timeout: 244 seconds]
zoums has joined #linux-sunxi
skiboy has quit [Quit: Leaving]
zoums has quit [Ping timeout: 240 seconds]
zoums has joined #linux-sunxi
zoums has quit [Ping timeout: 240 seconds]
zoums has joined #linux-sunxi
zoums has quit [Ping timeout: 244 seconds]
zoums has joined #linux-sunxi
TheSeven has quit [Ping timeout: 240 seconds]
[7] has joined #linux-sunxi
zoums has quit [Ping timeout: 250 seconds]
zoums has joined #linux-sunxi
zoums has quit [Ping timeout: 240 seconds]
dddddd has quit [Remote host closed the connection]
zoums has joined #linux-sunxi
lurchi_ has joined #linux-sunxi
lurchi__ has quit [Ping timeout: 250 seconds]
zoums has quit [Ping timeout: 250 seconds]
zoums has joined #linux-sunxi
kelvan has quit [Remote host closed the connection]
merlin1991 has quit [Read error: Connection reset by peer]
merlin1991 has joined #linux-sunxi
kelvan has joined #linux-sunxi
zoums has quit [Ping timeout: 240 seconds]
[7] has quit [Ping timeout: 240 seconds]
TheSeven has joined #linux-sunxi
zoums has joined #linux-sunxi
zoums has quit [Ping timeout: 244 seconds]
zoums has joined #linux-sunxi
selfbg has joined #linux-sunxi
zoums has quit [Ping timeout: 272 seconds]
zoums has joined #linux-sunxi
zoums has quit [Ping timeout: 246 seconds]
zoums has joined #linux-sunxi
zoums has quit [Ping timeout: 246 seconds]
random_yanek has quit [Ping timeout: 250 seconds]
random_yanek has joined #linux-sunxi
nuuuciano has quit [Ping timeout: 245 seconds]
heatfanjohn has quit [Remote host closed the connection]
<aalm>
lvrp16, do you know what would be the current most _stable_ setup for opi pc2? (or npi neo2? both are H5 however)
<lvrp16>
aalm: spectek memory, its a crapshoot, you have to test yourself. tiny boards have limited space for good voltage regulation designs.
pmp-p has quit [Ping timeout: 246 seconds]
pmpp has joined #linux-sunxi
pmpp is now known as pmp-p
tnovotny has joined #linux-sunxi
fkluknav has quit [Remote host closed the connection]
fkluknav has joined #linux-sunxi
<wens>
I suppose the schematics looks mostly the same, but the layout and trace sizes do matter
<karlp>
(it happens in the west too, we had some boards manufactured for ... a while... with the wrong caps on them, order of magnitude difference, all still worked fine, just not as good s it _could_ have done)
<wens>
how did that happen? blurred decimal point?
reinforce has joined #linux-sunxi
<karlp>
no idea, schematic says one thing, BOM says another.
<karlp>
some process fuckup at the manufacturing guys.
<karlp>
we were reviewing the bom for unrelated reasons, and were like, huh? that... cna't be right
nashpa has quit [Quit: Going away]
nashpa has joined #linux-sunxi
Andy-D has quit [Ping timeout: 250 seconds]
Andy-D has joined #linux-sunxi
nashpa has quit [Quit: Going away]
<wens>
hmm, did I forget to send the RGB565 and JPEG format support patches for sun6i csi?
nashpa has joined #linux-sunxi
nashpa has quit [Ping timeout: 246 seconds]
nashpa has joined #linux-sunxi
enrico_ has joined #linux-sunxi
nashpa has quit [Client Quit]
nashpa has joined #linux-sunxi
nashpa has quit [Client Quit]
nashpa has joined #linux-sunxi
The_Loko has joined #linux-sunxi
megi has joined #linux-sunxi
zoums has joined #linux-sunxi
tllim has joined #linux-sunxi
tl_lim has joined #linux-sunxi
tllim has quit [Ping timeout: 250 seconds]
leviathanch has joined #linux-sunxi
tl_lim has quit [Ping timeout: 250 seconds]
tl_lim has joined #linux-sunxi
fkluknav has quit [Remote host closed the connection]
paulliu has quit [Ping timeout: 250 seconds]
fkluknav has joined #linux-sunxi
zoums has quit [Ping timeout: 240 seconds]
paulliu has joined #linux-sunxi
tl_lim has quit [Ping timeout: 240 seconds]
nashpa has quit [Ping timeout: 240 seconds]
nashpa has joined #linux-sunxi
tllim has joined #linux-sunxi
<MoeIcenowy>
for H5 now I suggest just avoid them
<MoeIcenowy>
use H6 instead
<fALSO>
I didnt manage to even get the bootloader to work...
<fALSO>
tought my board wasnt ok, but tried an armbian and it worked
<fALSO>
gotta try your fork of the uboot with the h6 patches moeicenowy
<fALSO>
uboot -master didnt seem to work
<fALSO>
but im still trying to figure out something about the ATF
<fALSO>
from what i read in the documentation the ATF is required... but... uboot builds without any of it
<diego71>
fALSO, you should indicate the binary file of the ATF during the build
<fALSO>
do you know any guide or documentation specifiyng that ?
<fALSO>
i know how to build the ATF file... i just dont know how to make uboot use it
Net147 has quit [Read error: Connection reset by peer]
nashpa has quit [Quit: Going away]
nashpa has joined #linux-sunxi
Net147 has joined #linux-sunxi
nashpa has quit [Quit: Going away]
tnovotny has quit [Read error: Connection reset by peer]
nashpa has joined #linux-sunxi
<willmore>
wens, oh, most likely it was the factory doing a last minute substitution with *maybe* a consult to someone who though they understood things Maybe...
nashpa has quit [Quit: Going away]
nashpa has joined #linux-sunxi
nashpa has quit [Client Quit]
clemens3 has joined #linux-sunxi
nashpa has joined #linux-sunxi
nashpa has quit [Client Quit]
nashpa has joined #linux-sunxi
nashpa has quit [Ping timeout: 240 seconds]
nashpa has joined #linux-sunxi
nashpa has quit [Client Quit]
nashpa has joined #linux-sunxi
nashpa has quit [Client Quit]
nuuuciano has joined #linux-sunxi
nashpa has joined #linux-sunxi
nashpa has quit [Quit: Going away]
nashpa has joined #linux-sunxi
nashpa has quit [Ping timeout: 245 seconds]
nashpa has joined #linux-sunxi
perr has joined #linux-sunxi
nashpa has quit [Ping timeout: 240 seconds]
nashpa has joined #linux-sunxi
nashpa has quit [Client Quit]
nashpa has joined #linux-sunxi
nashpa has quit [Client Quit]
nashpa has joined #linux-sunxi
selfbg has quit [Remote host closed the connection]
zoums has joined #linux-sunxi
zoums has quit [Ping timeout: 240 seconds]
perr has quit [Remote host closed the connection]
perr has joined #linux-sunxi
<montjoie>
wow LUKSbench on H6 with cryptoengine 300kB/s such speed
<KotCzarny>
not good
<KotCzarny>
could it be it just needs another take to get up to speed?
<montjoie>
I set max clock of datasheet
<KotCzarny>
nah, as in, put/take data differently
<KotCzarny>
because 300kB is atrocious
<montjoie>
appart adding XTS since H6 support it, I am out of idea for the moment
<montjoie>
I will check with stock clock speed instead of using datasheet
zoums has joined #linux-sunxi
<KotCzarny>
dma? bigger blocks? parallel data processing?
<montjoie>
I already use 4k block
<montjoie>
I dreamed "4k will add too many speed ah aha h"
<KotCzarny>
how does it compare to bsp driver?
zoums has quit [Ping timeout: 240 seconds]
elros1 has quit [Remote host closed the connection]
<montjoie>
pfff, the image was generated on mmc and not on shm...
<KotCzarny>
still.
<montjoie>
5.8MB/s now
<montjoie>
my heart rebooted
<KotCzarny>
but if in real world scenario, writing to mmc would block hw crypto..
<montjoie>
H6 has a dedicated MMC controller with crypto EMCE
<montjoie>
it will be my next target when finished to mainline sun8i-ce and amlogic crypto
<montjoie>
wow xts(ecb(aes-arm64)) is only 3.7MB/s
<KotCzarny>
on marvell 3700 aes256-cbc is ~50MB/s
diego71_ has joined #linux-sunxi
perr has quit [Remote host closed the connection]
<KotCzarny>
or was it marvell armada375
diego71 has quit [Ping timeout: 245 seconds]
The_Loko has quit [Remote host closed the connection]
nashpa has quit [Ping timeout: 250 seconds]
<willmore>
montjoie, congrats, I think that beats what a Cortex-M3 can do at normal clocks....
nashpa has joined #linux-sunxi
argulp has quit [Quit: Leaving]
BenG83 has joined #linux-sunxi
msimpson has quit [Read error: Connection reset by peer]
<montjoie>
willmore: I need to understand why the cpu way is slower than h5
<montjoie>
perhaps its due to missing arm-ce
<montjoie>
module
<montjoie>
yeak better with ce
<willmore>
montjoie, what are you measuring with?
<willmore>
Does the H6 A53's have the crypto extensions?
<willmore>
I've never touched one.
BenG83 has quit [Quit: Leaving]
jstefanop has joined #linux-sunxi
<montjoie>
willmore: I measure a synchronous dd on a LUKS2 block
<montjoie>
I need to work with ipsec for bench also
netlynx has joined #linux-sunxi
netlynx has quit [Changing host]
netlynx has joined #linux-sunxi
<lvrp16>
i have been running stress test with nice cpuburn kmscube and memtester with u-boot at the limit of 768mhz for 30 some hours on 4 h5 1008MHz@1.1v and 15 hours on 4 h3 1008MHz@1.2v and it hasn't crashed. i will do a loop reboot test later today and higher frequencies on h3. kmscube on h3 doesn't seem to support textures and fails when i run it "-m rgba"
<lvrp16>
792 crashes immediately on both h3 and h5 so I assume there's a tuning issue or the memory controller flat out does not support it?
<lvrp16>
speak of the devil, 1 h3 just crashed
Andy-D has quit [Ping timeout: 250 seconds]
Rafael1980 has joined #linux-sunxi
Andy-D has joined #linux-sunxi
paulliu has quit [Quit: Leaving.]
leviathanch has quit [Remote host closed the connection]
JohnDoe_71Rus has joined #linux-sunxi
<quark_>
anarsoul: I found one problem why AP6356 module does not work in pine64-lts. eldo1 is actually wifi-vcc and dldo4 is wifi-vcc-io
<anarsoul>
oh
<quark_>
even though schematics say other way around
<anarsoul>
ask TL?
<quark_>
TL?
<anarsoul>
tllim on #pine64 on their irc server
<anarsoul>
he's Pine64 owner and he can ask HW guys
<quark_>
okey. thanks! I'll try to contact tllim
<quark_>
I did not found RTL8723BS module schematics and I don't have that module but I suppose it have to have reversed connections too
<quark_>
but there is now way around get that AP6356 working with eldo1 max 1.9V. Datasheet says min vcc voltage is 3.0V
<quark_>
some kind of jumper wire might be on option :)
enrico_ has quit [Quit: Bye]
diego_r has quit [Ping timeout: 246 seconds]
Mandragor has quit [Ping timeout: 250 seconds]
JBrooksBSI has joined #linux-sunxi
Mandragor has joined #linux-sunxi
Mandragor has quit [Ping timeout: 250 seconds]
t3st3r has joined #linux-sunxi
Mandragor has joined #linux-sunxi
JBrooksBSI has quit [Ping timeout: 256 seconds]
vagrantc has joined #linux-sunxi
<quark_>
anarsoul: actually just now noticed that rockpro64 board have vcc and vcc-io swapped in wifi/bt connector.
<quark_>
so that is the reason. pine64-lts and pine-h64 is not pin compatible with rockpro64. otherwise pinout is same in wifi/bt connector but those vcc and vcc-io are swapped
<anarsoul>
quark_: oh
<anarsoul>
that's unfortunate
<anarsoul>
fixable with dts, but unfortunate :(
<fALSO>
diego71_, trying now
<fALSO>
diego71_, make CROSS_COMPILE=aarch64-unknown-linux-gnu- PLAT=sun50i_h6 DEBUG=1 bl31
<fALSO>
Built build/sun50i_h6/debug/bl31.bin successfully
<fALSO>
going tomake that export point to it...
<fALSO>
im not sure if there was any different output on the uboot build
<fALSO>
going to flash it on the card anyway
<quark_>
anarsoul: I found from schematics that in pine64-lts both vcc and vcc-io can be feed from dldo4
clemens3 has quit [Ping timeout: 245 seconds]
<anarsoul>
quark_: I guess it requires some rework on the board
<quark_>
that might be one option. remove R20 and short R19
wasutton3_mobile has joined #linux-sunxi
<anarsoul>
for me it's easier to fix dts
<anarsoul>
or use dt overlay
<quark_>
but dts fix is not possible in pine64-lts because eldo1 is not able to provide 3.3V