<shirasaka-hazumi>
haven't pine64 release a proper Mali driver?
bonbons has joined #linux-sunxi
Mr__Anderson has joined #linux-sunxi
Mr__Anderson has quit [Remote host closed the connection]
nikre has joined #linux-sunxi
mosterta has joined #linux-sunxi
IgorPec has joined #linux-sunxi
<ssvb>
wens: 3 usb host ports in h5, this also looks good, tkaiser will like it
<KotCzarny>
but those are usb2 still?
<ssvb>
yes, if we can trust this pdf
majosa has joined #linux-sunxi
<majosa>
Is gonna have FEL over serial?
ganbold has quit [Ping timeout: 244 seconds]
netlynx has quit [Quit: Ex-Chat]
OverCR has quit [Read error: Connection reset by peer]
OverCR has joined #linux-sunxi
Putti has quit [Ping timeout: 258 seconds]
<tkaiser>
I'm testing with 4.7 on Pine64+ (Armbian build), how can I increase the fixed CPU clockspeed (want to test Ethernet and tools like iperf/iperf3 are single threaded and most likely that's the reason for the low throughput numbers compared to BSP kernel)
<MoeIcenowy>
tkaiser: voltage adjusting is not available now
<MoeIcenowy>
and we're even discussing how to implement it
<tkaiser>
MoeIcenowy: ok, at which value is VDD_CPUX then now?
<tkaiser>
I mean. By default if PMIC is not able to adjust anything with mainline?
foudubassan has quit [Ping timeout: 264 seconds]
<MoeIcenowy>
It's said that it can be driven at 816MHz safely
ricardocrudo has joined #linux-sunxi
salon_ has joined #linux-sunxi
mosterta has joined #linux-sunxi
nikre has quit [Ping timeout: 264 seconds]
reinforce has joined #linux-sunxi
jernej has joined #linux-sunxi
Putti has quit [Ping timeout: 276 seconds]
<tkaiser>
MoeIcenomy: Thanks, but where/what to adjust to get from the 408 MHz it's now running at to 816?
<tkaiser>
I don't fear overheating/damage since I use heatsink and huge fan. Only undervolting should be an issue then.
Da_Coynul has joined #linux-sunxi
mosterta has quit [Ping timeout: 276 seconds]
premoboss has joined #linux-sunxi
jstein_ has joined #linux-sunxi
jstein_ is now known as jstein
jstein has quit [Remote host closed the connection]
jernej has quit [Ping timeout: 240 seconds]
Da_Coynul has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
salon_ has quit [Quit: Leaving]
<ssvb>
tkaiser: I think that on a64 now it's best to use a patched mainline u-boot with jemk's dram patch, this way we have everything 100% open source and you should get 816mhz for the cpu clock speed
<KotCzarny>
he wants more
<KotCzarny>
he wants 1.1ghz
<ssvb>
it's also possible with a bit of patching
<tkaiser>
ssvb: I will wait a bit, just tested around with 4.7. IIRC montjoie was not happy with GbE throughput testing on A64 but that's most probably just due to CPU cores running at 408 MHz (iperf is CPU bound and acts single-threaded in one direction)
Da_Coynul has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
Sakami-_- has joined #linux-sunxi
pg12 has quit [Ping timeout: 240 seconds]
Sakami- has quit [Ping timeout: 240 seconds]
fire219 has joined #linux-sunxi
jbrown has quit [Ping timeout: 265 seconds]
<_mamalala>
tkaiser: turns out that the bananapi m2+ _does_ have spdif output on the expansion header, they just made a type. just wrote about that in the forum
<KotCzarny>
write it on the linux-sunxi wiki
<KotCzarny>
much better place
<_mamalala>
once i make an account there, maybe :P
<_mamalala>
but indeed, on the opi-one they have a completely different pinout on the cam connector, and do indeed use the PA pin that usually has spdif ... strange
tsuggs_ has quit [Remote host closed the connection]
<tkaiser>
_mamalala: 'Team BPi' doesn't do typos. It's the other way around. They provide correct information only from time to time by accident.
<_mamalala>
lol
<_mamalala>
i find it rather strange that the cam connectors have a different pinout .... given that they use the same 24 pin FFC connector, i consider that a dangerous thing to do
<_mamalala>
i mean, i could tolerate the fact that they use different pinouts on the expansion headers, as long as the groupings for GND, VCC, etc. are the same ...
<_mamalala>
meaning that you wont iommediately short out something if you plug a different extension in
<_mamalala>
but with the cam connectors, that is what would happen
<KotCzarny>
consider banana team as untrustworthy
<_mamalala>
well, the cam connector on the opi-one has a slightly different pinout compared to the bpi, while both of them have a completely different pinout to the nanopi ....
jbrown has joined #linux-sunxi
<tkaiser>
_mamalala: lvmc got in touch with a hardware vendor to produce different intermediate boards to connect standard camera modules. IIRC he did boards for M2+ and the Oranges, no idea about NanoPi M1 (but there's a thread in Armbian forum regarding this: http://forum.armbian.com/index.php/topic/1213-ov5640-camera-with-orange-pi/)
<_mamalala>
tkaiser: i see ... well, i'm not using a cam anyways, instead i'm going to use the cam connector for the GPIO that is there ...
<_mamalala>
would be great if for example FA would make a board that has all the unused IO of the H3 exposed as well
<_mamalala>
in case of the M1, that would be 18 IO's from PD, 8 extra from PG, and 11 extra from PC
ricardocrudo has quit [Ping timeout: 264 seconds]
premoboss has quit [Ping timeout: 264 seconds]
<_mamalala>
tkaiser: from the forum thread, by mattday: "It turns out you need to essentially switch the whole connector 180 degrees. So pin 1 becomes pin 24 and vice versa. I can't see how his adapter achieves that, but I can confirm this is necessary for the Orange Pis"
<_mamalala>
hehe, that is rather simple .... those FFC/FPC connectors come in two flavours ... one with the contacts to the FPC on one side, the other having them on the other side ... so, naturally, you then plug in the cable 180° rotated, and voila, alle the pins are swapped
MiLeon has quit [Quit: Leaving]
tkaiser has quit [Ping timeout: 252 seconds]
Putti has joined #linux-sunxi
MiLeon has joined #linux-sunxi
cptG_ has joined #linux-sunxi
cptG has quit [Ping timeout: 240 seconds]
IgorPec15 has joined #linux-sunxi
jernej has joined #linux-sunxi
Da_Coynul has joined #linux-sunxi
Nyuutwo has joined #linux-sunxi
IgorPec has joined #linux-sunxi
reinforce has quit [Read error: Connection reset by peer]
IgorPec15 has quit [Ping timeout: 244 seconds]
reinforce has joined #linux-sunxi
<diego71>
ssvb: debian testing, and yes the issue 28 on github gave me the hint about how to fix. I add a note on the wiki just in case someone else had the same problem
jernej has quit [Ping timeout: 244 seconds]
mnr has joined #linux-sunxi
pg12_ has quit [Ping timeout: 260 seconds]
pg12 has joined #linux-sunxi
<MiLeon>
hello
<mnr>
MiLeon: Hello :)
cnxsoft has quit [Quit: cnxsoft]
_whitelogger has joined #linux-sunxi
<ssvb>
diego71: just for the record, I wasn't ever able to reproduce it yet, maybe I should check this debian testing rootfs
<willmore>
_mamalala, good point on the cable. Wonder if someone just used the wrong version of the connector.
<_mamalala>
willmore: dunno ... there are also FPC cables in various flavours, so if you have a connector on each PCB, you can reverse the pinout simply by using a different cable ...
<_mamalala>
plus, depending on the layout of a camera module, the signals can end up either way
<_mamalala>
that's the problem with nit having any sane standards for such things, everyone does their own thing
<_mamalala>
add to that the fact that cheap manufacturers/layouters rarely care for standards anyways, and it becomes obvious why there is such a mess
<willmore>
Understood. I have a camera for the Opi1 on the way along with the adapter board. So, I'll be reading up on this to make sure I hook it up right when the time comes.
<_mamalala>
otoh, it's rather funny to look at all the different layouts of these H3 based boards ... it seems that they mostly copy from each other anyways, just doing some minor modifications here and there
<_mamalala>
i mean, it would be really creepy coincidence otherwise, that the part symbols and namings are mostly the same among them
<_mamalala>
but then, could also be that they all just outsource the schematics and layout work to the same person
<willmore>
_mamalala, they may have all based their schematics on the reference info from the chip maker.
<_mamalala>
or that, yes
<willmore>
And, yeah, I think you're right in that it's the same small batch of people doing all the layouts.
premoboss has joined #linux-sunxi
<premoboss>
i am using nanopi neo with armbian. kernel version 4.7.2-sun8i. i configured usb0 with ip 192.168.10.41/255.255.255.0 inside /etc/network/interfaces. add g_ether to /etc/modules. usb0 is up and running after a reboot. but on pc side, the usb0 does came up. i already configured it into (etc/network/interfaces of PC, the port is ok because with another miniboard (no nanopi neo) the usb0 came up at pc side and i can ssh into board with it. so i thinnk
<premoboss>
error is in same wrong configuration aon nanoneo side. hany help?
jbrown has quit [Ping timeout: 276 seconds]
mzki has quit [Ping timeout: 244 seconds]
jbrown has joined #linux-sunxi
lennyraposo has quit [Quit: Leaving.]
lennyraposo has joined #linux-sunxi
lennyraposo has quit [Client Quit]
lennyraposo has joined #linux-sunxi
somedude23 has joined #linux-sunxi
foudubassan has joined #linux-sunxi
tkaiser has joined #linux-sunxi
IgorPec2 has joined #linux-sunxi
IgorPec2 has quit [Ping timeout: 240 seconds]
IgorPec2 has joined #linux-sunxi
vagrantc has joined #linux-sunxi
IgorPec2 has quit [Client Quit]
Da_Coynul has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
popolon has joined #linux-sunxi
tkaiser has quit [Read error: Connection reset by peer]
avph has quit [Ping timeout: 264 seconds]
tkaiser has joined #linux-sunxi
avph has joined #linux-sunxi
tkaiser has quit [Ping timeout: 240 seconds]
jbrown has quit [Ping timeout: 255 seconds]
paulk-collins has quit [Remote host closed the connection]