narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - Publicly Logged on https://irclog.whitequark.org/linux-amlogic
tlwoerner_ has quit [Read error: Connection reset by peer]
sputnik__ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 246 seconds]
afaerber has quit [Quit: Leaving]
Darkmatter66 has quit [Ping timeout: 272 seconds]
Darkmatter66 has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 252 seconds]
Darkmatter66 has joined #linux-amlogic
_whitelogger has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 252 seconds]
Darkmatter66 has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 252 seconds]
Darkmatter66 has joined #linux-amlogic
wens has quit [Ping timeout: 245 seconds]
Ivanovic has quit [Quit: Caught sigterm, terminating...]
Ivanovic has joined #linux-amlogic
Ivanovic has quit [Client Quit]
Ivanovic has joined #linux-amlogic
sputnik__ has quit [Remote host closed the connection]
Ivanovic has quit [Read error: Connection reset by peer]
Ivanovic has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
sputnik__ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 252 seconds]
sputnik__ has quit [Read error: Connection reset by peer]
sputnik_ has joined #linux-amlogic
tlwoerner has joined #linux-amlogic
ldevulder_ has joined #linux-amlogic
default__ has quit [Ping timeout: 246 seconds]
Darkmatter66 has quit [Ping timeout: 252 seconds]
tlwoerner has quit [Remote host closed the connection]
tlwoerner has joined #linux-amlogic
Darkmatter66 has joined #linux-amlogic
tlwoerner has quit [Ping timeout: 268 seconds]
tlwoerner has joined #linux-amlogic
sputnik__ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 246 seconds]
sputnik__ has quit [Remote host closed the connection]
tlwoerner has quit [Ping timeout: 272 seconds]
default__ has joined #linux-amlogic
ldevulder_ has quit [Ping timeout: 252 seconds]
ndufresne has joined #linux-amlogic
tlwoerner has joined #linux-amlogic
Darkmatter66 has quit [Max SendQ exceeded]
Darkmatter66 has joined #linux-amlogic
<Lyude> Anyone know if it's possible to get uboot working for the khadas vim2 with working watchdog support?
tlwoerner has quit [Ping timeout: 252 seconds]
wens has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
Darkmatter66 has quit [Quit: ZNC 1.7.1 - https://znc.in]
Darkmatter66 has joined #linux-amlogic
Xogium has joined #linux-amlogic
<Lyude> sweet, figured it out: mw 0xc11098d0 0x3245dc0; mw 0xc11098dc 0x0; mw 0xc11098d8 0xFFFF
<xdarklight> Lyude: for mainline u-boot you can probably port the Linux watchdog driver to u-boot with little effort
<Lyude> xdarklight: I figured as much; but I don't really feel like possibly breaking uboot on this board since I think actually fixing that would require taking it out of it's case so I could join the right pins to get it into mregister mode
random_yanek has quit [Quit: random_yanek]
random_yanek has joined #linux-amlogic
random_yanek has quit [Max SendQ exceeded]
random_yanek has joined #linux-amlogic
<Lyude> So: does anyone know how one would go about controlling the fans on the vim2?
<Lyude> and additionally; has anyone actually got the emmc working on the vim2 with a mainline kernel?
<xdarklight> the first value of each tuple is the fan speed, the second value is the "level" (0 = off, ..., 3 = full speed)
<Lyude> ahhh; so am I supposed to modify those values? going off /* Dummy RPM values since fan is optional */
<xdarklight> yep (haven't tried it myself though since I don't have a fan for my VIM2)
<xdarklight> since there's only two GPIOs you're limited to four levels (0..3), so all that's missing is the correct fan speeds for each level for your specific fan
<Lyude> neat; I'll try it out. no daemons or anything needed in linux?
<xdarklight> shouldn't be needed AFAIK, the temperature targets are configured here: https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2.dts#L107
<Lyude> sorry for all the questions but; hitting another problem, it seems like every now and then the ethernet on this board will cut out in this strange way where it stops responding to RX, unless you do something to make the board do TX
<Lyude> in which case so long as the board is doing TX, RX works fine
<Lyude> but if it stops then it stops responding again'
<Lyude> chewitt/narmstrong: you seen anything like this? ^
<xdarklight> what kernel version are you running?
<xdarklight> there was an stmmac fix that affects all Amlogic SoCs (newer than Meson8)
<Lyude> xdarklight: 4.19rc7
<Lyude> if you've got any patches I can try them out
<xdarklight> hmm, 4.19-rc7 should already have 8fce3331702316d4bcfeb0771c09ac75d2192bbc
tlwoerner has joined #linux-amlogic
<Lyude> let me verify I've got that commit in this repo
<Xogium> very offtopic but, does anyone here knows if there is a wiki for mainline progress on porting SoC like armada-37xx to mainline ?
<Xogium> either kernel or u-boot, I mean
<Lyude> xdarklight: yep; looks like it's in my kernel
<Lyude> xdarklight: alright; will rebuild kernel (need to for unrelated reasons) and dtb and see how that goes
<xdarklight> original description why it was added to Odroid-C2: https://patchwork.kernel.org/patch/9528915/
<xdarklight> I'm calling it a day. good night!
<Lyude> thank you for the help xdarklight, you too!
<Lyude> xdarklight: btw for when you get back on, might be a bit too early to tell but I'm pretty sure I already see a dramatic difference on the ethernet performance with that option in the devicetree