adjtm has quit [Remote host closed the connection]
adjtm has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 256 seconds]
kevery1 is now known as kevery
maze-BUG has joined #linux-rockchip
maze-BUG1 has joined #linux-rockchip
maze-BUG has quit [Ping timeout: 260 seconds]
maze-BUG1 is now known as maze-BUG
armoon has joined #linux-rockchip
klokken has quit [Remote host closed the connection]
tuxd3v has quit [Quit: Leaving]
kevery has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
armoon has quit [Remote host closed the connection]
JohnDoe_71Rus has joined #linux-rockchip
vstehle has joined #linux-rockchip
maze-BUG has quit [Quit: maze-BUG]
kevery has quit [Read error: Connection reset by peer]
kevery1 has joined #linux-rockchip
kevery1 is now known as kevery
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 260 seconds]
kevery1 is now known as kevery
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 256 seconds]
kevery1 is now known as kevery
warpme_ has joined #linux-rockchip
maze-BUG has joined #linux-rockchip
maze-BUG has quit [Ping timeout: 240 seconds]
maze-BUG has joined #linux-rockchip
Ke has joined #linux-rockchip
<sphalerite>
maz: I added irqchip.gicv3_nolpi=1 to the firmware kernel as you suggested, unfortunately the OS kernel still can't talk to the wifi — I get "genirq: Flags mismatch irq 72. 00000088 (MRVL_PCIE) vs. 00000008 (wifi_wake)" and "mwifiex_pcie: request_irq failed: ret=-16"
maze-BUG has quit [Remote host closed the connection]
maze-BUG has joined #linux-rockchip
maze-BUG has quit [Remote host closed the connection]
maze-BUG has joined #linux-rockchip
maze-BUG has quit [Ping timeout: 265 seconds]
maze-BUG has joined #linux-rockchip
maze-BUG has quit [Remote host closed the connection]
<mps>
I have rk3399 gru-kevin samsung chromebook, alsa works but can't control it with alsamixer. controls are there but changing sliders or switches has no any effect
<mps>
do I need some special alsa setup or patches, anyone know?
<sphalerite>
mps: careful with those controls, you might fry your speakers
<maze-BUG>
But I really see the <project name="poky" path="yocto/poky" remote="yocto" revision="8cd3ee6e1a50ad9f40466bcadb236c619c42ef19" upstream="thud">
<maze-BUG>
But fetch error....
<mps>
sphalerite: yes, I read about that somewhere, but for now I'm safe because they don't work, they are always at some defaults. I use software controls in firefox and mpv
<mps>
but would be nice if could mute speaker and use headphones
maze-BUG1 has joined #linux-rockchip
stikonas_ has joined #linux-rockchip
maze-BUG has quit [Ping timeout: 250 seconds]
maze-BUG1 is now known as maze-BUG
klokken has joined #linux-rockchip
sb35 has joined #linux-rockchip
kevery has quit [Ping timeout: 250 seconds]
<sphalerite>
maze-BUG: that worked wonderfully, extremely happy I can access the internet from it without an adapter again! Thanks!
<maz>
sphalerite: I guess this was for me and not for maze-BUG... ;-) anyway, glad it is working. I'll try and revive this series at some point.
<sphalerite>
oops yes :)
<sphalerite>
maz: revive?
<maz>
sphalerite: the patch I gave you is just a hack. there is a bigger problem with the wifi DT binding that describe things that are incompatible with the PCI binding. and the whole wake-up over wifi is broken anyway. the series I liniked to above tries to solve a couple of these things. and given that it is over a year old, it needs reviving...
klokken has quit [Remote host closed the connection]
return0e has quit [Read error: Connection reset by peer]
return0e_ has joined #linux-rockchip
<nomis>
hi all. I am stuck in the woods regarding the boot process of a rk3328 based TV-Box. I am trying to build a yocto-image, but the thing I'm building just fails to boot, nothing happening on the serial port.
<nomis>
by shorting out the emmc clock pin I am able to upload rk3328_loader_v1.16.250.bin and then I am trying to flash the gpt image which is the result of the yocto build process.
<nomis>
I am a bit hazy about all the bootloader terminology (is that the SPL at 0x2000? Is that u-boot based as well?)
<nomis>
the u-boot that was on the original image for the tv box apparently was configured for the EVB-rk3328. Does U-Boot additionally need/use a device tree?
kevery has quit [Ping timeout: 250 seconds]
bshah has quit [Excess Flood]
bshah has joined #linux-rockchip
JohnDoe_71Rus has quit [Ping timeout: 256 seconds]