domidumont has quit [Remote host closed the connection]
domidumont has joined #linux-sunxi
Shirasaka-Hazumi is now known as huawei
Azathtot has joined #linux-sunxi
Azathtot has quit [Client Quit]
_whitelogger has quit [Excess Flood]
_whitelogger has joined #linux-sunxi
matthias_bgg has quit [Ping timeout: 246 seconds]
<rellla>
bah. this orangepi forum speed is totally demotivating ...
p1u3sch1 has quit [Ping timeout: 268 seconds]
p1u3sch1 has joined #linux-sunxi
_massi has joined #linux-sunxi
IgorPec4 has joined #linux-sunxi
IgorPec4 has quit [Ping timeout: 240 seconds]
_whitelogger has quit [Excess Flood]
_whitelogger has joined #linux-sunxi
formruga has quit [Remote host closed the connection]
formruga has joined #linux-sunxi
cptG_ has joined #linux-sunxi
JohnDoe_71Rus has quit [Remote host closed the connection]
cptG has quit [Ping timeout: 246 seconds]
MY123 has joined #linux-sunxi
<vickycq>
And for me, the linux-sunxi wiki speed is totally demotivating...
apritzel has joined #linux-sunxi
FDCX has quit [Ping timeout: 246 seconds]
ricardocrudo has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
<rellla>
vickycq: no speed issues here ...
kelvan has quit [Remote host closed the connection]
kelvan has joined #linux-sunxi
FDCX has joined #linux-sunxi
IgorPec has joined #linux-sunxi
<plaes>
rellla, vickycq: yeah, no speed issues here either
Rondom_ is now known as Rondom
<MY123>
hi ;)
<MY123>
Cortex-A53 on 40nm is a TERRIBLE idea
<MY123>
:p
vagrantc has quit [Ping timeout: 250 seconds]
tkaiser has joined #linux-sunxi
vagrantc has joined #linux-sunxi
<tkaiser>
rellla: plaes: I believe vickycq was mentioning the 'great firewall' ;)
<plaes>
yeah.. It occurred to me as well
domidumont has quit [Quit: Leaving.]
domidumont has joined #linux-sunxi
<tkaiser>
memleak: OPi One has in fact all the USB ports available (2 on solder points) and you can use dts for Orange Pi PC. Only difference is the voltage regulator but doesn't matter at this time when you're using mainline kernel. Works just fine (without Ethernet/display atm of course)
matthias_bgg has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
<tkaiser>
Since Xunlong was clever enough to use identical DRAM type and routing on all H3 Orange Pi one .dts works for all boards in fact, only the Plus needs special attention to power the USB-to-SATA bridge when rootfs is on USB.
<rellla>
tkaiser: is the orangepi server hosted on the east side of the firewall?
<jelle>
I think it's hosted on an orange pi pc :p
<tkaiser>
rellla: I would believe so. At least according to IP addresses Xunlong's and LeMaker's servers are hosted at the same hoster or maybe even the same cabinat and when Orange Pi forums sucks, LeMaker's does also
<tkaiser>
jelle: OPi PC would be a good choice, AFAIK Igor hosts the Armbian forum on an A20
p1u3sch1 has quit [Ping timeout: 276 seconds]
p1u3sch1 has joined #linux-sunxi
<tkaiser>
rellla: Use ping and maybe tracebox to check www.orangepi.org the next time it's too slow
<tkaiser>
ssvb: Thanks for cpuburn-a53. Without soldering a different DC-IN solution to Pine64 it's close to impossible to verify reliability at 1200 MHz :)
<rellla>
tkaiser: i don't need this forum, i'm just interested in how many effort is spent apart from linux-sunxi and why developing-people don't appear here or on ml ...
<tkaiser>
rellla: Since they don't know what linux-sunxi is? Someone might spread the words there and things might improve...
<MY123>
well, factory-overclocked stuff
<tkaiser>
MY123: Nope
<MY123>
tkaiser, I saw lots of factory-overclocked tablets
<tkaiser>
MY123: 'factory defaults' for Pine64 are 1152 MHz max. Community devs tried to unlock 1200/1344 but I hope I could convince them (after learning a lot from ssvb) to stay away from that
<MY123>
mostly Allwinner A20 stuff
<MY123>
tkaiser, well, is overvolt possible on the Pine64?
* MY123
thinks that if there is something to overclock, it's the Mali
<tkaiser>
The real problem when trying to unlock higher cpufreqs on Pine64 is Micro USB used for DC-IN. This will be then reason N¡ 1 for stability problems, crashes and data corruption.
<jemk>
tkaiser: did you try to use the pin headers to supply power? there are two dcin pins, they should be able to carry quite some current.
cajg has joined #linux-sunxi
<tkaiser>
jemk: No, I just tried to stop any overvolting/overclocking attempts since I would believe the settings longsleep chooses in his OS images now will be taken by anyone else who provides 3.10.x OS images for the Pine64 the next time
<jemk>
yeah, sure, i don't want to promote overclocking too
<tkaiser>
jemk: The other problem is: My heatsink is crap so I would either burn the A64 or have to allow throttling. And then testing anything above 1152 doesn't work
<MY123>
tkaiser, this reminds me of the Pi2/3 throttling to 600MHz when it detects that the voltage is too low
<tkaiser>
MY123: I would suspect the PMIC (AXP803?) contains an ADC to measure that like on AXP209. But now no readouts are exposed through sysfs
<MY123>
I think that having a fuse burnt on overclocking is the better solution
<MY123>
(avoids warranty for overclocked boards)
<tkaiser>
Let's see how the Pine people deal with both problems. Delivering an '1.2 GHz' that runs at 1152 MHz max and communicating that stability problems might be related to smartphone chargers and crappy USB cables and not software or the Pine64 instead. Good luck
<tkaiser>
jemk: Uploading a photo with these 2 pins marked/explained to the wiki might be a good idea
<MY123>
tkaiser, deceptive advertising
<tkaiser>
MY123: I would suspect just wrong communication between Allwinner and TL Lim in the beginning. The one mail he forwarded regarding A64 being 28nm or not was fascinating ;)
<tkaiser>
They started to promote the 1.2GHz just to realise later they got 1152MHz 'factory defaults' in reality
<eighc>
i have a q88 board and i already have debian vm with cross toolchain setup
<eighc>
i cloned sunxi-3.4 from linux-sunxi
<eighc>
will this give me the most features?
<eighc>
wiki says that suspend to ram is not supported
<eighc>
suspend to ram means that the whole SoC is down, and the only way to bring it back up is via rtc interrupt or user interface?
<eighc>
the wifi module on this board has four pads and communicates over usb, which means that there is no separate interrupt pin - since SoC is down in the suspend to ram, this would mean that the usb controller is down too, and that the device can't be brought back up over wifi?
<eighc>
does suspend to ram improve battery life at all? when is it used?
keesj has quit [Ping timeout: 240 seconds]
tkaiser has joined #linux-sunxi
<tkaiser>
eighc: On H3 in this mode consumption is at ~0.3W but there this is managed by the ARISC core inside the H3. No idea about A13 and whether there exists a pin to be used for resume
kaspter has quit [Ping timeout: 248 seconds]
JohnDoe_71Rus has joined #linux-sunxi
huawei has quit [Ping timeout: 246 seconds]
Shirasaka-Hazumi has joined #linux-sunxi
vishnup has joined #linux-sunxi
JohnDoe5 has joined #linux-sunxi
JohnDoe_71Rus has quit [Ping timeout: 244 seconds]
Ueno_Otoko has quit [Ping timeout: 250 seconds]
_whitelogger has quit [Excess Flood]
_whitelogger has joined #linux-sunxi
<eighc>
kernel itself does have the option to enable suspend to ram, i guess wiki is outdated
iamfrankenstein1 has joined #linux-sunxi
iamfrankenstein has quit [Ping timeout: 248 seconds]
iamfrankenstein1 is now known as iamfrankenstein
paulk-collins has joined #linux-sunxi
Netlynx has joined #linux-sunxi
<tkaiser>
eighc: Well then update the wiki. There aren't that much people that take care of 3.4 any more.
<wens>
linux foundation got selected this year for gsoc
yann||work has joined #linux-sunxi
mossroy has joined #linux-sunxi
mzki has quit [Quit: leaving]
apritzel has quit [Ping timeout: 244 seconds]
<Turl>
wens: o/
iamfrankenstein1 has joined #linux-sunxi
iamfrankenstein has quit [Ping timeout: 264 seconds]
iamfrankenstein1 is now known as iamfrankenstein
_massi has quit [Quit: Leaving]
valkyr1e has quit [Ping timeout: 250 seconds]
valkyr1e has joined #linux-sunxi
afaerber has quit [Quit: Ex-Chat]
gusenkovs_ has quit [Quit: Page closed]
ricardocrudo has quit [Remote host closed the connection]
reinforce has quit [Quit: Leaving.]
cosm_ has quit [Quit: Leaving]
keesj has joined #linux-sunxi
p1u3sch1 has quit [Ping timeout: 264 seconds]
p1u3sch1 has joined #linux-sunxi
p1u3sch1 has quit [Ping timeout: 244 seconds]
p1u3sch1 has joined #linux-sunxi
arokux has joined #linux-sunxi
Netlynx has quit [Quit: Leaving]
matthias_bgg has quit [Remote host closed the connection]
_whitelogger has quit [Excess Flood]
_whitelogger has joined #linux-sunxi
<arete74>
generalstupid: align 8192 pre 516µs on 516µs post 502µs diff 7.11µs
<arete74>
this is the line important
<KotCzarny>
funnily his card doesnt show anything in megs range
<KotCzarny>
maybe it's erase size is 8k too
pstef has quit [Ping timeout: 246 seconds]
<GeneralStupid>
its slow in every situation :(
<GeneralStupid>
it should be UHS-1
ilmaisin has joined #linux-sunxi
<ilmaisin>
hi, is there something that would prevent user installing a linux distro with mainline kernel on an arm board and then building and running the mali gpu driver?
<ilmaisin>
haven't yet found instructions to do that
<GeneralStupid>
ilmaisin: its "no problem" to do that
<ilmaisin>
GeneralStupid: unfortunately that page does not discuss installing the kernel modules on mainline kernel
<GeneralStupid>
ilmaisin: mainline :/ Im sorry
<ilmaisin>
yes, like one would do with nvidia drivers on a desktop computer
<GeneralStupid>
mainline on desktop? :D
<GeneralStupid>
Iam debian user, i dont understand that :D
<longsleep>
tkaiser: Hey quick question, regarding NFS boot, do you really need this stuff directly in vmlinux or would it be ok to have them as modules so you can load it via initrd?
domidumont has quit [Ping timeout: 276 seconds]
<ilmaisin>
GeneralStupid: Yes, as far as I know, desktops run mainline or very very lightly modified kernels
afaerber has joined #linux-sunxi
<GeneralStupid>
ilmaisin: yes, thats true. but iam sorry. i didnt find my link :D