页次: 1
据说这个显示驱动,tcon0里的vsync中断触发只有40hz。
难怪感觉不流畅,不知怎么搞出来的
Steward says:
-------------
ok
it is hard to explain something
first
not all of screen has TE pinout
ex: v2 bittboy
second
the TE pin is open on PCB for some bittboys
so, for v1, you need short it manually
and
even though all of hardware are ready
the trigger rate is only 40hz in f1c500s
I mean TE is output around 60hz
but f1c500s only get 40hz in kernel driver
so, many issues
I dont know how to say that
but
if you fix your hardware, maybe, you can check kernel whether it is somgthing I overlooked
any question ?People says:
-------------
kernel gets 40Hz instead of 60Hz because it is too slow to process it or the signal got lost in hw, for example by lack of filtering or filtering too much?
i have bittboy v2.5Steward says:
-------------
we use oscilloscope to double check and hw can ouput 60hz
in kernel, I just accumulate and print it
and the result is 40hz
even though boost priority for innterrupt
the result is same as without boos priority
we also check with some engineers who developed f1c500s
they havent checked this when produce this ic
I mean no any verification with interrupt speed
so, I dont know whats the root cause
maybe, kernel or IC
if you know this, please tell me
thanks
kekemuyu 说:smartcar 说:https://github.com/steward-fu/miyoo
请问大神, 这个 miyoo链接 怎么玩?
司徒删除了所有源码,在github搜索miyoo还能收到很多其他人fork司徒的源码
都被我叉过来了:
https://github.com/qq516333132/f1c500s_kernel
https://github.com/qq516333132/miyoo
https://github.com/qq516333132/f1c500s_uboot
https://github.com/qq516333132/miyoo_src
https://github.com/qq516333132/miyoo_rel
没有.config啊。
前几天试过这个源码为基础,改改编译出来,替换显示驱动r61520fb.ko,结果停留在logo进不去。
零售版机器里ko反编译出来的struct和自己用它源码编译的struct,比如fb_info对应某些变量offset不一致,折腾几天了不知咋回事。
晕哥知道不?
司徒主页上其他掌机的资源也有些删掉了
页次: 1