<unsolo>
so just calling mutex lock from galcore fails.
<unsolo>
but i will see what i can make of it
<unsolo>
its just a single call so i guess i will make it call mutex_lock_nested instead of just mutex lock
<unsolo>
since mutex lock is now just a simple #define of a mutex_lock_nested with args 0
<dv_>
hm perhaps you can collaborate with somebody here
<dv_>
there are a lot of imx6 projects, several of them are duplicates, or almost duplicates
<dv_>
its all quite fragmented
<dv_>
I know of two kernel projects: jnettlet's kernel (the one I linked to) and rmk's 3.14 kernel, which amongst other things takes parts of jnettlet's kernel and tries to make them upstreamable
<unsolo>
its fragmented because there is way to little effort to mainline things ;)
<unsolo>
hmm it actually is a deadlock..
<unsolo>
fun
<unsolo>
gckOS_GetPhyscicalAddress calls mutex lock whilst executed within a mutex lock
<unsolo>
<-- removes the lock for the fun of it
<unsolo>
lol kernel booted now but X resulted in yet another nested lock
<unsolo>
the fact that it starts up X indicates i have successfully ported galcore to 3.13.. provided i fix this locking issue
codinho_ has quit [Ping timeout: 258 seconds]
josh-adtec_ has quit [Ping timeout: 250 seconds]
bfederau has quit [Remote host closed the connection]
bfederau has joined #imx6-dev
<unsolo>
slap self
<unsolo>
CONFIG_DEBUG_MUTEXES=y and no galcore driver for you my friend