09:29 <dvergatal> mmind00: i have finally found the issue why optee greater than 3.7.0 is not starting but unfortunately i don't know how to fix it:P

09:32 <dvergatal> mmind00: the crux of matter is in the commit https://github.com/OP-TEE/optee_os/commit/520860f658be37b08f173b12db4594cc16351871 the have changed mmu initialization

09:33 <mmind00> dvergatal: wasn't there some config setting related to that?

09:33 <dvergatal> mmind00: i don't know

09:34 <dvergatal> mmind00: i've been checking commit by commit from the 3.7.0 which you helped me year ago to start and it was working for my for that time but etienne has finally merged his pkcs11 code into mainlien and it is quit frustrating to keep up my sources with the mainline

09:35 <dvergatal> my=me

09:35 <dvergatal> so i started to keep digging and yesterday have found that this commit is a regression

09:38 <dvergatal> mmind00: i've also asked jenswi in here https://github.com/OP-TEE/optee_os/issues/4977

09:39 <dvergatal> mmind00: from what i see there is no config setting to enable/disable it or maybe i'm blind

09:44 <mmind00> dvergatal: I jut remember glimpses of past discussions, and I do believe someone mentioned some config option changing the behaviour of that - I haven't touched optee in many months myself though [which will likely stay that way]

09:45 <dvergatal> mmind00: sure, config option for mmu?

09:45 <dvergatal> mmind00: here?

09:51 <mmind00> dvergatal: I don't remember the communication channel anymore - if it was this channel (still on freenode perhaps) or somewhere else

09:52 <dvergatal> dvergatal: ah ok thx anyway