You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No, progress here.
I was about to use a BusPirate to cature the SPI output of the two drivers that really should be identical. But then I rembered the 10MHz limit on the Bus Pirate. The 2013-02-09-wheezy-raspbian-ili9341-cnvogelg-fbtft image has 32MHz hardwired.
What I really want is for someone to test the display with the flexfp driver. Too see if that would work.
But I guess I have to wait for someone with a Watterott who wants the next 3.8 kernel. Maybe then we will see some self interest leading to fixing that driver.
Buy honestly I haven't asked lallalfa. I'm a bit busy now, so some things have to wait.
Having a display would have solved it. But I find it to expensive, and with shipping and customs fee it's out the question.
I really like that display, because it's good fit for the Pi, it uses SPI natively.
I don't like having a driver in my repo that doesn't work.
The driver in the repo works fine. I'm guessing that the reason for the bad report, would be miswiring. lallafa used CE1 (I discovered that when I used his kernel), but fbtft always uses CE0 for display and CE1 for touch.
I have added rotation support to the driver. Will be in the next release.
To bad the speed has to be lowered to 16MHz when the touch controller is used. The display just suddenly becomes all white.
This driver doesn't work with the display, see discussion
I have made an image with lallafa's kernel build: https://github.com/notro/fbtft/wiki
Ref: http://lallafa.de/blog/2013/03/watterott-mi0283qt-9a-display-for-the-rasbperry-pi/
The text was updated successfully, but these errors were encountered: