glenn@cs.utexas.edu (Glenn G. Lai) (02/16/91)
X386 1.1
--------
If you're looking for the X386 1.1 binaries (exclusive of the fonts, but
they haven't changed anyway), I've already sent them to turing.cse.nau.edu
and will send them to atc.sp.unisys.com after I finish this message.
ProDesigner II and NEC 4D
--------------------------
You read and use the info below AT YOUR OWN RISK.
As you may know, Thomas Roell's clock.pas, the way it's written, doesn't
detect the presense of the 44-MHz and 62-MHz crystals. I called Orchid and
was told that the ordering of the crystals are "proprietary." Luckily, some
knowledge of binary numbers and a little trial and error straightened
the most important thing (see below) out. The working parameters are:
# Orchid ProDesigner II/1024
ET4000 1024 1152 900 25 28 40 36 0 44 0 62 "1024x768" # Orchid Prodesigner II
Note that the "44" could be bogus, but since I wanted only 1024x768x256, I
didn't bother to check it out. I think you can even say "25 28 40 36 0 62"
and make it work at 1024x768.
Now comes the interesting part. Note that I didn't have all the documentation
I needed, so certain things were based on (very) educated ( :-) ) guesses.
(It works perfectly on my ProDesigner II + NEC 4D--one doesn't even hear the
awful sound that switching frequencies sometimes produces.)
I assumed the ProDesigner II syncs on green, as opposed to using separate
syncs as listed in its user's manual. I set 4D's sync switch to OFF, and
computed the following numbers based on this assumption. They are probably
as close to the 4D's spec as they can get.
# Orchid ProDesigner II and an NEC 4D
"1024x768" 62 1024 1071 1133 1327 768 769 773 799
This is a genuine noninterlaced 1024x768 at 60Hz. It flickers a bit, but
it's hardly noticeable unless you have a window with a white background
(even then it's no worse than our HP's color board and SONY). Note that
70Hz requires a 75-MHz crystal, according my calculation based on the NEC
4D manual. Don't forget that Thomas gave us a virtual screen of 1152x900
here, so some clients might get clipped at the border; move the mouse cursor
to bring the hidden parts into view.
You don't necessarily get the correct aspect ratio by making the root
window's width/height 4/3. Run "xfig," draw a circle, and adjust the
screen to make the circle look (and measure) like a circle to you.
Glenn
glenn@cs.utexas.edu
-----Cut here-----
#
# Copyright 1990,91 by Thomas Roell, Dinkelscherben, Germany.
#
# Permission to use, copy, modify, distribute, and sell this software and its
# documentation for any purpose is hereby granted without fee, provided that
# the above copyright notice appear in all copies and that both that
# copyright notice and this permission notice appear in supporting
# documentation, and that the name of Thomas Roell not be used in
# advertising or publicity pertaining to distribution of the software without
# specific, written prior permission. Thomas Roell makes no representations
# about the suitability of this software for any purpose. It is provided
# "as is" without express or implied warranty.
#
# THOMAS ROELL DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,
# INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO
# EVENT SHALL THOMAS ROELL BE LIABLE FOR ANY SPECIAL, INDIRECT OR
# CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
# DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
# TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
# PERFORMANCE OF THIS SOFTWARE.
#
# Author: Thomas Roell, roell@informatik.tu-muenchen.de
#
# $Header: /proj/X11/mit/server/ddx/at386/RCS/Xconfig,v 1.22 91/02/10 16:27:02 root Exp $
#
#
# define all devices to use
#
Primary
#
# name keymap
Keyboard # get the default-mapping that was estebished by ttymap(1)
#
# name device
#MouseSystems "/dev/tty00"
Logitech "/dev/tty00"
#Microsoft "/dev/tty00"
#BusMouse "/dev/mouse"
#
# just tell the server how big our display really is (in mm)
#
# Display 290 220
Display 290 217
#
# select some nice colors
#
WhitePixel "White"
BlackPixel "Black"
#Overscan "#89e5e5" # works not with every hardware & resolution !!!
#
# we are also able to set here the default root visual type
# (StaticGray, GrayScale, StaticColor, PseudoColor, TrueColor, DirectColor)
#
RootVisual PseudoColor
#
# if you want to disable CTRL+ALT+BS uncomment the following
#
#DontZap
#
# some nice paths, to avoid conflicts with other X-servers
#
RGBPath "/usr/lib/X11/rgb"
FontPath "/usr/lib/X11/fonts/misc/,/usr/lib/X11/fonts/75dpi/,/usr/lib/X11/fonts/100dpi/"
##############################################################################
# now lets declare our VGA board
#
Graphics
# Paradise OEM16
# chip ram virtual clocks default-mode flags
#PVGA1A 512 864 606 25 28 36 "640x480"
# Orchid ProDesigner+
# chip ram virtual clocks default-mode flags
#ET3000 512 864 606 25 26 36 30 "800x600"
# Orchid ProDesigner
# chip ram virtual clocks default-mode flags
#ET3000 512 864 606 25 28 35 45 65 "800x600"
# GENOA 5300/5400
# chip ram virtual clocks default-mode flags
#ET3000 512 864 606 25 28 0 45 0 0 39 "800x600"
# GENOA 6400
# chip ram virtual clocks default-mode flags
#GVGA 512 864 606 25 28 16 45 14 16 39 65 "800x600"
# TRICOM Mega/1024
# chip ram virtual clocks default-mode flags
# ET4000 1024 1152 900 25 28 62 36 0 0 0 45 "1024x768"
# Orchid ProDesigner II/1024
ET4000 1024 1152 900 25 28 40 36 0 44 0 62 "1024x768" # Orchid ProDesigner II
# STB PWR GRAPH
# chip ram virtual clocks default-mode flags
#ET4000 1024 1152 900 25 28 37 45 40 32 0 65 "1024x768"
# Sigma Legend with 1M
# chip ram virtual clocks default-mode flags
#ET4000 1024 1152 900 25 28 0 40 36 40 45 58
# 32 36 31 35 50 48 33 65 "1024x768" Legend
# Diamond Speedstar with 512K or 1M
# chip ram virtual clocks default-mode flags
#ET4000 512 840 624 25 28 32 36 40 45 50 62 "840x624"
#ET4000 1024 1152 900 25 28 32 36 40 45 50 62 "1024x768"
#
# Timings for build after standard VGA BIOS.
#
# name clock horzontal timing vertical timing flags
"640x480" 25 640 672 768 800 480 490 492 525
#"800x600" 36 800 816 952 1056 600 608 610 633
#"800x600" 39 800 872 968 1104 600 600 606 624
#"1024x768i" 45 1024 1064 1224 1264 768 777 785 817 Interlace
#"1024x768" 62 1024 1096 1272 1328 768 776 778 808
##############################################################################
# And now some specials build by myself. No guarantee at all.
# Just try it, if you want.
#
#
# Timings for a NEC 3D and a Genoa 5300
#
# name clock horzontal timing vertical timing flags
#"736x540" 28 736 768 800 896 540 540 550 560
#"800x600" 39 800 864 896 1008 600 600 606 624
#
# Timings for a Nano Flexscan 9070s and a TRICOM Mega
#
# name clock horzontal timing vertical timing flags
#"864x648" 45 864 912 1064 1080 648 648 668 672
#"920x690" 62 920 952 1088 1168 690 688 718 724
#"1024x768" 62 1024 1072 1200 1240 768 766 782 786
#"1024x768" 62 1024 1072 1176 1272 768 778 779 804
#"1152x900" 62 1152 1184 1288 1360 900 898 929 939 Interlace
# Orchid ProDesigner II and an NEC 4D
"1024x768" 62 1024 1071 1133 1327 768 769 773 799
# Timings for a Orchid ProDesigner (brians@eecs.ee.pdx.edu)
#
# name clock horzontal timing vertical timing flags
#"800x600" 36 800 832 966 966 600 600 609 631
# Diamond SpeedStar and NEC 2a (gwr@world.std.com)
#"840x624" 36 840 884 1032 1056 624 624 626 648darrylo@hpnmdla.HP.COM (Darryl Okahata) (02/17/91)
In comp.unix.sysv386, roell@informatik.tu-muenchen.de (Thomas Roell) writes: > X11R4core.tar.Z All binaries, libraries, etc. that are needed to > get X11R4 run on your 386box (except the fonts). Are these binaries supposed to work with Esix rev D? I followed the installation instructions (including running install.sh & kernel reconfig), and xinit dies with a "Creating TCP socket: Invalid argument" error. I'm guessing that this server is trying to use BSD sockets; unfortunately, Esix DOES NOT HAVE BSD sockets. It has a library that smells like BSD sockets, but is in no way or form BSD sockets. Esix has only streams, not sockets. I guess I'll have to try compiling the sources. Does anyone know if X11R4 can be compiled with gcc 1.38? For that matter, does anyone know if the native Esix ld(1) command can handle X11R4? I've heard that some 386 loaders cannot handle linking X11R4. As a side issue (which may get obsoleted by all this), in Esix, the stream pipes "sp" driver referenced by install.sh does NOT show up in /usr/options. The "sp" driver is part of the Remote File Sharing Package, and therefore shows up in "/usr/options/remote.name". -- Darryl Okahata UUCP: {hplabs!, hpcea!, hpfcla!} hpnmd!darrylo Internet: darrylo%hpnmd@hp-sde.sde.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion or policy of Hewlett-Packard or of the little green men that have been following him all day.