else- has quit [Remote host closed the connection]
cnxsoft has joined #linux-rockchip
ganbold has joined #linux-rockchip
cnxsoft1 has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 240 seconds]
markm has quit [Ping timeout: 265 seconds]
utente_ has quit [Read error: Connection reset by peer]
naobsd has joined #linux-rockchip
premoboss has joined #linux-rockchip
premoboss has quit [Read error: Connection reset by peer]
mrueg has quit [Quit: No Ping reply in 180 seconds.]
<bashintosh>
hi naobsd, any idea if the firefly uses the display timings found in arch/arm/boot/dts/lcd-box.dtsi for eDP out?
<bashintosh>
I can't test it yet as I am waiting for a eDP->MIPI board..
premoboss has joined #linux-rockchip
levd has joined #linux-rockchip
premoboss has quit [Read error: Connection reset by peer]
premoboss has joined #linux-rockchip
mrueg has joined #linux-rockchip
mrueg has quit [Client Quit]
premoboss has quit [Read error: Connection reset by peer]
premoboss has joined #linux-rockchip
mrueg has joined #linux-rockchip
markm has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 255 seconds]
<naobsd>
bashintosh: sorry, I don't have any eDP display. I think if _you_ use that dtsi, it will be used.
<naobsd>
btw I think "screen-type = <SCREEN_EDP>;" is for eDP
<naobsd>
well, I didn't say only screen-type need to be right. all parameter need to be right for your eDP display.
<naobsd>
I think there is not generic/universal lcd-XXX.dtsi
<naobsd>
you have to choose/prepare right one
<naobsd>
awfully busy :(
amstan has quit [Ping timeout: 246 seconds]
amstan has joined #linux-rockchip
amstan has joined #linux-rockchip
mrueg has quit [Ping timeout: 264 seconds]
AstralixNB has joined #linux-rockchip
mrueg has joined #linux-rockchip
mrueg has quit [Ping timeout: 256 seconds]
mrueg has joined #linux-rockchip
nashpa has quit [Ping timeout: 260 seconds]
nashpa has joined #linux-rockchip
levd1 has quit [Read error: Connection reset by peer]
levd has joined #linux-rockchip
wildea01 has joined #linux-rockchip
else- has joined #linux-rockchip
ssvb has quit [Ping timeout: 250 seconds]
levd1 has joined #linux-rockchip
levd1 has quit [Client Quit]
levd has quit [Ping timeout: 256 seconds]
naobsd has quit [Quit: naobsd]
nighty^ has joined #linux-rockchip
cnxsoft1 has quit [Quit: cnxsoft1]
premoboss has quit [Ping timeout: 244 seconds]
cnxsoft has joined #linux-rockchip
cnxsoft has quit [Remote host closed the connection]
cnxsoft has joined #linux-rockchip
_whitelogger____ has joined #linux-rockchip
c0d3z3r0 has quit [Remote host closed the connection]
c0d3z3r0 has joined #linux-rockchip
GriefNorth has joined #linux-rockchip
c0d3z3r0 has quit [Quit: quit]
c0d3z3r0 has joined #linux-rockchip
AstralixNB has left #linux-rockchip [#linux-rockchip]
naobsd has joined #linux-rockchip
ssvb has joined #linux-rockchip
dlezcano has quit [Ping timeout: 252 seconds]
dlezcano has joined #linux-rockchip
wildea01 has quit [Quit: leaving]
GTRsdk has joined #linux-rockchip
nighty^ has quit [Quit: Disappears in a puff of smoke]
GriefNorth has quit [Ping timeout: 246 seconds]
mrjay has joined #linux-rockchip
mrjay has left #linux-rockchip [#linux-rockchip]
mrjay has joined #linux-rockchip
arokux has quit [Remote host closed the connection]
<mrjay>
Does anybody working on usb phy for rk3066?
<mrjay>
i'm reusing my mk808 as a generic server and on mainline it's one thing that is missing to make it suitable for my needs
arokux has joined #linux-rockchip
<mmind00>
mrjay: not directly, but it should work the same as for the rk3288 ... I can try taking a look tomorrow
<mrjay>
mmind00: i would do that myself but I'm not a kernel developer :(. I know you are very busy but if you could find some time to look into that or post some info about problem (i know C a little) would be great
<mmind00>
mrjay: I'll try to take a look tomorrow ... the cortex-a9 socs got a little less love in the last time
<mrjay>
Yeap ... i see that in commits in linux repo. Also after some tests i can post mk808 working device tree. Would it be possible to also include it to mainline patches queue?
<mmind00>
mrjay: sure ... always nice to get more stuff from other people
<mrjay>
mmind00: great. This devices were very popular 2 years ago and deserve second chance in mainline kernel :)