📄 readme-cp2.html
字号:
<p>Name
: Include directive
<p>The Name identifies the output device name that will be present within
the pull-down menu and the Include directive defines the output device
identifier that will be defined within the configuration header file created
by the configuration tool.
<p>The following is an example of the definition of a new output device:
<p><tt>## OUTPUT DEVICE TYPES</tt>
<br><tt>#</tt>
<br><tt># Add the Stormpad flat panel display</tt>
<br><tt>#</tt>
<br><tt>stormpad Passive 640x480 display : INCLUDE_UGL_SHARP_LM8V31</tt>
<h3>
6.7 Graphics Device Definition</h3>
The graphics device definition section starts with a "## GRAPHICS DEVICES"
and ends with "END". In between each of these statements are the
statements to define the graphics device that includes the device name,
supported output device, supported operating modes, which consists of device
name, supported processor architectures, etc. The database entries
that are required to define a graphics device are:
<p><b>DEVICE</b> - name of the device. This is the name of the device
that will appear in the pull-down menu of the configuration tool.
<p><b>ARCH</b> - identifies the processor architectures that the graphics
device will operational. At least one ARCH entry must be present.
Additional ARCH entries may be present to specify additional processor
architectures.
<p><b>SELECT</b> - identifies the #define directive to include the
support for the graphics device. This value will be placed within
the generated header file.
<p><b>HEADER</b> - path to the header file that defines miscellaneous data
items required for the configuration process. This path name should
be relative to the setting of WIND_BASE. Refer to the section on
device header file requirements for definitions needed to support the configuration
process.
<p><b>OUTPUT</b> - identifies the output device types that the graphics
device supports. There must be at least one output device type and the
output device types must have already been defined within a OUTPUT section.
<p><b>MODE</b> - defines the modes that the graphics device can operate.
The mode is defined using the parameters, as follows:
<p>Color depth, resolution, refresh rate
<p>For example, to define an 8 bit color depth, with a resolution of 800x600,
and a refresh rate of 60 Hz, the mode definition would be:
<p><tt>MODE 8,800x600,60</tt>
<p><b>OPTION</b> - identifies which of the device extensions or options
that the graphics device supports, such as JPEG, Video, software cursors,
etc. Each option is present on its own line.
<p><b>DIR</b> - If the driver is present within the WindML tree (that is,
the source is within target/src/ugl/driver/graphics), then the DIR line
will define the subdirectory within that the graphics directory.
<p>The following is an example of the definitions for adding anew graphics
device:
<p><tt>## GRAPHICS DEVICES</tt>
<br><tt>#</tt>
<br><tt># Define the Stormpad LCD driver</tt>
<br><tt>#</tt>
<p><tt>START</tt>
<p><tt># Stormpad StrongArm SA1110/SA1111</tt>
<p><tt>DEVICE Stormpad SA LCD</tt>
<br><tt>ARCH ARMARCH4</tt>
<br><tt>SELECT INCLUDE_STORMPAD_SA_GRAPHICS</tt>
<br><tt>OUTPUT INCLUDE_UGL_SHARP_LM8V31</tt>
<br><tt>MODE 8,640x480,60</tt>
<br><tt>MODE 8,800x600,80</tt>
<br><tt>MODE 8,1024x768,60</tt>
<br><tt>MODE 16,640x480,60</tt>
<br><tt>MODE 16,800x600,80</tt>
<br><tt>DIR stormpad</tt>
<br><tt>HEADER target/config/stormpad/stormpad.h</tt>
<br><tt>OPTION JPEG</tt>
<p><tt>END</tt>
<h3>
6.8 Device Header File Requirements</h3>
The header files that are referenced within the configuration data files
require the presence of information that is used by the configuration process.
The primary information within these header files is to provide a linkage
between the configuration process (uglInitialize()) and the device driver.
The specific needs for the pointer, keyboard, and graphics device are defined
below.
<h3>
6.9 Pointer Header File</h3>
The pointer header files requires the following definitions:
<p><b>UGL_POINTER_INIT</b> - defines the initialization routine for the
pointer device
<p><b>SYS_POINTER_NAME</b> - defines the name of the device to use to access
the pointer device
<p>In addition, the pointer device handler needs to include the configuration
files that have been generated to obtain the device name (if it has been
changed from the default) that is to be used.
<p>The following is an example of the definition of these parameters and
the sequence required to include the generated configuration header:
<p><tt>/* Get configuration info for driver */</tt>
<br><tt>#ifndef INCLUDE_PS2_POINTER</tt>
<br><tt>#define INCLUDE_PS2_POINTER</tt>
<br><tt>#define BUILD_DRIVER</tt>
<br><tt>#include <uglInit.h></tt>
<br><tt>#endif /* INCLUDE_PS2_POINTER */</tt>
<p><tt>#define UGL_POINTER_INIT uglPs2PtrInit</tt>
<p><tt>/* Default to the first serial port */</tt>
<br><tt>#ifndef SYS_POINTER_NAME</tt>
<br><tt>#define SYS_POINTER_NAME "/pointer/0"</tt>
<br><tt>#endif /* SYS_POINTER_NAME */</tt>
<p>The WindML pointer device initialization code will not typically create
the I/O device driver. The creation of the I/O device will usually
take place within the BSP. The WindML pointer device handler will
open the device and process the raw data and queue it to the event services.
<h3>
6.10 Keyboard Header File</h3>
The keyboard header files requires the following definitions:
<p><b>UGL_KEYBOARD_INIT</b> - initialization routine for the keyboard device
<p><b>SYS_KEYBOARD_NAME </b>- default device name for the keyboard device
<p>In addition, the keyboard device handler needs to include the configuration
files that have been generated to obtain keyboards maps that are to be
supported and the device name that is to be used.
<p>The following is an example of the definition of these parameters and
the sequence required to include the generated configuration header:
<p><tt>/* Get configuration info for driver */</tt>
<br><tt>#ifndef INCLUDE_PC_AT_KEYBOARD</tt>
<br><tt>#define INCLUDE_PC_AT_KEYBOARD</tt>
<br><tt>#define BUILD_DRIVER</tt>
<br><tt>#include <uglInit.h></tt>
<br><tt>#endif /* INCLUDE_PC_AT_KEYBOARD */</tt>
<p><tt>#define UGL_KEYBOARD_INIT uglPcKbdInit</tt>
<p><tt>/* Default the keyboard device name */</tt>
<br><tt>#ifndef SYS_KEYBOARD_NAME</tt>
<br><tt>#define SYS_KEYBOARD_NAME "/keyboard/0"</tt>
<br><tt>#endif /* SYS_KEYBOARD_NAME */</tt>
<p>The WindML keyboard device initialization code will not typically create
the I/O device driver. The creation of the I/O device will usually
take place within the BSP. The WindML keyboard device handler will
open the device and process the raw data and queue it to the event services.
<h3>
6.11 Graphics Device Header File</h3>
The graphics header files require the following definitions:
<p><b>UGL_GRAPHICS_NAME</b> - name of the graphics device
<br><b>UGL_GRAPHICS_CREATE</b> - name of the device initialization function
<p>As with the other devices, the header files that provide the configuration
information must be included to obtain the operating modes, output device
type, and which options are to be included.
<p>The following provides the parameter definitions in the case where the
driver is constructed such that the 8 and 16 bit color depths are built
as two separate drivers:
<p><tt>/* Get the Device Driver Configuration Definitions */</tt>
<br><tt>#ifndef INCLUDE_IGS_GRAPHICS</tt>
<br><tt>#define INCLUDE_IGS_GRAPHICS</tt>
<br><tt>#define BUILD_DRIVER</tt>
<br><tt>#include <uglInit.h></tt>
<br><tt>#endif /* INCLUDE_IGS_GRAPHICS */</tt>
<p><tt>/* Set up for the requested frame buffer format */</tt>
<br><tt>#ifdef INCLUDE_UGL_ARGB4444</tt>
<br><tt>#define UGL_GRAPHICS_NAME "IGS-5050
- 16 Bit"</tt>
<br><tt>#define UGL_GRAPHICS_CREATE uglIGS16BitDevCreate</tt>
<br><tt>#define UGL_COLOR_DEPTH
16</tt>
<br><tt>#define UGL_MODE_FLAGS
UGL_MODE_DIRECT_COLOR</tt>
<br><tt>#endif /* INCLUDE_UGL_ARGB4444 */</tt>
<p><tt>#ifdef INCLUDE_UGL_RGB565</tt>
<br><tt>#define UGL_GRAPHICS_NAME "IGS-5050
- 16 Bit"</tt>
<br><tt>#define UGL_GRAPHICS_CREATE uglIGS16BitDevCreate</tt>
<br><tt>#define UGL_COLOR_DEPTH
16</tt>
<br><tt>#define UGL_MODE_FLAGS
UGL_MODE_DIRECT_COLOR</tt>
<br><tt>#endif /* INCLUDE_UGL_RGB565 */</tt>
<p><tt>#ifdef INCLUDE_UGL_INDEXED8</tt>
<br><tt>#define UGL_GRAPHICS_NAME "IGS-5050
- 8 Bit"</tt>
<br><tt>#define UGL_GRAPHICS_CREATE uglIGS8BitDevCreate</tt>
<br><tt>#define UGL_MODE_FLAGS
UGL_MODE_INDEXED_COLOR</tt>
<br><tt>#define UGL_COLOR_DEPTH
8</tt>
<br><tt>#endif /* INCLUDE_UGL_INDEXED8 */</tt>
<p><tt>/* Verify that some mode was selected, if not select a default */</tt>
<br><tt>#ifndef UGL_GRAPHICS_CREATE</tt>
<br><tt>#define UGL_GRAPHICS_NAME "IGS-5050
- 8 Bit"</tt>
<br><tt>#define UGL_GRAPHICS_CREATE uglIGS8BitDevCreate</tt>
<br><tt>#define UGL_MODE_FLAGS
UGL_MODE_INDEXED_COLOR</tt>
<br><tt>#define UGL_COLOR_DEPTH
8</tt>
<br><tt>#endif /* UGL_GRAPHICS_CREATE */</tt>
<br>
<br>
<br>
<h2>
<hr WIDTH="100%">7. <a NAME="Notes"></a>Notes on Specific Platforms</h2>
<li>
IDT9514 - This MIPS platform required that the uglInit.h file define the
JP3_ON macro. This macro is by default undef'ed at the end of the
uglInit.h file. The undef must be changed to a define and then the
IGS driver must be rebuilt using either the config tool or the command
line build as described in the User's Guide.</li>
<br>
<p>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<p>
<hr width="100%">
<h2>
8. <a NAME="Known"></a>Known Problems</h2>
<p><br>Problems known to exist with WindML 2.0 with cumulative patch 2
are identified within the following table.
<br>
<br>
<br>
<table BORDER WIDTH="100%" >
<caption><TBODY>
<br></TBODY></caption>
<tr>
<td><b><u>SPR#</u></b></td>
<td><b><u>Description </u></b></td>
<td><b>Work Around (if available)</b></td>
</tr>
<tr>
<td>33844</td>
<td>Final pixel in a line drawn across a region boundary is not incremented
correctly</td>
<td>Affects diagonal lines only</td>
</tr>
<tr>
<td>35182</td>
<td>Wide lines do not work on ellipses</td>
<td></td>
</tr>
<tr>
<td>35345</td>
<td>Comments in some function headers not in sync with the API appendix</td>
<td></td>
</tr>
<tr VALIGN=TOP>
<td>35489</td>
<td>SH4 Q2SD driver does not use bresenham error value</td>
<td></td>
</tr>
<tr VALIGN=TOP>
<td>35500</td>
<td>Inconsistent frame buffer configuration parameters between command
line (values entered in uglInit.h) and the corresponding values in the
configuration tool</td>
<td></td>
</tr>
<tr VALIGN=TOP>
<td>35681</td>
<td>WindML will not always be reloadable without a reboot of VxWorks since
device drivers are not deleted.</td>
<td></td>
</tr>
<tr VALIGN=TOP>
<td>66107/
<br>36017</td>
<td>Archive step can fail when files are small</td>
<td>When building into the UGL archive, delete the archive and perform
the build again. When building into the VxWorks archive, manually add the
missing object files.</td>
</tr>
<tr>
<td>36024</td>
<td>Hardware cursor does not move during a batch start</td>
<td></td>
</tr>
<tr>
<td>62434</td>
<td>IGS 5050 64x64 cursor not implemented</td>
<td></td>
</tr>
<tr>
<td>62238</td>
<td>Compile warnings when building for ARM</td>
<td></td>
</tr>
<tr>
<td>63311</td>
<td>German keyboard mapping is incorrect</td>
<td></td>
</tr>
<tr>
<td>64826</td>
<td>TCL errors when not viewing all configuration pages before building
a configuration</td>
<td>Be sure to visit each configuration page and make a selection.</td>
</tr>
<tr>
<td>65533</td>
<td>JPEG library exits on error, rather that return an error value</td>
<td></td>
</tr>
<tr>
<td>69190</td>
<td>Some Agfa fonts have incorrect inter-charcter spacing</td>
<td></td>
</tr>
<tr>
<td>69185</td>
<td>Make will randomly crash on Windows 2000 hosts</td>
<td>Each directory can be built seperately</td>
</tr>
<tr>
<td>69251</td>
<td>SimSolaris can not support a remote display (Solaris 2.7)</td>
<td></td>
</tr>
<tr>
<td>69264</td>
<td>BMF Font parser on Unix config tool may not parse all fonts</td>
<td>Remove all but those fonts actually being used or build from the command
line</td>
</tr>
<tr>
<td>69376</td>
<td>StrongArm archiver for Tornado 2.1 fails on large archives</td>
<td>This bug was seen with the large Unicode font file (unifont.c). Remove
the other font source code files from the directory and rebuild.</td>
</tr>
</table>
</body>
</html>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -