Guys,
I'm using QNX 6.1.0A on Daytona Board(XScale).
There is 'devg-cotulla.so' for graphics drivers.
Our daytona has 640 X 350 LCD screen.
And 'cotulla.conf' describe our screen properties like below.
I want to know how I can change screen to other resolution mode. (ex more
smaller resolution.)
Can I do it though changing contulla.conf ?
If so, is there anyone who teach me how I can ?
If not, Should I change 'devg-cotulla' driver ?
'devg-cotulla.so' is included in Xcale BSP on prebuilt binary.
Where I get the source code of 'devg-cotulla.so' ?
Any idea ?
YongSung
File 'cotulla.conf'.
# devg-cotulla.so parameters for tailoring to specific boards and display
modes.
#
# hsw Horizontal Sync Width
# elw End-of-line pixel clock wait
# blw Beginning-of-line pixel clock wait
# vsw Vertical sync pulse width
# efw End-of-frame line clock wait count
# bfw Beginning-of-frame line clock wait count
# vsp Vertical Sync Polarity (0 = active high, 1 = active low)
# hsp Horizontal Sync Polarity (0 = active high, 1 = active low)
# pcp Pixel Clock Polarity (0 = data sampled on rising edge of L_PCLK, 1
=data sampled on falling edge)
# oep Output enable polarity (0 - L_BIAS pin is active high in display mode
and parallel data input mode)
# acb AC bias pin frequency
# pcd Pixel Clock Divisor
# type 1 = Active Display 0 = Passive Display
# num 0 = Single Panel 1 = Dual Panel
# board 0 = Daytona 1 = Lubbock
# x width of panel
# y height of panel
#
# The driver will use the first un-commented entry.
# Lubbock board, dual panel, passive display
#hsw=30,elw=7,blw=107,vsw=1,efw=0,bfw=0,vsp=0,hsp=0,pcp=1,oep=0,acb=0,pcd=9,
type=0,num=1,board=1,x=640,y=480
# Daytona board, single panel, active display
hsw=30,elw=15,blw=73,vsw=1,efw=1,bfw=98,vsp=0,hsp=0,pcp=1,oep=0,acb=0,pcd=2,
type=1,num=0,board=0,x=640,y=350
Change resolution on daytona borad.
bridged with qdn.public.bsp
Post Reply
1 post
• Page 1 of 1
Jump to
- New qnx.* Newsgroup
- ↳ qnx.newuser
- ↳ qnx.rtos
- ↳ qnx.gui
- ↳ qnx.development_tools
- ↳ qnx.ddk
- ↳ qnx.porting
- ↳ qnx.bsp
- ↳ qnx.qnx4
- ↳ qnx.3rdparty_product_announcements
- ↳ qnx.cafe
- ↳ qnx.public.sysadmin
- ↳ qnx.evaluation
- QDN Newsgroups
- ↳ qdn.cafe
- ↳ qdn.public.qnx2
- ↳ qdn.public.qnx4
- ↳ qdn.public.neutrino
- ↳ qdn.public.photon
- ↳ qdn.public.porting
- ↳ qdn.public.news
- ↳ qdn.public.qnxjobs
- ↳ qdn.public.qnxrtp.newuser
- ↳ qdn.public.qnxrtp.installation
- ↳ qdn.public.qnxrtp.os
- ↳ qdn.public.qnxrtp.photon
- ↳ qdn.public.qnxrtp.devtools
- ↳ qdn.public.qnxrtp.applications
- ↳ qdn.public.qnxrtp.advocacy
- ↳ qdn.public.qnx4.photon
- ↳ qdn.public.qnx4.devtools
- ↳ qdn.public.articles
- ↳ qdn.public.ddk.graphics
- ↳ qdn.public.ddk.network
- ↳ qdn.public.ddk.audio
- ↳ qdn.public.ddk.input
- ↳ qdn.public.ddk.usb
- ↳ qdn.public.ddk.printer
- ↳ qdn.public.qnxrtp.porting
- ↳ qdn.public.qnxrtp.games
- ↳ qdn.public.qnxrtp.embedded
- ↳ qdn.public.qnxrtp.mips
- ↳ qdn.public.qnxrtp.powerpc
- ↳ qdn.public.qnxrtp.strongarm
- ↳ qdn.public.qnxrtp.x86
- ↳ qdn.public.sysadmin
- ↳ qdn.public.qnxrtp.xscale
- ↳ qdn.public.qnxrtp.sh4
- ↳ qdn.public.newuser
- ↳ qdn.public.installation
- ↳ qdn.public.devtools
- ↳ qdn.public.ddk
- ↳ qdn.public.bsp
- Other QNX Newsgroups
- ↳ comp.os.qnx
- ↳ openqnx.developer