Return to BSD News archive
Xref: sserve comp.unix.sysv386:25800 comp.unix.bsd:8199 comp.windows.x:47779 Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!agate!curtis From: curtis@cs.berkeley.edu (Curtis Yarvin) Newsgroups: comp.unix.sysv386,comp.unix.bsd,comp.windows.x Subject: Re: I need 8514/ATI Graphics Ultra support for ISC UNIX SVR3.2 & X11R4 Date: 25 Nov 1992 06:08:50 GMT Organization: CS Dept. Snakepit - Do Not Feed. Lines: 49 Message-ID: <1ev59iINNt8v@agate.berkeley.edu> References: <1992Nov23.073800.6592@Informatik.TU-Muenchen.DE> <1eshe9INNeum@agate.berkeley.edu> <1992Nov24.172506.29957@Informatik.TU-Muenchen.DE> NNTP-Posting-Host: cobra.cs.berkeley.edu In article <1992Nov24.172506.29957@Informatik.TU-Muenchen.DE> roell@informatik.tu-muenchen.de (Thomas Roell) writes: |>Mach8 documentation is now publicly available. | |That's suprising. COuld you please post where you got this info from, |and where to get the docs so other people can use them, too... | |>The Mach8 extensions are minor, and will not be noticed under most |>applications; I suspect the SGCS 85k versus free 60k xstones is more |>a result of extensive tweaking and optimization than this. | |no comment, but a big *smile* Yeah. This is the place where you will win every time, buying a commercial version of X. |>>Furthermore, you have to use DOS to setup a 1024x768 NI mode. |> |>That mode is the 1024x768x60hz mode. If your monitor can handle 70hz - |>and most can, these days - you will have no problem. The Ultra |>boots in 1024x768x70hz mode by default. | |Ok. The first Ultra I had was initialzed for 1024x768 interlaced. I |had to use DOS to get the 70Hz ... So they changed this ... I never |looked at the internal defaults since long time, at least not since I |programmed the ultra with it's native registers. Huh. That's interesting; especially as the Ultra I have is a fairly old one (pre-1280x1024), and boots up at 70Hz. Frankly, I find it odd that they changed that; the 8514/A standard is, after all, interlaced, and one can imagine a monitor being inadvertently damaged by this. |>Roell has, in the past, claimed that SysV use of X8514 requires kernel |>mods; this is also false. SVR3 has a call to enable user-level port |>access, and I believe SVR4 has it too. | |Yes, both SVR3.2 and SVR4 have calls to enable generall io port access |priviege: | | sysi86(SI86V86, V86SC_IOPL, PS_IOPL); | |That's not the problem. The problem is that some unixes are buggy to |keep this privilege. That has to do with the mechanisms how the |kernels restores the user context after a signal has been processed in |user space. ISC 2.0.2 has this problem, while 2.2 and 3.x doesn't. |Also some older SVR4s (4.0.1 and 4.0.2) have this problem. Just be careful not to send your X server any signals :-) c