schuler@palantir.gsfc.nasa.gov ( RMS) (01/21/89)
Shhhhh ! Don't tell the people I work with about this, they will think I spent days hacking the Xserver to get it to work BUT to help others out.... During my hacking on the X11R3 server, trying to get it to work on the HP catseye monitor, I realized (recalled) that the X11R2 server was using the topcat declaration in the /usr/lib/X11/X0screens file, and that it would not even run if it was declared as a catseye. (An important clue) So after days of scrutinizing, mapping, hacking, and an evening of debugging, (I was originaly trying to integrate the X11R2 catseye code into the R3 server) I decided to try an oooohh so simple approach. I replaced the definition of which routines to call for HP screen dependant functions for the catseye with topcat calls. (The HP server uses a table of function names to determine which routines to execute based on a HP device number [Where this comes from I still do not know]). Crossing my fingers, I did a make and and ran the server and lo and behold it worked like a champ. SURPRISE SURPRISE!! Kids, you should try this at home. The file to modify is screentab.c in $(TOP)/server/ddx/hp/hp. The table can be located by searching for "catseye". Just replace the three routines "catseyeScreenInfo", "catseyeScreenInit", and "catseyeScreenClose", with "topcatScreenInfo", "topcatScreenInit", and "topcatScreenClose" resepectively. I am still very curious as to why this works, any ideas? The machine is a HP 9000/360CH. Is it possible that this machine has a catseye monitor, but a topcat controller chip ? As HP does not distribute information about their hardware with the system (how many vendors do this though ?), I was not even aware they had different screen types. Good luck -Larry schuler@palantir.gsfc.nasa.gov One last thing, The server does seem to have problems with the colormap and window managers. twm completely loses it (Not quite as bad as on the Apollo - which may be a twm bug, but even uwm will leave tracks from it's popup windows occasionaly.)
mjb%hoosier.utah.edu@wasatch.UUCP (Mark J. Bradakis) (01/22/89)
In article <578@palantir.gsfc.nasa.gov> schuler@palantir.gsfc.nasa.gov (Larry Schuler - RMS) writes: > I am still very curious as to why this works, any ideas? The machine is >a HP 9000/360CH. Is it possible that this machine has a catseye monitor, but >a topcat controller chip ? The Catseye uses a lot of the same register control info as the Topcat. It "just" has more planes, more pixels displayed, etc. A 1280x1024 monitor will not work with a Topcat card, but you can get a low res Catseye which has only 1024x768 and will drive a Topcat 98782 or a 98785 monitor. mjb. mjb@hoosier.utah.edu Wafer - a small, homeless cookie.