VxWorks X available?
Patrick C Leger
that's what we need. Here's the situation:
We've got console using an Intel box running VxWorks. The console
talks to an SGI Indigo^2 and to an 11,000 lb. robot which rips things
apart. The console needs to do real-time stuff since it's sending
commands & recieving data from the robot, but it also has a touch
screen attached to it. We'd like to have an X display on the touch
screen.
So, does anyone know of an X implementation for VxWorks? Please let
me know, if so...
--
Chris Leger (bl...@cmu.edu)
Junior, Carnegie Mellon Computer Engineering
"...when people do our songs, it has kind of
a parody effect, like when Bill Murray does a
Beatles song." - Donald Fagen
Patrick Combes
>I know it seems sort of silly to put X on top of a real-time OS, but
>that's what we need. Here's the situation:
>We've got console using an Intel box running VxWorks. The console
>talks to an SGI Indigo^2 and to an 11,000 lb. robot which rips things
>apart. The console needs to do real-time stuff since it's sending
>commands & recieving data from the robot, but it also has a touch
>screen attached to it. We'd like to have an X display on the touch
>screen.
>So, does anyone know of an X implementation for VxWorks? Please let
>me know, if so...
From the FAQ:
21. X for VxWorks
WRS has a product called windX which supports Motif. There is also
libX11 contribution in the VxWorks Archive. This package is perhaps
fairly old and out of date. Essentially, to port X stuff to VxWorks
you'll need to do make sure code is re-entrant everywhere. There is a
"multi-thread" safe version of Xlib available somewhere on the net, one
might try porting that. There are also vendors that have built X servers
using VxWorks. Jupiter Systems, in Alameda, makes high-end X server
machines based on VxWorks. Other X terminal vendors (HP?) also use VxWorks.
___
This is all I know.....
Hope it helps
-Pat Combes
Fermilab
Paul D.Goffin
pl...@andrew.cmu.edu "Patrick C Leger" writes:
> So, does anyone know of an X implementation for VxWorks? Please let
> me know, if so...
We (Radstone Technology) have two X implementations which use
vxWorks - you have to buy the vxWorks!
One is a server for X11R4 which has been written to run on our
Mil Spec CPU40 and GDP-1A graphics card. Should run on other
processors though. Mil Spec is pricey!
The other is based on our PME68-41 68040 card, the VMAX multi-
screen graphics system and X11R5. These are commercial boards,
but I have no idea about the price of the VMAX which is a very
clever graphics card (multi screen, multi keyboards etc.)
Radstone at:
Montvale NJ (800) 368-2738 UK +44 327 359444
(201) 391-2700 France +33 (1) 64.46.04.03
(708) 304-0202
(408) 727-4795
Paul
--
---
Paul D. Goffin + p...@samal.demon.co.uk +44 525 373931
+ my system; my opinions.
Gene Kennon
contents of VisiCom's VX-Windows (client and server) product data sheet
below. VX-Windows is composed of three products which can be purchased
separately depending on your requirements.
VX-Server is MIT X Windows System (X11R5) compatible with VxWorks.
Included is a complete X server for a VxWorks.
VX-Libs is MIT X Windows System (X11R5) compatible for VxWorks.
Included are the X clients, libraries, Athena widgets, and
X
window manager (twm).
VX-Libs/M is VX-Libs plus the OSF/Motif 1.2.2 libraries, clients, and
Motif
Window Manager (mwm) compiled for a specific target.
Requires either VX-Server or other VxWorks compatible X
libraries.
All libraries have been made reentrant for efficient memory usage.
VisiCom has numerous platforms supported, will contract to provide
ports and
drivers to customer specific hardware (CPU, keyboard, video, mouse),
supplies
with the product sample source code to assist in customizing.
Please feel free to contact me directly with questions.
Gene Kennon
Vice President, Corporate Marketing
VisiCom Laboratories, Inc.
10052 Mesa Ridge Court
San Diego, CA 92121
(619) 457-2111
fax 457-0888
________________________________________________________________________
_____
X Window Systemª and OSF/Motifª for Real-Time Embedded Processes
The VisiCom X Window System (VX-Windows) provides an X Window
environment for real-time embedded processes. VX-Windows is a modified
version of the X Window System MIT standard distribution (including
server, window manager, and programming libraries) and the OSF/Motif
Toolkit. VX-Windows has been developed to run with high performance
real-time operating systems. VX-Windows can be networked, using the
operating system network facilities, with any BSD or UNIX¨ host
systems, or any other operating system with TCP/IP networking
facilities.
The VX-Windows Server is based on the sample server provided with the
standard MIT distribution, modified to provide a standard interface
with a driver that can be customized for particular graphic hardware.
The server can accept requests from clients running anywhere on the
network, including local clients.
Programming libraries include the Xlib programming library, the Xt
Intrinsics, the miscellaneous utilities (Xmu), the Athena widget set,
and the OSF/Motif widget set. The ÔtwmÕ and ÔmwmÕ window manager are
available as well as a variety of clients.
The VX-Windows X and Motif libraries are re-entrant. All library
elements are provided as library archive collections as well as
loadable images, allowing applications to be built with only those
functions which are required, or the entire library may be downloaded
and shared amongst multiple clients.
Features and Benefits
¥ Low cost X Window environment for real-time embedded applications
¥ Full support of X Window and OSF/Motif features
¥ Utilizes operating system networking facilities
¥ Disk storage for server, clients, and fonts can be on local disk or
on disk
attached to remote host
¥ Server supports requests from clients on local or remote machines
¥ Sample frame buffer, mouse, and keyboard drivers included
¥ Sample drivers can be modified for specific hardware
¥ Documentation on customization of sample drivers
¥ Local clients can utilize remote server
¥ Re-entrant client libraries.
¥ Twm and Mwm window managers
¥ Various demonstration clients provided
System Operating Requirements
¥ Currently supported to run under the VxWorks¨ real-time operating
system.
¥ 40 Mbyte hard disk on host or local machine for development
¥ 4+ Mbytes RAM recommended for execution
Supported Clients
- Twm and Mwm window managers
- xclock
- xhost
- xload
- xlsclients
- xlswins
- xsetroot
- xwininfo
- various other demonstration clients including:
- ico
- kaleid
- xfish
- xgif
Supported Hardware:
The only hardware dependent portions of VX-Windows are the frame
buffer, mouse, and keyboard drivers. A sample driver and documentation
on customizing the driver is provided. The VX-Windows system has been
successfully demonstrated on the following CPU boards and graphics
cards, but will work for all VxWorks' supported CPU's:
- Force CPU-30, CPU-40, SPARC-1E, SPARC-2CE, SPARC-3CE
- GMS V36, V46, V49, V64
- Tadpole TP-41V
- Motorola MVME-147, MVME-162, MVME-167, MVME-197
- PTI 131, 141, 151A
- Vigra MMI-150, MMI-250, and GDM-9000 Graphic Controllers
- Vigra VGS-882 Intelligent Graphic Controller
- Peritek VCD Series Graphic Controller
- DY 4 DVME-770
The x86 VX-Server has been built and tested to support the following
chipsets:
Cirrus Logic clgd5428
S3 86C805
Accelerated chipsets:
8514/A (and true clones)
ATI Mach8, Mach32
Cirrus CLGD5426, CLGD5428
S3 86C911, 86C924, 86C801, 86C805, 86C928
Western Digital WD90C31
SVGA chipsets:
Tseng ET3000, ET4000AX, ET4000/W32
Western Digital/Paradise PVGA1
Western Digital WD90C00, WD90C10, WD90C11, WD90C30, WD90C31
Genoa GVGA
Trident TVGA8800CS, TVGA8900B, TVGA8900C, TVGA8900CL, TVGA9000
ATI 28800-4, 28800-5, 28800-a
NCR 77C22, 77C22E
Cirrus Logic CLGD5420, CLGD5422, CLGD5424, CLGD5426, CLGD5428,
CLGD6205, CLGD6215, CLGD6225, CLGD6235
Compaq AVGA
OAK OTI067, OTI077
All of the above are supported in both 256 color and monochrome modes,
with the exception of the ATI and Cirrus chipsets, which are only
supported in 256 color mode.
------------------------------------------------------------------------
-----
Ordering Information:
VX-Windows 2.0
Price List
June 1, 1994
License Fees (object)
VX-Windows VX-SERVER VX-Libs/M VX-Libs
$4,000 $2,000 $3,000 $2,000
License Fees (source)
VX-Windows VX-Server VX-Libs/M VX-Libs
$20,000 $10,000 $10,000 $5,000
Target: 680x0 SPARC 80x86
Item P/N P/N P/N
VxWorksª : VX-Windowsª 810-1117-001 810-1117-003 810-1117-005
VX-Serverª 810-1114-001 810-1114-003 810-1114-005
VX-Libsª 810-1116-001 810-1116-003 810-1116-005
VX-Libs/Mª 810-1118-001 810-1118-002 810-1118-003
pSOS+ª: VX-Windowsª 810-1225-002
VX-Serverª 810-1230-002
VX-Libsª 810-1240-002
VX-Libs/Mª 810-1118-004
SOURCE CODE
VxWorks: VX-Windowsª 810-1117-002 810-1117-004 810-1117-006
VX-Serverª 810-1114-002 810-1114-004 810-1114-006
VX-Libs/Mª 810-1118-005 810-1118-006 810-1118-007
VX-Libsª 810-1116-002 810-1116-004 810-1116-006
pSOS+: VX-Windowsª 810-1225-004
VX-Serverª 810-1230-004
VX-Libs/Mª 810-1235-004
VX-Libsª 810-1240-004
VX-Supportª 890-1015-001
VX-Server target license 810-1110-003
OSF/Motif¨ target license 830-2002-001
Development Licenses are royalty-free, single-site, project licenses.
VX-Windows includes VX-Server andVX-Libs/M and supports X11R5, Motif
1.2.2.
VX-Server target licenses are required for each target display system
deployed with VX-Server object code.
Motif target licenses are required by Open Software Foundation for each
target CPU system deployed with each production application. Target
licenses are purchased individually at $40 per copy. Each Motif target
license allows customers to bundle the OSF/Motif runtime with every
copy of their application, up to the number of copies purchased.
VX-Server includes source to VX-gen (680x0 and SPARC), VX86_SVGS and
VX86_S3 (80x86).
VX-Libs/M includes source to mwm, Motif widget library, and Motif
clients, as well as twm, Xlib, Xmu, Xext, Xt, Xaw and X clients. Motif
sources can be supplied only if customer is an Open Software Foundation
source licensee.
VX-Libs includes source to twm, Xlib, Xmu, Xext, Xt, Xaw and X clients.
VX-Support is a twelve month support and update fee (i.e., extends the
standard ninety day period to fifteen months Ñ 20% of list price per
year).
VX-Serverª 2.0
Target License Fee List
April 1, 1994
Server licenses are required for each target display system deployed.
Licenses are purchased individually on a pre-paid basis, according to
the schedule below.
Quantity Target License Fee
1 $500
2 - 4 $250
5 - 9 $200
10 - 24 $175
25 - 49 $150
50 - 99 $125
100 - 249 $100
250 - 499 $ 50
500 - 999 $ 25
1000 + $ 10
------------------------------------------------------------------------
-----
VX-Windows Memory Usage
Module Object Size Execution Size
support.o 34896 (Unix and Posix support)
fixun.o 212 (float to unsigned int
patch)
vigra250drv.o 11072 19140 (graphics driver)
Xvx.o (server) 568025 628160
X11.o 192385
Xext.o 12786
Xt.o 227045
Xmu.o 49766
Xaw.o 178025
Xm.o 892326
Athena.o 647414
Motif.o 1359705
VX-Libs.o 1531669
Mwm 203882 384200
Twm 137525 308900
Object Size is the size of the object file to be downloaded. The amount
of memory required for the object varies depending on whether symbols
are loaded or not. When only global symbols are loaded (default), these
sizes are somewhat less.
Execution Size is the approximate number of bytes consumed by the
module text and data after loading and starting the module. This number
was retrieved from the memShow facility under VxWorks. memShow was
executed before the module was downloaded, and then executed 60 seconds
after the module was downloaded and started. The delay was placed in to
allow the module to allocate all initial necessary data. The window
manager modules will require different memory amounts as the
configuration changes (the .*rc file), and as clients are executed and
managed by the window manager. The server module will also consume
memory as additional clients are executed.
bob schulman
various X servers available for vxWorks. We will soon also offer
re-entrant client side support for both the core client side
libraries (Xlib/Xt/Xaw/Xmu) and for Motif as well.
Seaweed Systems is also available for contracting work for X server
porting, extension, and enhancement as well as custom extensions and
ports of the client-side code.
The current server code is X11R5; there will be X11R6 server available
within 45 days. The client code will be X11R6.
Both source and object-only products are available.
For information, please send email to
in...@seaweed.com
or call me at:
(510) 482-3575
Bob Schulman