<amstan>
micken: while i think the stuff is kept pretty secret for reasons i'm sure there's some information you can find given that a lot of other boards use it (like even the raspberry pi)
<amstan>
looks like risc os works on the rpi too
<micken>
amstan: ok , if the dwc2 is on rpi I am lucky
<amstan>
it is
<amstan>
that being said, there's probably still work to be done to get it working
<amstan>
like the phys, hooking it up to the rest of the soc, clocks, etc
<micken>
yea
<micken>
the physaddresses is in the TRM I guess
<amstan>
it's also in the linux kernel
<micken>
the rest is up to guessing
<micken>
linux kernel is a problem because of gpl
<amstan>
it's all in the linux kernel, in theory all you need to do is just copy what it does
<amstan>
not really sure what counts as gpl if all you're looking at is memory addresses and what to put into them to get it working
<micken>
yea could work
<amstan>
anyway, ianal
nighty-- has joined #linux-rockchip
nighty-- has quit [Remote host closed the connection]
nighty-- has joined #linux-rockchip
wzyy2 has joined #linux-rockchip
wzyy2 has quit [Quit: Konversation terminated!]
<micken>
amstan: thanks for your help
<micken>
amstan: one more thing
<micken>
amstan: do you know which UART is exposed on the UART pins on the tinker board?
<Tef61>
micken: How's your experience so far with the Ticker board? What are you using it for?
<micken>
Tef61: getting it tomorrow
<micken>
Tef61: porting risc os to it
<stdint>
micken, same pin as rpi
<micken>
So I am basicly doing a board bringup this night
<micken>
stdint: sorry but does that mean UART0?
<stdint>
micken, yes
<micken>
stdint: great , then I have it right
<stdint>
the default u-boot shipped with asus would use that pin
<micken>
ok
<micken>
I am actually relying on it being setup by u-boot
<micken>
3:31am
<micken>
sigh
<micken>
got to get some sleep
<stdint>
go night
lkcl has joined #linux-rockchip
wzyy2 has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
<wzyy2>
Have try weston with atomic modesetting and gstreamer 1.12 today. ;)
<wzyy2>
It's really cool to see we can get such a thing like android HWC in GNU/Linux.
<naobsd>
meta-rockchip?
<wzyy2>
No need to worry about the playback speed, compositor-drm in weston can use drm overlay plane to draw dmabuf.
<wzyy2>
yep, i try it in meta-rockchip, by change weston to this.
<wzyy2>
Wonder if it's possible to take use of rga in compositor-drm.
<naobsd>
yocto with rk3288 is very interesting
<wzyy2>
Yeah, i like yocto, it's customizable and make it easy for me to do experimenters.
<naobsd>
I want to try to run linux on my rk3288 VR too
<naobsd>
I need to make some patch to support unknown 2K mipi lcd ;)
kever has quit [Read error: Connection reset by peer]
kever has joined #linux-rockchip
arnd has quit []
arnd has joined #linux-rockchip
cnxsoft has quit [Remote host closed the connection]
cnxsoft has joined #linux-rockchip
<wzyy2>
\o/ Finally we can get rid of horrible x11.
<wzyy2>
Weston work so well ---- When something was moved on top of drm plane, it will back to GPU composition.
<Tef61>
naobsd: You do anything with VR?
<Myy>
So the only thing remaining with wayland is to be able to run others compositors, I guess ? :)
<naobsd>
wzyy2: congrats :)
JohnDoe_71Rus has joined #linux-rockchip
<naobsd>
Tef61: I just bought VR device with rk3288
<wzyy2>
compositors-drm with atomic support are good enough to use , just wait it be merged in main weston branch and i could based on it to do a little modfied for rockchip platfrom.
techping has quit [Remote host closed the connection]
cnxsoft has quit [Ping timeout: 240 seconds]
cnxsoft has joined #linux-rockchip
cnxsoft has quit [Client Quit]
wzyy2 has quit [Ping timeout: 240 seconds]
wzyy2 has joined #linux-rockchip
tlwoerner has quit [Quit: Leaving]
tlwoerner has joined #linux-rockchip
tlwoerner has joined #linux-rockchip
LongWork has quit [Read error: Connection reset by peer]
LongWork has joined #linux-rockchip
wadim_ has quit [Remote host closed the connection]
paulk-collins has joined #linux-rockchip
<ayaka>
naobsd, I don't know you could read Chinese
<ayaka>
anyway, I have hear that the upgrade android of the px3
<ayaka>
but if you want to use the px3se, I would be happy
<ayaka>
since it is linux system
<naobsd>
ayaka: I cannot read Chinese ;)
<naobsd>
linux system? that page says it's Android 7.1...
<ayaka>
px3 and px3 are different chip
<ayaka>
px3se
<naobsd>
px3 is similar to rk3188. what's px3se? rk3036?
<ayaka>
rk3128
<naobsd>
ah
<ayaka>
it supports hevc decoder
<ayaka>
but the cpu is more wake
<naobsd>
px3 is for higher performance?
<naobsd>
I surprised that Cortex-A9 based SoC is still maintained ;)
<ayaka>
I don't touch the android products, I can't give you an answer
<ayaka>
the kernel would be still 3.10, won't be 4.4
<naobsd>
3.0?
<ayaka>
3.10
<ayaka>
oh, I forget there is kernel 3.0, ok those kernel are dropped
<naobsd>
oh, it's great evolution ;)
<naobsd>
my previous work was rk3168 with 3.0 kernel... ;)
<naobsd>
(I left that project, happily)
<naobsd>
ah
<naobsd>
I still need to do something for rk3066/3.0 for chirimen... but it's not the job, just hobby
wzyy2 has quit [Ping timeout: 240 seconds]
wzyy2 has joined #linux-rockchip
lkcl has quit [Ping timeout: 272 seconds]
lkcl has joined #linux-rockchip
wzyy2 has quit [Ping timeout: 240 seconds]
nighty-- has quit [Quit: Disappears in a puff of smoke]
cyteen has quit [Ping timeout: 255 seconds]
afaerber has quit [Quit: Leaving]
cyteen has joined #linux-rockchip
lkcl has quit [Ping timeout: 255 seconds]
Myy has joined #linux-rockchip
<Myy>
miaou
<ayaka>
Myy, I am suffering from the power problem as well
<ayaka>
it seems that I don't have a proper way to offer the power to vpu power domain
<Myy>
I'll try to investigate this today. Meanwhile, I'm trying to finish the first version of my Graphical Assembler ( http://bit.ly/2qWsL2G ) so I didn't progress that much, besides locating the problem
<Myy>
That said, I see that the power on code use atomic_read calls
<Myy>
There might some issues related with the new refcount code. Some atomic_read were also replaced by another call in the 4.11 series
<ayaka>
the problem I meet is not the atomic read
<ayaka>
just pm_runtime related
cwd has joined #linux-rockchip
<Myy>
I've added some debugging printk and when reading power_on_cnt, the systems receives : 3408904758
<Myy>
I guess that the variable isn't set to 0 at first ?
<Myy>
I'll paste what I got on dmesg with my debugging messagse added
lkcl has joined #linux-rockchip
<Myy>
Turns out that using the wrong printk format borks out the whole message
<Myy>
So, power_on_cnt is really set to 0 on powerup
<Myy>
Meanwhile, I guess I'll just add all the RK3288 DTB files to my patched mainline kernel repo
<micken>
test program http://www.update.uu.se/~micken/test_uart.S , not so skilled in GAS, I use ARM syntax normaly. I just took for granted that u-boot on RK3288 doesn't destroy uart config when launching a binary with "go address" ..
<micken>
that is the normal behavior
<micken>
I don't get why it crash when I write a byte to UART2
<Myy>
What's the generated code though ? (objdump -d)
<micken>
can I paste?
<Myy>
If that's not too long, yeah. Else ghostbin.com