Turl changed the topic of #linux-sunxi to: Allwinner/sunxi /development discussion - did you try looking at our wiki? https://linux-sunxi.org - Don't ask to ask. Just ask and wait! - https://github.com/linux-sunxi/ - Logs at http://irclog.whitequark.org/linux-sunxi
vagrantc has joined #linux-sunxi
khuey is now known as khuey|away
avernos has quit [Quit: Ex-Chat]
interrobangd has quit [Quit: Leaving]
apritzel1 has joined #linux-sunxi
naobsd has joined #linux-sunxi
apritzel1 has quit [Ping timeout: 246 seconds]
naobsd1 has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
naobsd has quit [Read error: Connection reset by peer]
naobsd1 is now known as naobsd
akaizen has quit [Remote host closed the connection]
viccuad has quit [Ping timeout: 246 seconds]
naobsd has quit [Quit: naobsd]
akaizen has joined #linux-sunxi
apritzel has quit [Ping timeout: 246 seconds]
ninolein has quit [Ping timeout: 250 seconds]
egbert has quit [Disconnected by services]
ninolein has joined #linux-sunxi
egbert has joined #linux-sunxi
orly_owl has joined #linux-sunxi
_whitelogger_ has joined #linux-sunxi
clonak has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
nashpa has joined #linux-sunxi
ricardocrudo has quit [*.net *.split]
tomboy65 has quit [*.net *.split]
codekipper has quit [*.net *.split]
cajg has quit [*.net *.split]
adj_ has quit [*.net *.split]
nashpa_ has quit [*.net *.split]
MackBoy has quit [*.net *.split]
formruga has quit [*.net *.split]
NiteHawk has quit [*.net *.split]
libv has quit [*.net *.split]
SJRvanSchaik has quit [*.net *.split]
_fortis has quit [*.net *.split]
engideavr has quit [*.net *.split]
firnsy has quit [*.net *.split]
bbrezillon has quit [*.net *.split]
speakman has quit [*.net *.split]
Michal has quit [*.net *.split]
NiteHawk has joined #linux-sunxi
cnxsoft has quit [Ping timeout: 264 seconds]
ricardocrudo has joined #linux-sunxi
tomboy65 has joined #linux-sunxi
speakman has joined #linux-sunxi
SJRvanSchaik has joined #linux-sunxi
cajg has joined #linux-sunxi
engideavr has joined #linux-sunxi
Michal has joined #linux-sunxi
MackBoy has joined #linux-sunxi
adj_ has joined #linux-sunxi
formruga has joined #linux-sunxi
_fortis has joined #linux-sunxi
libv has joined #linux-sunxi
bbrezillon has joined #linux-sunxi
firnsy has joined #linux-sunxi
codekipper has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-sunxi
Ueno_Otoko has joined #linux-sunxi
p1u3sch1 has quit [Ping timeout: 250 seconds]
p1u3sch1 has joined #linux-sunxi
ricardocrudo has quit [Ping timeout: 245 seconds]
TheSeven has quit [Ping timeout: 240 seconds]
TheSeven has joined #linux-sunxi
kaspter has joined #linux-sunxi
Gerwin_J has joined #linux-sunxi
Ueno_Otoko has quit [Ping timeout: 264 seconds]
_whitelogger has joined #linux-sunxi
Ueno_Otoko has joined #linux-sunxi
IgorPec has joined #linux-sunxi
vagrantc has joined #linux-sunxi
Ueno_Otoko has quit [Ping timeout: 276 seconds]
JohnDoe_71Rus has joined #linux-sunxi
iamfrankenstein has joined #linux-sunxi
iamfrankenstein has quit [Client Quit]
lynxis has quit [Remote host closed the connection]
lynxis has joined #linux-sunxi
vishnu_ has quit [Remote host closed the connection]
vishnu_ has joined #linux-sunxi
iamfrankenstein has joined #linux-sunxi
kaspter has quit [Remote host closed the connection]
vagrantc has quit [Quit: leaving]
hipboi has quit [Quit: This computer has gone to sleep]
vinifr has joined #linux-sunxi
<vinifr> hi guys, there is no more sunxi-next in git://github.com/mripard/linux.git, which branch should I use to sunxi mainline?
afaerber has joined #linux-sunxi
<plaes> vinifr: did you find it somewhere on the wiki?
<vinifr> I would like to use mripard repo
<vinifr> does not matter if it stable or not
<plaes> well, in case you really want unstable stuff, then there's this: https://github.com/jwrdegoede/linux-sunxi/tree/sunxi-wip
<plaes> linux-sunxi's sunxi-next is for next mainline
<plaes> and the last one contains some stuff that's submitted but still under review
<plaes> wens: official sunxi-next branch is now under linux-sunxi?
<vinifr> what about mripard' repo?
<plaes> no idea
Ueno_Otoko has joined #linux-sunxi
mosterta has joined #linux-sunxi
VargaD has quit [Ping timeout: 250 seconds]
VargaD has joined #linux-sunxi
Ueno_Otoko has quit [Ping timeout: 260 seconds]
<topi`> does anyone know if there is a similar channel than this for Rockchip discussion? I'm getting a Geekbox soon
<topi`> afaik there is some folks behind mainlining RK3368 support
<Wizzup_> there is a rockchip channel, yes
<Wizzup_> tried #linux-rockchip ? (a guess)
<NiteHawk> try #linux-rockchip
<topi`> great
<topi`> well, the title for cheapest NAS soc still goes to A20 :)
<topi`> and Rockchip hasn't shown any willingness to implement SATA in silicon
FlorianH has joined #linux-sunxi
apritzel has joined #linux-sunxi
<MoeIcenowy> @mripard Where can I find sunxi kms code now?
<wens> plaes: i dont have push permission to mripard's repo :p
<wens> his git.kernel.org next branch only carries sunxi stuff for linux-next
<wens> sunxi-next over on linux-sunxi is for everyone who want latest stuff but doesn't want to use linux-next
<KotCzarny> cheapest and bestest
<MoeIcenowy> but it seems that no pre-configured A20 NASes available
<KotCzarny> um, apt-get install samba ?
<KotCzarny> apt-get install nfsd ?
<NiteHawk> no no, "emerge samba" ;)
JohnDoe_71Rus has quit [Quit: KVIrc KVIrc Equilibrium 4.2.0, revision: 42021, sources date: 20120701, built on: 2013-10-21 12:25:22 UTC 42021 http://www.kvirc.net/]
reinforce has joined #linux-sunxi
<MoeIcenowy> NiteHawk: and wait for a heat A20
<MoeIcenowy> :-)
<NiteHawk> bah, that's not really an issue on A20 :)
<topi`> agreed, according to a blog post in Olimex.com, it seems the H3 is otherwise
<topi`> for some reason, the H3 seems to excel at heat production
apritzel has quit [Ping timeout: 246 seconds]
<MoeIcenowy> cpufreq-utils can solve most problems :p
viccuad has joined #linux-sunxi
FlorianH has quit [Ping timeout: 276 seconds]
paulk-collins has joined #linux-sunxi
Ueno_Otoko has joined #linux-sunxi
FlorianH has joined #linux-sunxi
domidumont has joined #linux-sunxi
domidumont has quit [Remote host closed the connection]
domidumont has joined #linux-sunxi
Netlynx has joined #linux-sunxi
reinforce has quit [Ping timeout: 255 seconds]
apritzel has joined #linux-sunxi
<diego71> topi`: only because most of the board overclock it (or believe in aw marketing, and use it at very high clock frequency)
<KotCzarny> overheating cpu isnt smart idea
tkaiser has joined #linux-sunxi
<tkaiser> topi`: The blog post from Olimex was wrong. Ssvb explained everything in detail here: https://groups.google.com/forum/#!topic/linux-sunxi/20Ir4It3GsA
<tkaiser> To sum it up: Use sane dvfs and 'cooler table' settings and take care of heat dissipation and you're done
<ssvb> topi`: olimex encountered overheating problems with their h3 board, but we have no reasons to generalize this information
Gerwin_J has quit [Quit: Gerwin_J]
reinforce has joined #linux-sunxi
<ssvb> moreover, they suspect DRAM clock speed being the culprit, but I tried to ask in their blog about the type of DRAM they use and did not get any answer
<MoeIcenowy> In fact A33 will also have many heat
<MoeIcenowy> A33 runs at 1.34GHz at most
<MoeIcenowy> and it's still stable
apritzel has quit [Ping timeout: 246 seconds]
<ssvb> how can one read the .brd and .sch files from https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/H3-OLinuXino ?
naobsd has joined #linux-sunxi
<plaes> ssvb: eagle
<ssvb> it would be nice if they just had a pdf schematic file for lazy people who don't want to install extra tools
<ssvb> topi`: anyway, Orange Pi PC is a very nice H3 board, almost a perfect one for this SoC
<MoeIcenowy> and cheap
<ssvb> just missing gigabit ethernet, all the other bells and whistles (wlan, etc.) you can get via usb peripherals
<MoeIcenowy> I won't buy a opipc as a development device only because I have no monitors
<MoeIcenowy> all my computers are notebooks
<ssvb> you can still use it as a headless 'server'
<ssvb> btw, do you have no TV?
<MoeIcenowy> I'm a college student in my dorm
<MoeIcenowy> I may face the head problem after I get my CHIP
<MoeIcenowy> (Although it won't be shipped until July
<ssvb> yeah, I also fell into this trap
<ssvb> tried to buy a CHIP board during their getchip campaign, only to notice later that it does not get shipped immediately :-(
<MoeIcenowy> haha
<MoeIcenowy> And a VGA Adapter is more expensive than itself...
egbert has quit [Ping timeout: 260 seconds]
<MoeIcenowy> To be honest, I want to buy a RGB LCD and attach it to CHIP.
egbert has joined #linux-sunxi
<MoeIcenowy> A 7-inch RGB LCD with gt911 ctp is only ¥300
<tkaiser> ssvb: The announced Orange Pi One/Lite seem also interesting ($10/$13).
fl_0 has quit [Ping timeout: 260 seconds]
reinforce has quit [Quit: Leaving.]
Gerwin_J has joined #linux-sunxi
fl_0 has joined #linux-sunxi
<MoeIcenowy> tkaiser: Ah-Oh?
<vinifr> hi guys, i'm trying to boot mainline sunxi-next, but it hi guys, but hangs here: "fsck.exfat used greatest stack depth: 5240 bytes left"
Gerwin_J has quit [Client Quit]
<vinifr> but hangs here: "fsck.exfat used greatest stack depth: 5240 bytes left"
<NiteHawk> ssvb: maybe try https://schematics.io/ ?
<NiteHawk> nevermind, i just gave it a spin and it fails to import that specific .sch
avph has quit [Ping timeout: 255 seconds]
<ssvb> NiteHawk: I just want to know if the Olimex H3 board is using normal DDR3 or DDR3L, and also how the CPUX voltage is provided
<ssvb> this might give a hint about why they are suffering from overheating problems
<ssvb> but I guess, this was just an early engineering sample and Olimex will solve all the issues in the final revision of the board
avph has joined #linux-sunxi
lynxis has quit [Remote host closed the connection]
lynxis has joined #linux-sunxi
apritzel has joined #linux-sunxi
mosterta has quit [Ping timeout: 240 seconds]
SadSmile has joined #linux-sunxi
iamfrankenstein has quit [Quit: iamfrankenstein]
iamfrankenstein has joined #linux-sunxi
iamfrankenstein has quit [Client Quit]
tkaiser has quit [Quit: jIRCii - http://www.oldschoolirc.com]
<topi`> ouch, the xunlong freq tables sound really moronic
tkaiser has joined #linux-sunxi
<tkaiser> As ssvb pointed already out: Due to the cooler table they used Xunlong prevented extreme overvolting
<tkaiser> It's 'tuning' by 3rd parties that led to the overvolted/overclocked/overheated situation
paulk-collins has quit [Ping timeout: 240 seconds]
<ssvb> tkaiser: to be honest, the picture at http://www.aliexpress.com/item/Orange-Pi-PC-linux-and-android-mini-PC-Beyond-Raspberry-Pi-2/32448079125.html still advertises the 1.6GHz CPU clock speed
<KotCzarny> stupid oblivious marketingers
<ssvb> and the "Compatible with Raspberry Pi 2" claim is also fishy
<ssvb> I guess, it is probably normal for Chinese marketing if everyone is doing exactly the same
<tkaiser> Regarding the 1.6 Ghz in our wiki we still 'share' the same 'information' at many places ;)
<ssvb> being honest would put them at a disadvantage
<tkaiser> At least true for SinoVoip and LeMaker regarding cpufreq stuff
<ssvb> do you mean that the linux-sunxi wiki still lists 1.6GHz for H3 somewhere?
<tkaiser> The voltage regulatur on the new Orange Pi One/Lite is only able to adjust between 1.1V and 1.3V and they seem to take your recommended frequencies: 624 MHz @ 1.1V and 1200 MHz @ 1.3V
<tkaiser> Most of the stuff on the other Orange Pi pages is outdated/incomplete since most of us seem to focus on the PC only
<KotCzarny> is 1.5GHz stable with radiator+fan ?
<tkaiser> It's beyond specs. Again: Read the link to the linux-sunxi list, ssvb explained everything :)
<ssvb> KotCzarny: 1.5GHz needs high voltage, which is out of the valid range specified by the H3 datasheet
interrobangd has joined #linux-sunxi
apritzel has quit [Ping timeout: 246 seconds]
<ssvb> about the H3 CPU clock frequency, probably it's safe to assume that the nominal speed is 1.2GHz and it also can be "turbo boosted" up to 1.3GHz if you can provide good heat dissipation or tolerate occasional throttling
<MoeIcenowy> yes
<MoeIcenowy> 1.5 may be too high
<MoeIcenowy> The processor architecture in H3 should be the same as A33
<MoeIcenowy> (s/should//
JohnDoe_71Rus has joined #linux-sunxi
<ssvb> don't know, maybe something closer to 1.4GHz at 1.4V is also possible
<MoeIcenowy> or say "1.5Ghz at your own risk
<MoeIcenowy> cpufreq-utils can solve all problems
<MoeIcenowy> :p
pmattern has joined #linux-sunxi
<ssvb> MoeIcenowy: A33 is supposedly using 40 nm manufacturing process and H3 is using 28 nm, this means that H3 can probably run at a higher clock speed
<tkaiser> MoeIcenowy: cpufreq-utils alone won't help. The contents of the dvfs table are even more important.
<tkaiser> In Orange Pi's case just two table entries existed leading to the CPU cores being fed with 1.3V all the times even when clocking at 60 MHz
<tkaiser> Based on my tests heat scales more or less linearly with core voltage
<MoeIcenowy> tkaiser: it's the vendor's fault
<MoeIcenowy> but luckily script.bin.is changable
<KotCzarny> which mean oranges are the shittiest of them all
<MoeIcenowy> orange pi is a good guy
<MoeIcenowy> for rmb 100
<tkaiser> I won't expect software/support at that price
<MoeIcenowy> yes
<ssvb> KotCzarny: "which mean oranges are the shittiest of them all" - and this is based on what?
<MoeIcenowy> i did everything on my former a33 tablet
<MoeIcenowy> it's 460 rmb ($80-)
<ssvb> KotCzarny: the hardware seems to be ok, the software support is nonexistent but this is easily fixable
<MoeIcenowy> with a 10inch 20
<KotCzarny> ssvb: on the added value of false advertising
<MoeIcenowy> 1024x768 ips screen
<KotCzarny> apart from usual aw woes
<ssvb> KotCzarny: that's probably just a cultural difference thing, which is hard to comprehend by the westerners
<MoeIcenowy> what's the price of orange pi pc outside PRC?
<MoeIcenowy> in PRC it's 100rmb ($17-
<tkaiser> $15 + $3.5 worldwide shipping
<MoeIcenowy> tkaiset: also so cheap
<MoeIcenowy> shipping is also cheap
<KotCzarny> i bought opipc for ~30usd
<tkaiser> Yes, and shipping was also fast!
<MoeIcenowy> my CHIP costs $15 for shipping
<ssvb> yep, and the price is also below the VAT threshold in Europe (~22 euro I think), which is very nice
<MoeIcenowy> (and it won't be shipped until jul
<ssvb> I mean for the Orange Pi PC
<tkaiser> I'm curious whether they increase shipping costs for the 2 new Orange Pis (shipping should start on 25th)
<MoeIcenowy> Who have enough time can use Orange Pi to get 2 times better CPU performance/price value than Raspberry Pi 2
<MoeIcenowy> In China shipping services are very good
<MoeIcenowy> (if use the standard outside China
<MoeIcenowy> I bought my uSD breakout at Tue. afternoon
<MoeIcenowy> and get it at 9:00 on Wed
<MoeIcenowy> But I cannot also understand why Orange Pi will add a dangerous frequency
<MoeIcenowy> maybe it's only a bug
<MoeIcenowy> We'd report it to Xunlong
<ssvb> KotCzarny: 30usd seems a bit expensive, maybe you got it not directly from Xunlong but from some fishy reseller?
<tkaiser> Their settings weren't that dangerous since the 'cooler table' prevented using the highest clock speeds
<MoeIcenowy> tkaiser: ?
<MoeIcenowy> cooler table?
<tkaiser> In loboris' OS images these settings were then 'unlocked' and some values even higher. With Xunlong settings CPU cores were disabled (and never came back until reboot)
<KotCzarny> ssvb: yeah, local buy
<tkaiser> With loboris' settings throttling occured
<MoeIcenowy> In Huaqiang North the price of Allwinner devices can be 1/3 of the price on Amazon
<tkaiser> 'cooler table', budget cooling. That's what we've to deal with with most (or even all) recent SoCs. At least quad core or more
<MoeIcenowy> (I means Amazon not in China
<MoeIcenowy> At least my A33 is safe for 1.34GHz * 4
<MoeIcenowy> But maybe a tablet's board is more stable than a development board
<vinifr> hi, Has anyone tested the sunxi-next mainline with Cubieboard-v1?
<ssvb> MoeIcenowy: how did you test that it is stable? also are you sure that it does not get throttled?
cnxsoft has quit [Quit: cnxsoft]
<MoeIcenowy> ssvb: I used it to build mesa and llvm
<tkaiser> MoeIcenowy: And you always checked cpu frequency?
<MoeIcenowy> tkaiser: I didn't always check it
<ssvb> MoeIcenowy: gcc is not the most demanding workload
<MoeIcenowy> ssvb: then how?
<MoeIcenowy> (I may test now
<tkaiser> cpuburn-a7
<MoeIcenowy> (The device is currently in GNU/Linux
<MoeIcenowy> cpuburn-a7 is by ssvb?
<tkaiser> Yes
<tkaiser> You could also use stress and sysbench in parallel
<tkaiser> In my tests SoC temperatures increased even a bit compared to only running cpuburn on all cores.
<ssvb> vinifr: Cubieboard-v1 is supported by the mainline kernel since a very long time ago
<MoeIcenowy> cpufreq-ljt-stress-test will build a libjpeg-turbo, interesting...
<tkaiser> But this 'measurement thing' is difficult. Until you spend a lot of time on it and always check everything twice you run into wrong conclusions pretty fast
<tkaiser> s/until/unless
<MoeIcenowy> How can I judge whether the CPU goes wrong?
<ssvb> vinifr: do you mean that you have some problems with the *current* sunxi-next branch?
<MoeIcenowy> (And it seems that my tablet's DRAM runs at 360MHz
<ssvb> MoeIcenowy: if the CPU is having troubles, then the decoded JPEG images may be become corrupted and this gets detected by the test
<MoeIcenowy> oh
<MoeIcenowy> libjpeg-turbo is still being compiled
<MoeIcenowy> (my distro uses mozjpeg
<MoeIcenowy> ah-oh?!
<MoeIcenowy> I have cjpeg and djpeg
<MoeIcenowy> WTH
<MoeIcenowy> How does the script judge the utils
<MoeIcenowy> ssvb: can't mozjpeg ones be used?
<MoeIcenowy> ssvb:
<MoeIcenowy> ./cpufreq-ljt-stress-test:170:in ``': Cannot allocate memory - nproc (Errno::ENOMEM)
<MoeIcenowy> should I add some swaps or use zram?
<ssvb> MoeIcenowy: the script checks that the cjpeg and djpeg are from libjpeg-turbo, which has NEON optimizations. And NEON code is a much more demanding workload than the regular non-optimized C based jpeg decoder
<ssvb> MoeIcenowy: how much RAM do you have on your device?
<MoeIcenowy> 512m
<MoeIcenowy> ssvb: mozjpeg have also neon
<ssvb> 512m should be enough
<ssvb> is it used up by something?
<MoeIcenowy> oh a xfce
<MoeIcenowy> ssvb: Should I do more stress test when ./cpufreq-ljt-stress-test is running?
<MoeIcenowy> it may be too easy in 1344MHz
<ssvb> run cpuburn-a7 in parallel (cpuburn-a7 is heating up the cpu, and libjpeg-turbo is detecting potential corruption)
<MoeIcenowy> run one or four?
<MoeIcenowy> or three?
<ssvb> cpuburn-a7 is already forking to load all cpu cores
<ssvb> also try to tweak voltages in the cpufreq table to see if you have any safety headroom
<MoeIcenowy> 1344 passed
<MoeIcenowy> my device runs on 1.46V on 1344
<vinifr> ssvb, Yes, it hangs here: Starting kernel ...
<tkaiser> ssvb: BTW: On the A83T cpuburn forks only 4 threads not 8
<ssvb> MoeIcenowy: the recommended maximum is 1.4V according to the A33 datasheet, so you are already in a dangerous territory
<ssvb> tkaiser: yeah, this is a bug and it should be probably fixed
<ssvb> MoeIcenowy: are you sure that the CPU is not overheating at this voltage?
<topi`> what kind of instructions does the cpuburn-a7 use?
<topi`> probably a mix of integer and fp, to maximise the use of different units
<topi`> and minimize cpu stalls
<MoeIcenowy> ssvb: I may need to disassemble it?
<MoeIcenowy> to get the temperature
<ssvb> topi`: mostly floating point instructions (square root and multiplication in parallel), and also some branches and load/store
<ssvb> vinifr: why "env set fdt_high ffffffff"?
<tkaiser> MoeIcenowy: Keep an eye on /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq to see whether throttling happens
<MoeIcenowy> I locked it with governer=userspace
<vinifr> with or without this command, does not work
<MoeIcenowy> Oh it's 120000000
<ssvb> vinifr: does the latest kernel from kernel.org work on your board?
<tkaiser> And what does /sys/class/thermal/thermal_zone1/temp looks like?
<MoeIcenowy> it's forced to 12000000
<MoeIcenowy> tkaiser: 67
<MoeIcenowy> It seems that now 1.34GHz is not available
<vinifr> ssvb, I have not tested kernel.org yet, i'm testing https://github.com/linux-sunxi/linux-sunxi/tree/sunxi-next
<MoeIcenowy> in the new round of stress test
<MoeIcenowy> 1344 is SKIPPED
<ssvb> vinifr: unless you know what you are doing, it's a good idea to use stable kernels instead of the experimental branch
<tkaiser> MoeIcenomy: Do you have /sys/devices/virtual/thermal/cooling_device0/ with your kernel?
<MoeIcenowy> tkaiser: yes
<MoeIcenowy> and I have no /sys/class/thermal/thermal_zone1 but /sys/class/thermal/thermal_zone0
<ssvb> vinifr: but you have apparently picked a wrong kernel
<tkaiser> Ok, and what does 'cat /sys/class/thermal/thermal_zone0/temp' output?
<MoeIcenowy> 68
TheSeven has quit [Ping timeout: 250 seconds]
TheSeven has joined #linux-sunxi
<tkaiser> There's the culprit. Look into your fex file for the cooler table
<ssvb> vinifr: once again, http://linux-sunxi.org/Mainline_Kernel_Howto#Stable_releases says "This is probably what you should choose if you are looking for stability."
<topi`> ssvb: it's tricky business trying to exercise the load/store unit *while* not causing pipeline stalls on an in-order cpu like the cortex-a7 :)
<ssvb> MoeIcenowy: it looks like your CPU got throttled to 1.2GHz
<vinifr> well, like I said, i'm using sunxi-next over on linux-sunxi
<topi`> maybe if there is a way to ensure *most* of loads will just hit the L1 cache...
<ssvb> vinifr: well, that's the reason of your problem
<MoeIcenowy> How do the freq-vol table exist in mainline kernel?
<topi`> on another topic, does anybody know of a *cheap* camera module? I want to deploy several cameras around the house
<topi`> I hear Xunlong is selling a camera module for Orange PI for 6 bucks
<topi`> I just wonder if that is supported in linux
<tkaiser> topi`: It is
<tkaiser> But quality sucks
<ssvb> topi`: cortex-a7 is still pipelined, the square root calculation runs for many cycles in the background while the cpu can do other things
<topi`> ok, then my solution would be to buy 5x OPi PC for $15 apiece and then 5x camera modules
<tkaiser> No, you want to buy 5 Orange Pi One for $10 each ;)
<topi`> ssvb: yes, it works like that, *however* if another instruction is causing a data dependency on the result of that sqrt, then a pipeline stall occurs
<MoeIcenowy> tkaiser: is sunxi isp code in H3 SDK blobs?
<MoeIcenowy> In A33 SDK it is
<topi`> tkaiser: I need the camera-boards to have Wifi
<tkaiser> topi`: Then OPi Lite for $13 ;)
<ssvb> topi`: yes, these are the trivial basic things which every assembly programmer knows
<MoeIcenowy> need the camera-boards to have Wifi?
<topi`> btw is there any other way to buy Orange PI stuff than the aliexpress store? AE doesn't work for me since they don't take Paypal
<topi`> MoeIcenowy: to transfer the images in real-time :)
<MoeIcenowy> Maybe no other ways
<topi`> tkaiser: from my point of view, that product doesn't exist yet
<tkaiser> topi`: Only through local resellers. Regarding the new boards: http://www.cnx-software.com/2016/01/02/orange-pi-one-is-a-10-quad-core-board-with-ethernet-and-hdmi/
<topi`> ssvb: sorry, didn't mean to undermine your authority on the subject :)
<topi`> ssvb: actually, did you work for Nokia at some point in distant history?
<MoeIcenowy> Aliexpress (or its PRC version, Taobao) is the official of Xunlong
<topi`> OK. I need to find out a way to pay on Aliexpress and I don't have a credit card
<topi`> *sigh* I wish the would take bitcoin
<ssvb> vinifr: testing this patchset might be probably a too difficult task for you if you even have problems debugging the kernel boot problems
IgorPec2 has joined #linux-sunxi
<tkaiser> topi`: For the camera module you find an improved driver in one of the camera module threads in Xunlong's forum.
<MoeIcenowy> topi`: impossible to use bitcoin
IgorPec has quit [Ping timeout: 246 seconds]
<MoeIcenowy> topi`: It accepts Western Union
<topi`> I guess chinese authorities are very suspicious about bitcoin
<MoeIcenowy> or Bank Trasfer
interrobangd has quit [Read error: Connection reset by peer]
<MoeIcenowy> topi` :right
<vinifr> ssvb, ok, i'll check here, thanks
<topi`> tkaiser: is it a kernel driver that doesn't corrupt your kernel or make it crash? :)
<tkaiser> It's just an improved gc2035.c
<tkaiser> Providing better quality/fps
IgorPec2 has quit [Ping timeout: 246 seconds]
<topi`> ok
<tkaiser> topi`: Also have a look at https://groups.google.com/forum/#!topic/linux-sunxi/7_H233Cl4iE (@lex also patched the gc2035 driver)
<tkaiser> And if you really care about quality and want to record video in high resolution I would better go with Raspberry Pi A+ and its camera module
JohnDoe8 has joined #linux-sunxi
Ueno_Otoko has quit [Ping timeout: 265 seconds]
<topi`> but the camera modules for RPi are expensive
<topi`> all RPi modules are :
JohnDoe_71Rus has quit [Ping timeout: 260 seconds]
Gerwin_J has joined #linux-sunxi
<tkaiser> Yes, but you get 1080p video encoded on the VideoCore VPU
<tkaiser> Instead of 640x480 @ 4 fps ;)
<KotCzarny> ;)
<MoeIcenowy> tkaiser: try libvdpau-sunxi
<MoeIcenowy> although experimental
<tkaiser> It's about encoding
<MoeIcenowy> sunxi also supports encoding
<MoeIcenowy> although no suitable framework to implement it
<MoeIcenowy> ·Supports H.264 1080p@30fps video encoding
<tkaiser> I know but read the thread above
<MoeIcenowy> In fact, I wonder why an OTT solution (H3) have CSI
Netlynx has quit [Quit: Leaving]
<MoeIcenowy> tkaiser: I don't think this PoC is capable for H3
<tkaiser> That's the reason we still use RPi B+ as IP cameras. Recording/transcoding happens on sunxi devices
<MoeIcenowy> yes
<MoeIcenowy> the power of Allwinner processors are not well used by linux-sunxi community now
<vinifr> ssvb, ok, it works!!! There is some problem with default sunxi_defconfig
<plaes> vinifr: what was missing?
<vinifr> plaes, I don't have any idea :D I pick up a old from my folder when i was testing mainline
<topi`> does anyone know of a usable "virtual credit card" available for a european?
<topi`> I tried signing up for OKpay.com but their prices for putting money in (via SEPA transfer) were obscene
<plaes> I know two banks that offer them in Estonia, but you need to have an account
<ssvb> topi`: https://elisa.fi/lompakko/ but afaik now it costs 1 euro per month
<mripard> vinifr: sunxi_defconfig seems ok: http://kernelci.org/boot/sun4i-a10-cubieboard/
<plaes> mripard: http://linux-sunxi.org/Mainline_Kernel_Howto mentions linux-next in your github repo
<vinifr> mripard, well, to me does not, stay hang in Starting kernel ...
khuey|away is now known as khuey
<ssvb> vinifr: "I pick up a old from my folder when i was testing mainline" sounds like the likely culprit
khuey is now known as khuey|away
<ssvb> if you are improvising, then you should expect problems and be able to solve them yourself
leio has quit [Ping timeout: 260 seconds]
leio has joined #linux-sunxi
<vinifr> i mean, this old config works with sunxi-next from linux-sunxi
<ssvb> there are nice tools which can compare texts files
<vinifr> but default sunxi_defconfig does not work
<ssvb> you can try to use the "safedefconfig" make target with your working config
<ssvb> then compare the resulting "defconfig" file with "sunxi_defconfig"
<ssvb> using simple diff or maybe even visual diff tools such as http://meldmerge.org/
<ssvb> *savedefconfig
<mripard> plaes: changed, thanks
<MoeIcenowy> mripard: what's the status of disp kms?
<mripard> still the same, working on the A13, in progress on the A33
<MoeIcenowy> What's the difference of it on A13/33?
<mripard> the clocks are not the same
<mripard> the tcon has a single channel
<mripard> not much, but it still requires some work
<MoeIcenowy> I may still need to learn the clocking framework of Linux kernel
<MoeIcenowy> BTW, do you know any driver for gslX680 touchscreen ICs which do not require a certain version of sunxi kernel?
<MoeIcenowy> My SDK have 2 drivers, gslx680 and gslx680new
<MoeIcenowy> the former one do not work for my tablet
<MoeIcenowy> the latter one works, but not stable, and a blob exists in it
<mripard> I don't know much about the sunxi kernel, unfortunately
<MoeIcenowy> The "you" refers to the whole linux-sunxi
<vinifr> mripard, Excuse my ignorance, from where I can get the patchset: http://lists.infradead.org/pipermail/linux-arm-kernel/2015-October/382050.html
<mripard> vinifr: if you have the mails, you can apply the patches directly
<mripard> be aware that these patches will change drastically in the v2
<vinifr> mripard, which the appropriate kernel to test this patchset?
apritzel has joined #linux-sunxi
FlorianH has quit [Ping timeout: 272 seconds]
vishnu_ has quit [Ping timeout: 250 seconds]
FlorianH has joined #linux-sunxi
interrobangd has joined #linux-sunxi
<mripard> the one in the git branch ?
mawe242 has joined #linux-sunxi
<vinifr> ok
tkaiser has quit [Quit: jIRCii - http://www.oldschoolirc.com]
IgorPec has joined #linux-sunxi
<mawe242> mripard: I'm about to update the SPI word wait patch series with more fixes. Do I send the whole series to a combined recipient list for all patches/subsystems, or each patch in the series to a separate recipient list?
<robogoat> Does anybody have a link to a good document on USB OTG on the A20? I have a few pcduino3 nano lites, and I would like to use the serial and/or rndis gadgets,,
<mawe242> robogoat, do you know http://linux-sunxi.org/USB_Gadget ?
<robogoat> Ah, pfft.
<robogoat> I think I have done most of that, but let me doublecheck.
<mripard> mawe242: if it's just fixes, it doesn't need to be part of any series, just send them alone
<mawe242> mripard: ok, but if the series depends on some of those patches?
<mawe242> just add a note that the series depends on those?
<robogoat> mawe242: Hmm, I am trying to use a 4.3 kernel,
<robogoat> mainline,
<robogoat> and some of those configs don't match up.
<mawe242> mripard: but the question still remains... if the series contains patches that touches different subsystems, do I send the whole series to all recipients for all subsystem, or each patch with a separate recipient list?
<robogoat> Anybody have thoughts?
mosterta has joined #linux-sunxi
<robogoat> I am wondering if I am missing something for otg in sun7i-a20-pcduino3-nano.dts .
apritzel has quit [Ping timeout: 246 seconds]
JohnDoe8 has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/]
<atsampso1> robogoat: 4.3 mainline won't do OTG on the pcDuino Nano -- there's some patches you need. See http://thread.gmane.org/gmane.comp.hardware.netbook.arm.sunxi/19214/focus=19215
book`_ has quit [Ping timeout: 244 seconds]
interrobangd has quit [Quit: Leaving]
book` has joined #linux-sunxi
lemonzest has joined #linux-sunxi
avph has quit [Ping timeout: 255 seconds]
avph has joined #linux-sunxi
apritzel has joined #linux-sunxi
mmwolbrink has joined #linux-sunxi
reinforce has joined #linux-sunxi
mosterta has quit [Ping timeout: 265 seconds]
Ntemis has joined #linux-sunxi
apritzel has quit [Ping timeout: 246 seconds]
lemonzest has quit [Ping timeout: 245 seconds]
lemonzest has joined #linux-sunxi
Gerwin_J has quit [Quit: Gerwin_J]
<robogoat> atsampso1: Thanks!
<robogoat> Just found a thread in the armbian forum that says it should work on 4.4-rc6+
<robogoat> So maybe I will try that.
avph has quit [Ping timeout: 255 seconds]
avph has joined #linux-sunxi
Ntemis has quit [Remote host closed the connection]
<robogoat> atsampso1: Did you end up pulling specific patches from ssvb/20151014-4.3.0-rc5-pcduino2-otg-test or just using that branch?
domidumont has quit [Ping timeout: 246 seconds]
<robogoat> Also, do you have your dts patch in a public git repo anywhere?
lemonzest has quit [Quit: Leaving]
<atsampso1> robogoat: looks like I cherry-picked the patches from ssvb's branch and applied them to sunxi-next when I was testing it
<atsampso1> robogoat: the DTS patch ("ARM: dts: sun7i: Enable USB DRC on pcDuino v3 Nano") is in sunxi-next
viccuad has quit [Ping timeout: 246 seconds]
apritzel has joined #linux-sunxi
<ssvb> robogoat: what is your OTG use case?
bonbons has joined #linux-sunxi
<ssvb> OTG support is (or used to be) rather new and buggy
<robogoat> ssvb: Well, ideally g_serial or CDC ethernet.
<ssvb> if you want serial and ethernet support, then you can select these kernel options and statically compile this stuff
<ssvb> then there is probably a bug in the initialization order, so you want this workaround - https://github.com/ssvb/linux-sunxi/commit/f9a70e4ce11da9eb6b9654b8eb957ef41567603a
<ssvb> and maybe CONFIG_MUSB_PIO_ONLY=y is still necessary
<robogoat> Ok, yes, I think I have gathered some of this info from research earlier.
mawe242 has quit [Quit: Leaving]
<robogoat> I am currently testing some things with several pcduino3-nano-lites that I picked up on amazon.
<robogoat> Going full diskless.
<ssvb> moreover, the 'device' vs. 'host' role is selected once (based on the id pin of the connected cable) and if you try to change role at runtime, then everything fails
<robogoat> My current development process involves u-boot over spl, a serial cable and an ethernet cable.
<robogoat> spl/fel.
libv_ has joined #linux-sunxi
<robogoat> If I could do the serial/ethernet over the otg port as well as fel bootloading, I could cut 3 cables and an adapter down to 1 cable.
<robogoat> I think.
<ssvb> you can do this, that was exactly the use case I tested :-)
libv has quit [Ping timeout: 246 seconds]
libv has joined #linux-sunxi
<ssvb> robogoat: just take the patches from https://github.com/ssvb/linux-sunxi/commits/20151014-4.3.0-rc5-pcduino2-otg-test and everything should work
libv_ has quit [Ping timeout: 245 seconds]
reinforce has quit [Quit: Leaving.]
<ssvb> robogoat: maybe I need to check if all these problems are still there with the latest kernel and write some guide at http://linux-sunxi.org/USB_Gadget#mainline_kernel
libv_ has joined #linux-sunxi
<vinifr> I have tested HDMI and USB in mainline, both are ok
libv has quit [Ping timeout: 245 seconds]
<ssvb> vinifr: we are taking about USB *OTG* now
IgorPec has quit [Ping timeout: 246 seconds]
p1u3sch1 has quit [Read error: Connection reset by peer]
<vinifr> ok
<robogoat> Yes,
libv_ is now known as libv
<robogoat> I think that a platform with 0 firmware is a pretty interesting proposition.
<robogoat> Meaning, no physical places that store firmware (eeprom, nand, etc).
p1u3sch1 has joined #linux-sunxi
<robogoat> ssvb: Were you seeing much bugginess with those otg devices? Would they be unsuitable for a long-running usecase?
libv_ has joined #linux-sunxi
<ssvb> robogoat: I did not test this long enough, because I assumed that the work on the OTG support is still being done
<ssvb> but the general idea is that you should not touch the cable, if you try to unplug it and then plug back, everything blows up
<robogoat> Right, right.
<ssvb> and as I said, I have not checked the latest kernel yet, maybe things have changed for the better
<robogoat> I am just wondering if there were any "it blows up after x days/x bytes transferred" etc.
libv has quit [Ping timeout: 245 seconds]
<robogoat> Anyway, it is worth testing a bit myself :)
libv_ is now known as libv
libv has quit [Remote host closed the connection]
<ssvb> robogoat: sure!
robogoat has quit [Ping timeout: 265 seconds]
mmwolbrink has quit [Ping timeout: 245 seconds]
robogoat has joined #linux-sunxi
vinifr has quit [Quit: Saindo]
libv has joined #linux-sunxi
bonbons has quit [Quit: Leaving]
fredy has quit [Quit: ZNC - http://znc.in]
fredy has joined #linux-sunxi
FlorianH has quit [Ping timeout: 256 seconds]
SadSmile has quit [Quit: Leaving]
pmattern has quit [Quit: Genug für heute.]
pmattern has joined #linux-sunxi
Zotan has left #linux-sunxi ["http://quassel-irc.org - Chat comfortably. Anywhere."]
libv_ has joined #linux-sunxi
libv has quit [Ping timeout: 260 seconds]
libv_ is now known as libv
FlorianH has joined #linux-sunxi
bmeneg_ has joined #linux-sunxi
FlorianH has quit [Ping timeout: 276 seconds]