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
vicencb has quit [Quit: Leaving.]
_whitelogger has joined #linux-rockchip
vstehle has quit [Ping timeout: 244 seconds]
cnxsoft has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
tlwoerner has quit [Quit: Leaving]
tlwoerner has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
asciilifeform has left #linux-rockchip [#linux-rockchip]
_whitelogger has joined #linux-rockchip
vstehle has joined #linux-rockchip
rperier has quit [Quit: No Ping reply in 180 seconds.]
vagrantc has quit [Quit: leaving]
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
rperier has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
jelly has quit [Quit: ""]
jelly-home has joined #linux-rockchip
lkcl has joined #linux-rockchip
BenG83 has joined #linux-rockchip
<eballetbo> rc1 out! Time for some tests ...
<eballetbo> maz: any clue on this https://hastebin.com/awojatibey.cs It is triggered when I shutdown the machine.
<eballetbo> ups, is not here ... mmind00 ^
<mmind00> eballetbo: maz is on holiday if I remember #armlinux correctly ... does it change anything if you revert the 2 new iommu commits from 2 days ago?
<mmind00> eballetbo: I still need to run -rc1 through my boards today
<eballetbo> mmind00: yep, WARNING gone with the latest 2 new iommu commits
<mmind00> eballetbo: aaaah ... devm is falling on our toes
<mmind00> eballetbo: or not devm itself
<mmind00> eballetbo: but rk_iommu_shutdown does force_suspend and should possibly also disable the irq beforehand?
<mmind00> eballetbo: https://bpaste.net/show/4f3f5766ec29 seems to have helped me on pinky
<eballetbo> nice, will test in a minute
<mmind00> I'm off to lunch meanwhile ... see you in a bit :-)
<eballetbo> mmind00: yeah, that seems to help
aalm has quit [Ping timeout: 268 seconds]
vicencb has joined #linux-rockchip
<mmind00> eballetbo: great to see, so I guess I'll submit that as patch
<eballetbo> go ahead :)
<eballetbo> Thanks for the patch, now only one warning needs to be fixed :)
matthias_bgg has quit [Ping timeout: 252 seconds]
vicencb has quit [Quit: Leaving.]
<mmind00> eballetbo: you seem to be the bearer of bad news today :-P ... but that one I also saw during the merge window
<mmind00> eballetbo: interestingly that seems to be limited to kevin for me ... the aarch64 rock64 (rk3328) does not print this warning
afaerber has joined #linux-rockchip
<eballetbo> interesting
<eballetbo> oh, not bad news, common and usual news after rc1 :P
<mmind00> but I do like -rc1's without them better :-D
aalm has joined #linux-rockchip
<mmind00> eballetbo: btw. thanks a lot for testing on newer kernels :-)
matthias_bgg has joined #linux-rockchip
vicencb has joined #linux-rockchip
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
hunderteins has quit [Quit: TinyIRC 1.1]
JohnDoe_71Rus has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
return0e has quit [Remote host closed the connection]
BenG83 has quit [Quit: Leaving]
return0e has joined #linux-rockchip
return0xe has joined #linux-rockchip
return0e has quit [Ping timeout: 244 seconds]
jelly-home is now known as jelly
aalm has quit [Ping timeout: 276 seconds]
afaerber has quit [Quit: Leaving]
vagrantc has joined #linux-rockchip
<Esmil> Hmm.. I can't seem to get 4.19-rc1 booting on my kevin. I get a null pointer deref in dw_mci_request_end
<Esmil> eballetbo: do you have a kernel config I can look at and compare to mine?
JohnDoe_71Rus has quit [Ping timeout: 252 seconds]
matthias_bgg has quit [Quit: Leaving]
<Ke> Esmil: did you accidentally disable CROS_EC_SPI on oldconfig
<Ke> not sure, if that would break the boot, but somehow I had it off after oldconfig
<Ke> where would one get driver for simple-sound-card
<Ke> nvm sound/soc/generic/simple-card.c:
<Ke> my hacker script is broken
<Esmil> Ke: no, I noticed that change, but thanks
anarsoul|2 has joined #linux-rockchip
aalm has joined #linux-rockchip
afaerber has joined #linux-rockchip
rasta234 has joined #linux-rockchip
<rasta234> hello beeble
<rasta234> you may remember me from yesterday... I am the guy of the Yundoo Y8
<rasta234> today I made some progress, got the HDMI on but later on, there is a problem with dwmmc_rockchip
<rasta234> and .. kernel panic
<rasta234> would you take a look to the boot log?
<rasta234> this is the log:
<rasta234> I accept anybody's help :-)
<rasta234> The thing is this: I have a Yundoo Y8 which doesn't have linux support. This TVBox seems to be very similar to firefly rk3399. latest build for the Y8 is an android 7.1 image. I extract its dtb and then the dts (for android) which looks almost exactly as Rockchip RK3399 Board rev2 (BOX) - rk3399-box-rev2-android-6.0.dts
<rasta234> but there is no linux version for this, so I made some changes using rk3399-firefly-linux.dts
<beeble> you could try disabling sdio0 (change status = "okay" to "disabled")
<rasta234> i'll try that one
<beeble> you will lose wifi if it's attached to sdio, but let's just start there and then move forward by checking if there are any reset pins etc you have to change. your decompiled dtb will help with that
<rasta234> this is the Y8 android dts: https://pastebin.com/X5maiK88
<rasta234> this are my progress with the firefly linux dts: https://pastebin.com/8qkpvX9R
<beeble> the wifi power enable pin is different as far as i can see. so you will have to change that
<beeble> you have to match the pin assignment to your hardware. that is a bit painful as you have to trace the numerical entries in the decompiled dts
<beeble> but without schematics there is no other way
<beeble> but let's see if you get any further with sdio disabled
<rasta234> I'm compiling now
<rasta234> what is the code for "wifi power enable pin", I am nor very familiar with all this... so I need a hint to locate it in the dts file :-)
<beeble> if i guess correctly your timezone is PDT, if so you are a bit unlucky as i'm 9 hours behind and have to go soon
<beeble> hmm, maybe i was wrong, could be that it's the same pin. wifi-enable-h points to the same pin in both dts
<beeble> bit hard to say on a phone display :)
<rasta234> i am utc+2
<rasta234> I'm going also soon to dream a little bit
<rasta234> If you are in mobile, it is better to give up for today
<rasta234> tomorrow I promise to come back :-)
<rasta234> I need this box running a decent operating system... android is a joke
lkcl has quit [Ping timeout: 252 seconds]
<rasta234> BTW, wifi was initialized ok with the firefly kernel dtb before the modifications
<rasta234> thats the log for the Y8 booting with the firefly 3399 ubuntu 16.04 original image
rasta234 has quit [Quit: Page closed]
sphalerite has quit [Ping timeout: 264 seconds]
sphalerite has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
kaspter has quit [Remote host closed the connection]