The following procedure describes how to apply your Screen configuration by
using a command-line interface.
Screen processes the configuration file, graphics.conf,
only when Screen services (screen) starts.
If your target system allows it, you can modify the configuration file and use the following procedure
to apply your new configuration. Otherwise, you need to make your modifications to
graphics.conf on your host, and then build it into your
OS image filesystem
. When your target boots with the new IFS, and screen starts, your new
configuration takes effect.
Prior to starting this procedure, ensure the following:
-
Your target hardware is running the QNX Neutrino RTOS.
-
You can run a shell and commands, such as pidin.
- You've modified graphics.conf with your desired configuration.
To apply your Screen configuration:
-
Stop screen by using the following command:
-
Verify that your screen process has stopped.
Run:
pidin -p screen
and verify that the screen process isn't running.
- Optional:
If you haven't already, set the LD_LIBRARY_PATH environment variable to include the
directories of the shared libraries that Screen needs.
export LD_LIBRARY_PATH=:/lib:/usr/lib:/lib/dll:/proc/boot
- Optional:
If you are configuring mtouch and using the devi driver,
ensure that you have io-hid and devi-hid
running. Run:
pidin ar
From the output of pidin ar, verify that
io-hid and devi-hid are running.
Here's an example of the proceses that could be running on your platform:
pid Arguments
1 procnto-smp-instr -v
4098 devc-seromap -e -p -F -b115200 -c48000000/16 0x48020000^2,106
4099 slogger
4100 pipe
4101 i2c-omap35xx-omap4 -p 0x48070000 -i 88
4102 i2c-omap35xx-omap4 -p 0x48072000 -i 89
4103 i2c-omap35xx-omap4 -p 0x48060000 -i 93
4104 i2c-omap35xx-omap4 -p 0x48350000 -i 94
8201 io-audio -d omap4pdm
16394 devb-mmcsd-blaze cam silent blk noatime,cache=8m mmcsd ioport=0x4809c100,ioport=0x4a056000,irq=115,dma=30,dma=61,dma=62 dos exe=all
16395 spi-master -u 0 -d omap4430 base=0x48098100,irq=97,sdma=0
16396 spi-master -u 3 -d omap4430 base=0x480ba100,irq=80,sdma=0
16397 io-usb -domap4430-mg ioport=0x4a0ab000,irq=124 -dehci-omap3 ioport=0x4a064c00,irq=109
20494 io-pkt-v4 -ptcpip -dsmsc9500 mac=004460515624
24591 dhcp.client
32784 devc-pty
32786 inetd
36881 qconn
36883 sh
73748 fs-cifs 10.222.109.24:/test /t screen
176149 io-hid -dusb
180246 devi-hid -PrR1280 touch
184343 pidin ar
To confirm that io-hid is running with
devh-usb.so, you can run the command:
pidin -p io-hid mem
pid tid name prio STATE code data stack
176149 1 t/bin/io-hid 10r SIGWAITINFO 36K 124K 24K(516K)*
176149 2 t/bin/io-hid 21r RECEIVE 36K 124K 4096(12K)
176149 3 t/bin/io-hid 10r RECEIVE 36K 124K 4096(20K)
176149 5 t/bin/io-hid 10r REPLY 36K 124K 4096(20K)
176149 6 t/bin/io-hid 10r RECEIVE 36K 124K 4096(20K)
libc.so.3 @ 1000000 460K 16K
libhiddi.so.1 @78000000 32K 4096
devh-usb.so @78009000 16K 4096
libusbdi.so.2 @7800e000 40K 8192
-
Restart screen by running screen.
-
Verify that there were no warnings generated from your new
configuration by running sloginfo.