Using framebuffer with AOC E1649FWU monitor on Ubuntu 14.04

berryja · 05-18-2016, 05:05 PM

I am not sure what the hardware is exactly, but using the udlfb driver, I am able to get images to display using the fbi program. Interestingly, the display stays off (backlight off) until I display something on it. The first run seems to have some issues (black pixels show a random line pattern), but after I get all the pixels painted not-black, everything seems to work. The display comes up in 16-bit mode (5, 6, 5) which is not as convenient to work with, but I guess better than not working at all.

I have not gotten it to work with a custom app I wrote to draw on the framebuffer. I guess now it's just comparing to the fbi code to see what it is doing differently. I am not doing any VT stuff in my app, so maybe that is it.

Thanks for the suggestion.

berryja · 05-20-2016, 01:51 PM

I finally got it working using my custom code. After ripping apart the fbi app code, I figured out the trick was writing to the buffer twice with a little bit of time between.

samjam · 05-20-2016, 01:54 PM

Quote:

Originally Posted by berryja

I finally got it working using my custom code. After ripping apart the fbi app code, I figured out the trick was writing to the buffer twice with a little bit of time between.

That is very unexpected. You just write the image twice with a small delay?

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

05-18-2016, 05:05 PM	#1
berryja Junior Member Join Date: May 2016 Posts: 3	I am not sure what the hardware is exactly, but using the udlfb driver, I am able to get images to display using the fbi program. Interestingly, the display stays off (backlight off) until I display something on it. The first run seems to have some issues (black pixels show a random line pattern), but after I get all the pixels painted not-black, everything seems to work. The display comes up in 16-bit mode (5, 6, 5) which is not as convenient to work with, but I guess better than not working at all. I have not gotten it to work with a custom app I wrote to draw on the framebuffer. I guess now it's just comparing to the fbi code to see what it is doing differently. I am not doing any VT stuff in my app, so maybe that is it. Thanks for the suggestion.

05-20-2016, 01:51 PM	#2
berryja Junior Member Join Date: May 2016 Posts: 3	I finally got it working using my custom code. After ripping apart the fbi app code, I figured out the trick was writing to the buffer twice with a little bit of time between.