i have to connect an ARM-board to a LC-Display. Its a graphical display with a resolution of 120x64 Pixel. The ARM-Board has a VGA-Chip onboard. The customer wants to use X for this display, whatever reason he will have. So my question is now: what is the best way to bring these things together? Should i adapt the kernel-fbdev or the fbdevhw from X? Or is there an easier way? Is there someone who has made such development and will share his Experiences? Thank you,
regards, Jens
--
Die obige Adresse is OK, wird aber nicht gelesen.
Für Mails an mich bitte "usenet" gegen "jens.nixdorf" austauschen.
Alex Pavloff schrubte am Mittwoch, 20. August 2003 17:44:
You're right, the lcd will be connected to a cpu-port.
To write a driver is also my idea. So i looked into the kernel-sources to get some understanding how the framebuffer works. But there are some things i didn't found out yet:
The framebuffer represents mostly the memory of a vga-card, but i need also the write-routines, because i have to change the port to write to. Where is this set in the kernel? Or should i put my own write-routines directly into the framebuffer (fbmem.c)?
Normally there are several fb-drivers in the source. When they are compiled as modules, the kernel looks at the hardware, is reading some stuff and with this stuff it can determine which card is connected. My lcd is deaf and mutely, because the lack of own "intelligence", so it would not answer. How can i say the kernel, that it has to use _my_ framebuffer-driver?
Screen sizes shouldnt be a problem, because the customers product will be a handheld-like device, which has only predefined applications on it (which also have to be written yet).
regards, Jens
--
Die obige Adresse is OK, wird aber nicht gelesen.
Für Mails an mich bitte "usenet" gegen "jens.nixdorf" austauschen.
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.