<psydread>
I am trying to get graphics acceleration to work on my Orange Pi Win Plus running fully updated Debian Sid with Mesa 20.0.x and compiled 5.6.2 with the lima kernel module and other drivers yesterday to use the hardware to the fullest, but it still doesn't appear to work for some reason
lurchi_ has quit [Quit: Konversation terminated!]
lurchi_ has joined #linux-sunxi
cnxsoft1 has joined #linux-sunxi
cnxsoft has quit [Ping timeout: 256 seconds]
lurchi_ is now known as lurchi__
psydread has left #linux-sunxi [#linux-sunxi]
psydread has joined #linux-sunxi
chewitt_ is now known as chewitt
Mangy_Dog has joined #linux-sunxi
maccraft has joined #linux-sunxi
macc24 has quit [Ping timeout: 240 seconds]
Nakaori has quit [Ping timeout: 256 seconds]
yann has quit [Ping timeout: 260 seconds]
Kasreyn has joined #linux-sunxi
<Kasreyn>
morning! i was just reading about the BPi M3 USB-to-SATA port, one of the main reasons i picked up an M1.. do you know if the M2 Ultra has a native SATA interface?
<psydread>
I think they made a typo, it should be 1.5 GHz
<clementp[m]>
@megi sorry I missed to replug the radiator :S. Nothing wrong, I retest this morning and sent a serie. Don't hesitate to comment :)
<clementp[m]>
megi: ^
<Kasreyn>
thanks psydread :)
florian has joined #linux-sunxi
<psydread>
also doesn't that seem rather expensive for such a board? I paid €50 a piece for my Orange Pi Win Plus in 2017 and that included a power supply, a case, a 16 GB microSD card and shipping
<Kasreyn>
psydread: yeah.. a little price? i paid 58$ for the M1 in Oct 2015...
<Kasreyn>
there are not many sellers that have the M2U
<megi>
clementp[m]: great, thanks :)
<megi>
H6 Linux support is shaping up very nicely :)
<Kasreyn>
maybe i'll just continue using the M1 i've been very happy with it so far
NeuroScr has joined #linux-sunxi
kaspter has quit [Quit: kaspter]
florian has quit [Ping timeout: 258 seconds]
netlynx has joined #linux-sunxi
netlynx has quit [Changing host]
netlynx has joined #linux-sunxi
tdebrouw has joined #linux-sunxi
Kasreyn has quit [Remote host closed the connection]
macc24 has joined #linux-sunxi
Nakaori has joined #linux-sunxi
maccraft has quit [Ping timeout: 265 seconds]
<megi>
clementp[m]: I sent out all my feedback, I don't have anything more
<montjoie>
smaeul: your H6 network patch for uboot WORKS!!
<montjoie>
thanks, I will save lots of USB dongle
warpme_ has quit [Quit: Connection closed for inactivity]
gediz0x539 has quit [Ping timeout: 265 seconds]
reinforce has joined #linux-sunxi
macc24 has joined #linux-sunxi
gsz has quit [Quit: Konversation terminated!]
gediz0x539 has joined #linux-sunxi
florian has joined #linux-sunxi
<clementp[m]>
megi: thanks just one question regarding the thermal point set to 80°C. Is it no a bit low? allwinner set this to 100°C. A64 set it to 90°C.
florian has quit [Ping timeout: 260 seconds]
luke-jr has quit [Ping timeout: 260 seconds]
florian has joined #linux-sunxi
<clementp[m]>
I made a mistake the 1.8GHz reach the hot trip point very quickly and then oscilating between 1.5 and 1.8Ghz. Maybe it's better to lower this frequency and have it stable no ?
luke-jr has joined #linux-sunxi
florian has quit [Ping timeout: 256 seconds]
<clementp[m]>
maybe we can have a more stable point at 1.6Ghz
dddddd has quit [Ping timeout: 250 seconds]
mauz555 has joined #linux-sunxi
McSalty01 has joined #linux-sunxi
<McSalty01>
Hi all, I was originally not going to install debian to my Olinuxino Lime 2 board, but after some testing with other distros, I've found that the original sunxi image seems to work best (although I'll make my own build). I have just one question which I cannot find the exact answer for (probably my own fault, but I thought it's better just to ask you). Does the image contain any non-free or binary blobs (drivers eg.) (
<McSalty01>
including the u-boot)? I'm a linux-libre fan, but besides arch, I also choose to keep all my debian installs completely open. Thanks
<McSalty01>
my board uses the allwinner A20 soc*
<juri_>
mcsalty: from my memory, yes, but please refer to the linux-sunxi.org wiki to get a list of what is non-free in their support package for the A20.
return0e_ has quit [Ping timeout: 256 seconds]
<McSalty01>
juri_: thanks, but I searched for it and could not find any reference
mauz555 has quit [Remote host closed the connection]
mauz555 has joined #linux-sunxi
tllim has joined #linux-sunxi
mauz555 has quit [Ping timeout: 265 seconds]
<McSalty01>
juri: that last page is very interesting. How could I have looked over that. Thanks for that. It seems that everything is blob-free now, since I found references to articles that the cedarx allwinner soc is now liverated entirely. It's kind of dubious, because that already happened in 2013-2014 it seems. Although the page states they have only released part of their code. Will try to read some more about it. Thanks for
<McSalty01>
putting me on the right track!
RichardG867 has quit [Ping timeout: 272 seconds]
macc24 has quit [Ping timeout: 265 seconds]
mauz555 has joined #linux-sunxi
luke-jr has quit [Ping timeout: 256 seconds]
macc24 has joined #linux-sunxi
return0e has joined #linux-sunxi
mauz555 has quit [Remote host closed the connection]
luke-jr has joined #linux-sunxi
mauz555 has joined #linux-sunxi
mauz555 has quit [Remote host closed the connection]
mauz555 has joined #linux-sunxi
McSalty01 has quit []
<psydread>
I built everything from scratch last year using the linux-sunxi wiki as a guide, so I don't have any blobs installed as far as I know. The only kind of dodgy thing could be the ARM Trusted Firmware (as in people bringing up Trustzone as something similar to the Intel Management Engine), but even that came from Github
<buZz>
amd's trustzone is indeed licensed from ARM
<buZz>
i'm not aware of any sunxi chip that has something similar though?
<psydread>
I had to build u-boot with ARM Trusted Firmware support, that was the only thing
<psydread>
on Allwinner A64
<wens>
there's no ATF for ARMv7, and you probably aren't using OPTEE either
<wens>
the PSCI code for ARMv7 sunxi is in U-boot
vagrantc has joined #linux-sunxi
RichardG867_ has joined #linux-sunxi
tdebrouw has joined #linux-sunxi
jstein has joined #linux-sunxi
I[m] has joined #linux-sunxi
return0e has quit [Read error: Connection reset by peer]
return0e has joined #linux-sunxi
nashpa_ has quit [Quit: Going away]
nashpa has joined #linux-sunxi
sunshavi has quit [Remote host closed the connection]
sunshavi has quit [Remote host closed the connection]
aloo_shu has quit [Read error: Connection reset by peer]
tbueno has joined #linux-sunxi
aloo_two is now known as aloo_shu
aloo_shu has quit [Client Quit]
aloo_shu has joined #linux-sunxi
aloo_shu has quit [Client Quit]
aloo_shu has joined #linux-sunxi
lurchi__ is now known as lurchi_
sunshavi has joined #linux-sunxi
NeuroScr has joined #linux-sunxi
lurchi_ is now known as lurchi__
florian has quit [Ping timeout: 256 seconds]
gediz0x539 has quit [Quit: Leaving.]
dddddd has joined #linux-sunxi
dev1990 has quit [Quit: Konversation terminated!]
<megi>
clementp[m]: depends on the board/setup, my Orange Pi 3 is running at 1.8GHz@65°C all the time when used with a fan (and no heatsink)
<clementp[m]>
megi: Ok, 1.6 and 1.7 is still usefull so my V2 patch is wrong I added the wrong Orange Pi board :(
<megi>
people who worry about the frequent frequency changes may change the top frequency via sysfs at runtime
<megi>
ah
<clementp[m]>
You can set a frequency which is not in the OPP table ?
<megi>
no
<megi>
you can limit what OPP DVFS will use
<clementp[m]>
If you set the frequency manually and reach the temperature, the Kernel will change it for you
<megi>
via cpupower tool for example
<megi>
I meant that if people don't like that badly cooled board heats up too quickly, and then throttles a lot, they can limit the OPPs cpufreq will use via cpupower frequency-set --max 1.4GHz or whatever
<clementp[m]>
ha yes agreen, you can set the max
<clementp[m]>
but I you board can handle 1.6 or 1.7 but can't for 1.8
<megi>
I'm not sure what you mean...
<clementp[m]>
actually only 1.5GHz and 1.8GHz are available
<megi>
yes
<clementp[m]>
my board was throlling between these 2 values
<clementp[m]>
now that I added 1.6 and 1.7
<megi>
ok
<clementp[m]>
it's now throlling slower between 1.5 and 1.6
<clementp[m]>
I think it's better to add these 2 steps no ?
<megi>
I have no idea. It seems that you can get better performance by throttling between 1.8 and 1.5, than between basically two almost identical frequencies that are much lower
<megi>
but it would have to be tested
<clementp[m]>
but you will stay 2% of the time at 1.8GHz and 98% at 1.5
<megi>
some boards may just as well throttle between 1.8 and 1.7
<clementp[m]>
yes
<megi>
which would be better
<megi>
yeah
<clementp[m]>
Also the temperature is increasing really really fast at 1.8GHz
<clementp[m]>
whereas it's slowly increasing at 1.6
<megi>
yes, it needs a better cooling, especially if you have steady load
<megi>
my Opi3 idles at 60°C at 1.8GHz
<megi>
with no cooling
<megi>
it will handle bursty load with better performace without overheating
<megi>
all this is just a question of what perf tuning people want to do
<megi>
anyway, feel free to drop the 1.8GHz OPP if you think that's better
<megi>
maybe you can mark it as turbo-mode, so that people can enable it via boost mode at runtime?