nodebit has quit [Remote host closed the connection]
qeed has quit [Quit: Leaving]
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-sunxi
Sjurygg26 has joined #linux-sunxi
Gerwin_J has quit [Ping timeout: 240 seconds]
Sjurygg26 has quit [Remote host closed the connection]
IgorPec has joined #linux-sunxi
NccT has joined #linux-sunxi
clemens3 has quit [Ping timeout: 252 seconds]
Mr__Anderson has joined #linux-sunxi
NccT has quit [Remote host closed the connection]
gpiero10 has joined #linux-sunxi
<jonkerj>
I've been playing around with a kconfig for my h5 orange pi 0+2, taking the fdt compatibles list as an input to find the right config options
gpiero10 has quit [Remote host closed the connection]
<jonkerj>
I see that the FDT for the board has a /soc/timer@1c20c00 with a 'allwinner,sun4i-a10-timer' compatible, which isn't selected by the aarch64/arm64 config
<jonkerj>
I mean, the appropriate clocksource driver (CONFIG_SUN4I_TIMER) is only selected (and selectable) by arch/arm/mach-sunxi/Kconfig and/or COMPILE_TEST (which is obviously not what I want)
<jonkerj>
I am wondering if the node is superfluous in the DT or if the Kconfig system for ARM64 needs to select this
miasma has joined #linux-sunxi
<jonkerj>
the board seems to run fine without it, though
<ElBarto>
jonkerj: it isn't used as the arm generic timer is present too
<jonkerj>
makes sense
<ElBarto>
we (FreeBSD) use it as the source for timecounter as the generic timer is glitchy
<ElBarto>
it reminds me that I need to send patches for that, the compatible isn't correct
<jonkerj>
yw :-)
<jonkerj>
so in theory, I could trick arch/arm64/Kconfig.platforms to enable CONFIG_SUN4I_TIMER and have a less glitchy timer driver on H5
<ElBarto>
depend on the linux driver
<jonkerj>
what kind glitchyness do you guys experience btw?
<ElBarto>
the a10 timer have 64 bits counter that we used on FreeBSD, but it isn't available in >A20 iirc
<ElBarto>
so the driver might need some work
<ElBarto>
the counters glitch when they do rollover on a certain pattern
<ElBarto>
which causes a lot of different problem
<ElBarto>
weird ntp issue, callouts (function fired after a certain amount of time) being weird too etc ...
<jonkerj>
random unstableness
<jonkerj>
caused by a variety of timer-induced problems
<ElBarto>
right
clemens3 has joined #linux-sunxi
<ElBarto>
everything is now fine since we use the other timer for timecounter
<ElBarto>
we still use the arm generic timer for eventtimer, it seems ok
msimpson has joined #linux-sunxi
yann|work has quit [Ping timeout: 240 seconds]
diego_r has joined #linux-sunxi
LockeAnarchist1 has joined #linux-sunxi
LockeAnarchist1 has quit [Remote host closed the connection]
nuuuciano has quit [Ping timeout: 240 seconds]
nuuuciano has joined #linux-sunxi
<wens>
so in linux parlance the arch timer could be used as a timer, but not a clocksource
<ElBarto>
which arch timer ? the allwinner one ?
BroderTuck has joined #linux-sunxi
mhlavink has quit [Ping timeout: 240 seconds]
<ElBarto>
also mind share why ? just for my general knowledge :)
<BroderTuck>
Speaking of misbehaving timers, a quote from the slackware-arm changelog: "Reverted to the 4.17 branch. Unfortunately 4.18 was unstable on the OrangePi. In particular, the date was jumping 100 years and there were numerous Kernel panics."
Jak_o_Shadows26 has joined #linux-sunxi
feep_ has joined #linux-sunxi
Jak_o_Shadows26 has quit [Remote host closed the connection]
feep_ has quit [Remote host closed the connection]
<ElBarto>
BroderTuck: that's one of the issue you can encounter, but it also present in 4.17 since it's hardware-related so I don't know why they've reverted
<jonkerj>
just upgraded my (orange pi) H3 boards to 4.18.7, haven't seen such issues
<jonkerj>
(yet)
<ElBarto>
also only the A64 is glitchy
<ElBarto>
I guess there is a OrangePi board with A64
bsc has joined #linux-sunxi
Nahom has joined #linux-sunxi
Nahom has left #linux-sunxi [#linux-sunxi]
Nahom has joined #linux-sunxi
<BroderTuck>
Seems like the OrangePi Win is A64-based
bsc has quit [Remote host closed the connection]
<BroderTuck>
ElBarto: I also thought it sounded odd that there would be any difference between 4.17 and 4.18, that's why I brought it up here.
<ElBarto>
BroderTuck: I guess the panics that they saw were not time related, but it's not very clear
jaganteki has joined #linux-sunxi
Guest42181 has joined #linux-sunxi
<wens>
ElBarto: arch timer = arm generic timer
Guest42181 has quit [Remote host closed the connection]
<ElBarto>
wens: so I'm lost, why did you said that the arm generic timer couldn't be used as a clocksource ?
Nahom has quit [Ping timeout: 256 seconds]
<ElBarto>
(I guess clocksource in linux is just a counter right ?)
yann|work has joined #linux-sunxi
Nahom has joined #linux-sunxi
evand_ has joined #linux-sunxi
evand_ has quit [Remote host closed the connection]
<wens>
because of the a64 glitch?
<ElBarto>
ok sorry, just understood what you mean, not enough coffee this morning it seems
<ElBarto>
so yeah, I'll send patches soon to fix the DTS, I just need to confirm which SoC changed the a10-timer to *not* have the 64 bits counter
<ElBarto>
based on the datasheet it seems to be the A23
<ElBarto>
but since I don't have such hardware I don't know
clemens3 has quit [Remote host closed the connection]
jaganteki has quit [Ping timeout: 256 seconds]
clemens3 has joined #linux-sunxi
Nahom has quit [Ping timeout: 256 seconds]
<wens>
64 bits counter?
<ElBarto>
A10 timer have 64 bits counter (CNT64_* in the user manual)
<wens>
I don't think we ever used it
<ElBarto>
that's what the FreeBSD developer used 5/6 years ago when he ported FreeBSD on A10
<ElBarto>
and that's how I found out that they aren't present on later SoC :)
<wens>
it's incorrect to use it, since the memory region for the timer doesn't even cover those registers
<wens>
FYI the registers were moved to the CPUCFG part starting with the A20
<ElBarto>
damn you're right, I guess it was from back in the day when we have our own dts
<ElBarto>
and since I haven't booted my A10 board in 2 years I've never noticed this
m4ssi has joined #linux-sunxi
aballier has quit [Ping timeout: 240 seconds]
aballier has joined #linux-sunxi
Guest97741_10 has joined #linux-sunxi
Guest97741_10 has quit [Remote host closed the connection]
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-sunxi
binia20 has joined #linux-sunxi
binia20 has quit [Remote host closed the connection]
ghuntley13 has joined #linux-sunxi
pmpp has joined #linux-sunxi
ghuntley13 has quit [Remote host closed the connection]
pmpp_ has quit [Ping timeout: 245 seconds]
pmpp has quit [Client Quit]
pmpp has joined #linux-sunxi
nixen17 has joined #linux-sunxi
pmpp has quit [Client Quit]
nixen17 has quit [Read error: Connection reset by peer]
pmpp has joined #linux-sunxi
lkcl has quit [Ping timeout: 260 seconds]
lkcl has joined #linux-sunxi
pmpp has quit [Client Quit]
pmpp has joined #linux-sunxi
Nahom has joined #linux-sunxi
<Nahom>
Hello
<Nahom>
I have a bunch of Mele M3 devices and have put linux on them
pmpp has quit [Client Quit]
<Nahom>
But haven't managed to get get wifi driver installed
<Nahom>
It is RTL8188ETV. Anyone has any ideas?
pmpp has joined #linux-sunxi
pmpp has quit [Client Quit]
pmpp has joined #linux-sunxi
pmpp has quit [Client Quit]
pmpp has joined #linux-sunxi
matthias_bgg has joined #linux-sunxi
pmpp has quit [Client Quit]
afaerber has joined #linux-sunxi
pmpp has joined #linux-sunxi
<karlp>
yeah, find something with better wifi hardware?
<karlp>
better than 8189etv...
<KotCzarny>
why sticking realtek
<KotCzarny>
*to
pmpp has quit [Client Quit]
Andy-D has joined #linux-sunxi
pmpp has joined #linux-sunxi
<karlp>
because it's whats on the mele m3 hardware
<karlp>
more than the price of the opi zero+ entirely.
<KotCzarny>
it all depends what is your target
<KotCzarny>
for bpi-r1 having stable wifi(+ap functionality) is important, and 8192cu is ulti-crap
pmpp has joined #linux-sunxi
<KotCzarny>
so just grab any decent usb wifi dongle and forget
habbah21 has quit [Remote host closed the connection]
<KotCzarny>
rt5370 is ~2-3usd
<KotCzarny>
and for me it works nicely as an ap in one location
enrico_ has joined #linux-sunxi
<karlp>
isthat rt28xx or mt76 driver?
<KotCzarny>
rt28xx
<KotCzarny>
you have to check what chipset is inside
<KotCzarny>
chinese sell the same package with them mixed randomly
<karlp>
yeah, buying usb dongles is a wildcard.
<KotCzarny>
on the plus side i got one mt7601u for free thanks to aliexpress refund
<karlp>
especially if you want to use them in AP mode.
pmpp has quit [Client Quit]
netg2 has joined #linux-sunxi
matthias_bgg has quit [Ping timeout: 268 seconds]
alm_ has joined #linux-sunxi
pmpp has joined #linux-sunxi
netg2 has quit [Remote host closed the connection]
<Nahom>
Ok, I guess I will look for a wifi dongle
<Nahom>
I have managed to put the mainline kernel and used a Ubuntu 18.04 rootfs. I have written it up in a medium article. Would that be useful to anyone?
pmpp has quit [Client Quit]
pmpp has joined #linux-sunxi
pmpp has quit [Client Quit]
alm_ has quit [Quit: Page closed]
pmpp has joined #linux-sunxi
<Nahom>
Ok, I have another question. The mainline kernel I used is 4.19... but when I try to install kernel-headers from apt, it only gives me 4.15 ones. How can I sync these up?
<KotCzarny>
apt-get remove linux* ?
<KotCzarny>
or just ignore
<KotCzarny>
most things dont crash
<KotCzarny>
and external modules look in /lib/modules/*/build anyway
pmpp has quit [Client Quit]
pmpp has joined #linux-sunxi
<fALSO>
download the kernel sources ?
<KotCzarny>
he used 4.19 so guessing he built it himself
<Nahom>
yes built it
pmpp has quit [Client Quit]
rexxster has quit [Remote host closed the connection]
pmpp has joined #linux-sunxi
Guest64928 has joined #linux-sunxi
Guest64928 has quit [Remote host closed the connection]
pmpp has quit [Client Quit]
pmpp has joined #linux-sunxi
pmpp has quit [Client Quit]
pmpp has joined #linux-sunxi
pmpp has quit [Client Quit]
pmpp has joined #linux-sunxi
f11f12 has joined #linux-sunxi
afaerber has joined #linux-sunxi
pmpp has quit [Client Quit]
pmpp has joined #linux-sunxi
pmpp has quit [Client Quit]
pmpp has joined #linux-sunxi
pmpp has quit [Client Quit]
pmpp has joined #linux-sunxi
<dgp>
nahom: If you want kernel headers packager you need to use the debian tool to build the kernel
PatrickC_1 has quit [Remote host closed the connection]
vagrantc has quit [Quit: leaving]
f11f12 has quit [Quit: f11f12]
f0xx has quit [Ping timeout: 252 seconds]
tlwoerner has quit [Ping timeout: 260 seconds]
jstein_ has joined #linux-sunxi
jstein_ is now known as jstein
iamfrankenstein has joined #linux-sunxi
tlwoerner has joined #linux-sunxi
yann|work has quit [Ping timeout: 272 seconds]
<dgp>
The mainlining page on the wiki says that ethernet support for the v3s went into 4.13 but it doesn't seem to be in 4.18. Are the patches for it in a repo somewhere?
Mr__Anderson has quit [Remote host closed the connection]
jstein has quit [Quit: quit]
yann|work has joined #linux-sunxi
Putti has quit [Ping timeout: 252 seconds]
Spike29 has joined #linux-sunxi
Spike29 has quit [Remote host closed the connection]
trisk11 has joined #linux-sunxi
iamfrankenstein has quit [Ping timeout: 268 seconds]
trisk11 has quit [Remote host closed the connection]