Robert Murrell
|
io-display and BIOS interactions
|
Robert Murrell
03/28/2011 10:31 AM
post84329
|
io-display and BIOS interactions
I am trying to interface an odd-resolution LCD screen to an x86 single-board PC. My goal is to avoid having a custom
BIOS created for our application. My plan was to set the board for blank booting (which I have working) and let io-
display set the proper settings for the LCD screen, but this isn't working as expected. We are experimenting with two
different manufacturer's boards. One uses an SMI SM712 LynxEM4+ graphics chip. The other uses an XGI Technology Volari
Z9 chip. The LCD screen is a 480x272 TFT color display (I didn't pick it). For the SM712 I configure io-display to
use the smi7xx driver and for the Z9 I use the svga driver. Since the Z9 chip doesn't seem to have an existing QNX
driver that targets this hardware, I've been concentrating on the SM712 board.
Both board power up OK in CRT 640x480 mode. For the Sm712 board, I have a simple program that opens io-display and can
display a simple bitmap. I edited display.conf to set the resolution to 480x272, but the screen always comes up in
648x480, the BIOS default. Next, I tried to customize smi7xx.conf to match the LCD display's timing characteristics. I
set the BIOS display settings to 640x480 TFT LCD. When I run my test program, gf_dev_attach returns 2,
GF_ERR_IODISPLAY. I will get this error even if I set display.conf to 640x480 resolution to match the BIOS resolution.
This error is too generic for me to determine what is wrong. Is there something else I need to set to get io-display
to at least attach to the LCD screen?
|
|
|