ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | Wiki at http://linux-rockchip.info | Logs at http://irclog.whitequark.org/linux-rockchip | ML at http://groups.google.com/group/linux-rockchip
naobsd has joined #linux-rockchip
BorgCuba has quit [Quit: leaving]
cnxsoft has joined #linux-rockchip
naobsd has quit [Remote host closed the connection]
luke-jr_ has joined #linux-rockchip
sjoerd` has joined #linux-rockchip
Luke-Jr has quit [*.net *.split]
Danukeru has quit [*.net *.split]
RayFlower has quit [*.net *.split]
sjoerd has quit [*.net *.split]
luke-jr_ is now known as Luke-Jr
RayFlower has joined #linux-rockchip
Danukeru has joined #linux-rockchip
markm has quit [Ping timeout: 256 seconds]
<philhug> anyone running mainline linux on the veyron/rk3288 chromebook?
<philhug> it hangs before printing anything on the usb uart
markm has joined #linux-rockchip
dlezcano has joined #linux-rockchip
gb_master has joined #linux-rockchip
GriefNorth has joined #linux-rockchip
rubensm has quit [Ping timeout: 244 seconds]
dlezcano has quit [Ping timeout: 255 seconds]
rubensm has joined #linux-rockchip
dlezcano has joined #linux-rockchip
dlezcano has quit [Ping timeout: 244 seconds]
markm_ has joined #linux-rockchip
libv_ has joined #linux-rockchip
libv_ is now known as libv
cnxsoft has quit [Ping timeout: 240 seconds]
cristian_c has joined #linux-rockchip
cristian_c has quit [Quit: Bye]
cristian_c has joined #linux-rockchip
ssvb has quit [Quit: Leaving]
premoboss has quit [Quit: Sto andando via]
JohnDoe_71Rus has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft has joined #linux-rockchip
cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft has joined #linux-rockchip
Robintel has quit [Quit: Connection closed for inactivity]
markm_ has quit [Ping timeout: 250 seconds]
markm has quit [Ping timeout: 250 seconds]
cnxsoft has quit [Quit: cnxsoft]
JohnDoe5 has joined #linux-rockchip
ssvb has joined #linux-rockchip
JohnDoe_71Rus has quit [Ping timeout: 265 seconds]
JohnDoe5 has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/]
<mmind00> philhug: do you have the debug_ll enabled? ... mass production coreboots do not configure the uart clocks, so if debug_ll wants to print something, it get stuck
<philhug> mmind00: I just applied the patch from arch and don't see it configuring the clocks. thanks for the hint.
<philhug> trying now with debug_ll disabled
<philhug> mmind00: much better, thanks :)
<mmind00> philhug: great to hear :-)
gb_master has quit [Remote host closed the connection]
markm has joined #linux-rockchip
gb_master has joined #linux-rockchip
<c0d3z3r0> mmind00, rperier: hey guys, I got a kernel panic with current linux-next. looks like a problem with arc emac but I'm not sure. maybe you could have a look at this? http://pastebin.com/mAj10umD
cristian__c has joined #linux-rockchip
cristian_c has quit [Read error: Connection reset by peer]
<c0d3z3r0> mmind00: here comes another one :/ http://pastebin.com/59RB8JYd
<mmind00> c0d3z3r0: looks like arc_emac_poll does something wrong? But I've never looked deep into the arc-emac so far
<c0d3z3r0> mmind00: hmm… rperier and naobsd had that problem in 9/2014 :S
<sjoerd`> c0d3z3r0: It's a someone known issue nobody really had time to look into afaik
<c0d3z3r0> sjoerd`: oh bad :( I had a short look at it but my kernel knowledge isn't that good
<gb_master> I guess you're talking about the skb_panic problem I was having with rk3188... sadly, afaik, it has never been solved and this made my radxa rock completely useless with the mainline kernel, as the eth makes it panic after a few secs. anyway, rperier was giving it a look back in the days
<c0d3z3r0> gb_master: the panic appears very randomly on high load as well as on idle state…. and the makes squeaky noises when receiving o.O :D
<gb_master> c0d3z3r0: I don't remember squeaky noises... anyway, my radxa panic'ed every single time after a few secs after booting
<gb_master> c0d3z3r0: as I needed the mainline kernel for other reasons, I had to switch to alternatives to rk3188
<c0d3z3r0> gb_master: which board do you have now?
<gb_master> rpi2... at least, is continuously supported. a thing that rockchip (and a lot of other companies), apparently, doesn't do
<gb_master> sadly, I don't know much about kernel dev, otherwise I would have tried to help. as long as this bug isn't fixed, radxa will be kept in its box
<c0d3z3r0> gb_master: same here
<gb_master> c0d3z3r0: I don't know if the dev on the rk3188 is still active here... as far as I saw, a lot of movement is going on rk3288 and further. hopefully, somebody will fix it someday
<c0d3z3r0> gb_master: I hope so.. I had some time for playing with barebox on the rock and my debian installer. today I was really happy that I got everything working but than …. kernel panic
<gb_master> c0d3z3r0: I really hope so. Things are going better with rk3288 and mainline?
<c0d3z3r0> gb_master: I don't have any rk3288 board. just rpi b, rpi 2 and radxa rock
<gb_master> c0d3z3r0: just like me. identical.
<c0d3z3r0> gb_master: odroid-xu4 looks nice
<gb_master> c0d3z3r0: if it's maintained/mainline, then it's already a GOOD point :)
<c0d3z3r0> gb_master: their current kernel at github is 4.2-rc1 … looks like they're doing the same sh*t as rockchip… https://github.com/hardkernel/linux/tree/odroidxu4-v4.2-rc1
<gb_master> c0d3z3r0: well, maybe it's "just" maintained, like with rpi
<c0d3z3r0> gb_master: don't the rpi people contribute to mainline?
<gb_master> c0d3z3r0: I have no idea... I guess, anyway, that rpi works already fine with the mainline
<gb_master> c0d3z3r0: I'm just guessing
<gb_master> c0d3z3r0: aaaaaaaaand you're right. and status is not that bad. as far as I remember, the video is still suffering in the mainline
<c0d3z3r0> gb_master: hmm looks like the odroid works with mainline, too. at least cpu, usb 3.0 and ethernet
<gb_master> c0d3z3r0: I have no idea. but I don't want to spend more money on this stuff. I'm fine with the rpi2 now and I hope I'll be able to use the rr soon
<c0d3z3r0> gb_master: yeah, it would be really great if someone could fix the ethernet on rr.
<gb_master> c0d3z3r0: rperier, you're our only hope :)
<c0d3z3r0> gb_master: I have to leave now cya
<gb_master> c0d3z3r0: enjoy
<mmind00> gb_master: just picking up the question from 21:28 ... yes our rk3288 support in mainline is a lot better at the moment
<mmind00> gb_master: mainly due to the big effort coming from the Chromebook project
nighty^ has quit [Quit: Disappears in a puff of smoke]
<philhug> mmind00: I guess it's best if I track your for-next branch for veyron-speedy?
<mmind00> philhug: depends on what you want to do ;-) ... my "for-next" feeds directly into the linux-next tree together with all other maintainer-trees ... but that doesn't give you output on the internal display yet [display-port driver is still in flight]
<mmind00> philhug: for other cases there is https://github.com/mmind/linux-rockchip/tree/devel/somewhat-stable (together with the rk3288_veyron_defconfig in there) will also get you output on the display
<mmind00> philhug: thankfully the dp driver is the only real difference between my dev-tree and mainline nowadays
<philhug> I'm trying to figure out what's missing to add support to the official debian kernel.
<mmind00> philhug: nothing big if you can live with hdmi-only :-)
<philhug> yeah, that's what I figured..
<philhug> there just seem to be some issues with device tree in mainline
<philhug> e.g. only internal mmc works and the dwc usb controller seems to be broken
<philhug> but maybe it's caused by kernel config :) I'll try yours..
<mmind00> philhug: there seems to be more strange stuff ... i.e. all the cros-es error messages that shouldn't be there
<philhug> yeah, spi is broken too
<mmind00> philhug: also the dwmmc in your log wants to use PIO instead of the controller-internal DMA for whatever reason
<philhug> I guess .config issue then
GriefNorth has quit [Ping timeout: 246 seconds]
markm has quit [Ping timeout: 244 seconds]
gb_master has quit [Remote host closed the connection]
markm has joined #linux-rockchip
cristian__c has quit [Quit: Bye]