Hi notro
notro wrote:fbtft never was a good fit for these keidei displays, but it's successor tinydrm has a much better modularity.
Oh, I've never heard about it, need to check it
notro wrote:
I don't have a keidei displays myself, and I certainly don't want one, but the hacker/maker spirit shown in this thread has spurred me to make it very easy to write a keidei driver that can support multiple versions of the display.
Hahaha, u're right - you certainly don't want the spi one

Anyway, I don't see them so much now, there is much more small tft displays with spi interface with proper(compatible) fbtft spi interface (spi to parallel

)
AS far as I remember, kedei don't change the I/F (3 or 4 in chain SIPO registers) , but for better pcb routing they changed in each version signals locations at shift registers outputs, or they doing a strange things to the display signals
notro wrote:
I have looked at some code on @saper_2's github repo and put together a keidei skeleton driver. It probably won't work as-is, but I'm quite certain that some people in this thread should be able to make it work.
My code works only for v1 or v2 , for later versions - they made too many changes in hardware

, and there is no inits.
For V5
Conjur did great job of: recording init sequence, and writing code for displaying images
notro wrote:I see some mention of i2c here, does some versions of the display use i2c?
No, just some people have problems with i2c interface on sys-images from kedei.