ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log http://irclog.whitequark.org/linux-rockchip | Community GH https://github.com/linux-rockchip | Rockchip GH https://github.com/rockchip-linux | ML https://groups.google.com/group/linux-rockchip
tllim has joined #linux-rockchip
perr has quit [Remote host closed the connection]
perr has joined #linux-rockchip
nighty- has joined #linux-rockchip
nighty- has quit [Max SendQ exceeded]
tllim has quit [Quit: Leaving]
nighty- has joined #linux-rockchip
perr has quit [Remote host closed the connection]
nighty- is now known as nighty
nighty is now known as nighty--
nighty-- is now known as nighty-
libv has joined #linux-rockchip
libv_ has quit [Ping timeout: 265 seconds]
lurchi__ is now known as lurchi_
cnxsoft has joined #linux-rockchip
Xal1u5 has quit [Ping timeout: 256 seconds]
return0e has joined #linux-rockchip
anarsoul has quit [Ping timeout: 245 seconds]
Kamikaze84 has joined #linux-rockchip
<Kamikaze84> Hi again all. I'm thinking about submitting this as a patch to the linux-rockchip mailing list (after first making sure it applies against latest mainline rk3399-firefly.dts). Before I do that, I was hoping someone with another firefly RK3399 might try the patch to see if it works for them. I'm especially interested as I've heard some Firefly RK3399 boards already work fine with the existing DTS, but mine (like some others a
<Kamikaze84> * a patch, I was hoping someone that has a working Firefly RK3399 board could try it with their mainline kernel to make sure it doesn't regress on their setup, otherwise the patch is useless. I must obviously note I can't be responsible if it messes up your board. I'm only a tinkerer who likes playing with various hardware and getting it setup the way I want.. Anyway my patch is here:
<Kamikaze84> If anyone is able to try it and confirm that it works, that'd be helpful. I'd then submit to linux-rockchip mailing list and see if they will add it to their tree and submit to mainline in PR at some stage.
ujerry__ has joined #linux-rockchip
ujerry_ has quit [Ping timeout: 268 seconds]
lurchi__ has joined #linux-rockchip
lurchi_ has quit [Ping timeout: 248 seconds]
vstehle has joined #linux-rockchip
ujerry__ has quit [Read error: Connection timed out]
ujerry__ has joined #linux-rockchip
anarsoul has joined #linux-rockchip
anarsoul|3 has quit [Ping timeout: 245 seconds]
ujerry__ has quit [Ping timeout: 240 seconds]
ujerry__ has joined #linux-rockchip
Easyfab has joined #linux-rockchip
lurchi__ has quit [Quit: Konversation terminated!]
lurchi__ has joined #linux-rockchip
<Kamikaze84> I'll be back another time to ask too... on the off chance someone tests it and wants to leave a message that they've tested it, I can always check on the irc.whitequark.org site to see messages I might have missed.
<Kamikaze84> thanks
Kamikaze84 has quit []
cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft1 has joined #linux-rockchip
cnxsoft1 is now known as cnxsoft
xerpi has joined #linux-rockchip
fysa has joined #linux-rockchip
kaspter has joined #linux-rockchip
nOOb__ has quit [Ping timeout: 244 seconds]
LargePrime has quit [Ping timeout: 256 seconds]
nOOb__ has joined #linux-rockchip
LargePrime has joined #linux-rockchip
return0e has quit [Ping timeout: 260 seconds]
Xal1u5 has joined #linux-rockchip
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-rockchip
ujerry__ has quit [Quit: Leaving]
Easyfab has quit [Quit: Leaving]
lukasz_ has joined #linux-rockchip
mateo` has quit [Ping timeout: 260 seconds]
return0e has joined #linux-rockchip
mateo` has joined #linux-rockchip
ganbold has joined #linux-rockchip
lukasz_ has quit [Ping timeout: 245 seconds]
return0e_ has joined #linux-rockchip
return0e has quit [Ping timeout: 265 seconds]
lukasz_ has joined #linux-rockchip
return0e has joined #linux-rockchip
xerpi has quit [Quit: Leaving]
return0e_ has quit [Ping timeout: 256 seconds]
nOOb__ has quit [Quit: Leaving]
LargePrime has quit [Ping timeout: 265 seconds]
perr has joined #linux-rockchip
Kamikaze84 has joined #linux-rockchip
LargePrime has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
perr has quit [Quit: Leaving]
xerpi has joined #linux-rockchip
Kamikaze84 has quit [Quit: Page closed]
panicking has joined #linux-rockchip
<panicking> Hi all
<panicking> playing a bit with yocto, and I have some problem on testing gstreamer
<panicking> stable version pyro. I have some failing video and some not rendering one. What is the correct way to play video?
<panicking> gst-launch-1.0 uridecodebin uri=file:///mnt/Men_in_Black_\[m1080p\]_\(1997\)_.mp4 ! rkximagesink
indy has quit [Read error: Connection reset by peer]
<panicking> gst-play-1.0 file:///mnt/Alien_Covenant_2017_4K.UHD.2160p.BDRip_Ita_Eng_x265-NAHOM.mkv video=rkximagesink
<panicking> this is an alternative way but this video dump
<panicking> somehow
indy has joined #linux-rockchip
adj__ has joined #linux-rockchip
adj_ has quit [Ping timeout: 268 seconds]
xerpi has quit [Quit: Leaving]
fysa has quit [Remote host closed the connection]
Omegamoon has joined #linux-rockchip
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-rockchip
Omegamoon has quit [Quit: Leaving.]
fysa has joined #linux-rockchip
<fysa> how can I force the video mode for a rock64? whenever I use rkmpv to play a video, it forces the screen mode to 4k@30hz even though my xorg config doesn't have 4k as an option.. I think I need to force the fbdev mode at boot to 1080p also?
<fysa> or can I ban a resolution?
<fysa> maybe .. drm_kms_helper.edid_firmware=edid/1920x1080.bin
<fysa> or maybe .. video=HDMI-A-1:1920x1080@120
<fysa> trying that first
lkcl has quit [Read error: Connection reset by peer]
fysa has quit [Remote host closed the connection]
lkcl has joined #linux-rockchip
fysa has joined #linux-rockchip
fysa has quit [Remote host closed the connection]
vagrantc has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
<ayufan> you should try to overwrite the edid
Omegamoon has joined #linux-rockchip
adj__ has quit [Remote host closed the connection]
adj__ has joined #linux-rockchip
lukasz_ has quit [Quit: Leaving]
panicking has quit [Remote host closed the connection]
gnufan has joined #linux-rockchip
Omegamoon has left #linux-rockchip [#linux-rockchip]
return0e has quit [Read error: Connection reset by peer]
return0e has joined #linux-rockchip
Xal1u5 has quit [Quit: Leaving]
return0e has quit [Read error: Connection reset by peer]
return0e has joined #linux-rockchip
return0e has quit [Read error: Connection reset by peer]
<adj__> asciilifeform, so on recent chromebooks the write protecting of firmware is the battery detect pin?
return0e has joined #linux-rockchip
<adj__> could malware write coreboot or depthcharge if the battery dies? I'm not sure if I really prefer this to the screw