Re: ..yawed OpenGL on 8 MB ATI mach64, was: [Flightgear-devel] Re: framerate

2002-04-03 Thread Arnt Karlsen

On Wed, 3 Apr 2002 00:41:26 +0200 (CEST), 
Martin Spott [EMAIL PROTECTED] wrote in message 
[EMAIL PROTECTED]:

  From: Alex Perry [EMAIL PROTECTED]
 
  I don't know whether the IIC has the Pro feature set (suspect
  not). If it does, the Mach64 driver of Utah-GLX works fine for me.
 
 You might want to have a look at recent DRI development. I'm following
 this already for a while and it appears to me that the guys got quite
 far with implementing DRI for Mach64,

..thanks.  Any chance it is available as a rpm, or a tarball 
that will come out as an ok rpm, out of a 'rpm -ta '?
(Up to my ears in work.)

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: ..yawed OpenGL on 8 MB ATI mach64, was: [Flightgear-devel] Re: framerate

2002-04-03 Thread Arnt Karlsen

On Wed, 3 Apr 2002 15:03:17 -0800 (PST), 
Alex Perry [EMAIL PROTECTED] wrote in message 
[EMAIL PROTECTED]:

  On Wed, 3 Apr 2002 00:41:26 +0200 (CEST), 
  Martin Spott [EMAIL PROTECTED] wrote in message 
  [EMAIL PROTECTED]:
  
From: Alex Perry [EMAIL PROTECTED]
   
I don't know whether the IIC has the Pro feature set (suspect
not). If it does, the Mach64 driver of Utah-GLX works fine for
me.
   
   You might want to have a look at recent DRI development. I'm
   following this already for a while and it appears to me that the
   guys got quite far with implementing DRI for Mach64,
  
  ..thanks.  Any chance it is available as a rpm, or a tarball 
  that will come out as an ok rpm, out of a 'rpm -ta '?
 
 I have no idea.  Last time I touched an rpm was about a year ago.
 As I remember, I carefully used a long pole that had an alien
 on the end ... what do those command line switches mean ?

..build rpm from this tarball.  If it barfs, or a cvs commit warrants,
'rpm -e' it, and try another, say 'rpm -ba ', as in build that darn rpm
from the tarball using the '.spec'-file I fixed.  Length of pole is 
discretionary.  ;-)

..snippets of 'man 8 rpm':
BUILDING PACKAGES:
   rpm {-ba|-bb|-bp|-bc|-bi|-bl|-bs} [build-options] SPECFILE ...
   rpm {-ta|-tb|-tp|-tc|-ti|-tl|-ts} [build-options] TARBALL ...
   rpm {--rebuild|--recompile} SOURCEPKG ...
...
BUILD OPTIONS
The general form of an rpm build command is 
rpm {-bSTAGE|-tSTAGE} [build-options] FILE ...
The argument used is -b if a spec file is being used to build the
package and -t if rpm should look inside of a (possibly compressed) tar
file for the spec file to use. After the first  argument, the next
character (STAGE) specifies the stages of building and packaging to be
done and is one of:

-baBuild binary and source packages (after doing the %prep, %build,
and %install stages).

...etc.  Enables use of /usr if /usr/local chokes like:  ;-)
[arnt@lana http-install]$ df -h
FilesystemSize  Used Avail Use% Mounted on
/dev/hda9 251M   97M  141M  41% /
/dev/hda5  23M  4.6M   16M  22% /boot
/dev/hdb7 4.8G  4.1G  544M  89% /home
/dev/hdb5 2.8G  2.3G  455M  84% /home/arnt/DL
none   62M 0   61M   0% /dev/shm
/dev/hda71011M   82M  878M   9% /tmp
/dev/hda6 4.9G  4.2G  580M  88% /usr
/dev/hda113.6G  2.9G  524M  85% /usr/local
/dev/hda81011M  275M  685M  29% /var

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: ..yawed OpenGL on 8 MB ATI mach64, was: [Flightgear-devel] Re: framerate

2002-04-02 Thread Martin Spott

 From: Alex Perry [EMAIL PROTECTED]

 I don't know whether the IIC has the Pro feature set (suspect not).
 If it does, the Mach64 driver of Utah-GLX works fine for me.

You might want to have a look at recent DRI development. I'm following this
already for a while and it appears to me that the guys got quite far with
implementing DRI for Mach64,

Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are !
--

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



..yawed OpenGL on 8 MB ATI mach64, was: [Flightgear-devel] Re: framerate 1/s

2002-03-22 Thread Arnt Karlsen

(This is also posted on usenet on 
comp.os.linux.x  no.it.os.unix.linux.diverse)

On Fri, 22 Mar 2002 23:37:46 +0100, 
Melchior FRANZ [EMAIL PROTECTED] wrote in message 
[EMAIL PROTECTED]:
 
 PS: Of course,I get better framerates up to 40/s (without
 clouds/panel) insome areas (above the sea ;-), but airports badly
 kill performance,just like the panel does. That's very sad,
 because I can never landwith ILS. Need a better computer ...


..are you sure you can't get good framerates with a good video card?

..on my bloated workstation, an AMD K6-2 450, on an Epox
 EP-MVGP3G2 main board, I can add ram from 128 MB to 384MB.
 SW: Red Hat 7.2, all erratas, XFree86 4.1.0-15, kernel 2.4.18 
 and the aty framebuffer in the kernel, vt's at vga=795, 
 and X at 1600 x 1200 x 24bpp @ 59Hz, nice once stomped home.

..which videocard should I go for?  
 (I like to avoid closed source drivers.)

..the apg-slot is occupied by an 8 MB ATI 3D Rage IIC AGP (rev 122).  
 Nice 2D at 1600x1200x24bpp, my torched Sony GDM-2038  will _not_ 
 sync vga, last time, it spent 22 hours to sync vga.
 
..whatever it syncs, is yawed 1/3 off the screen, to the left.
 Right boot stomping with xvidtune:
 Num hsync: 1, Num vsync: 1
 hsync range 0:  28.00 -  88.00
 vsync range 0:  50.00 - 175.00
 1600x1200   162.00   1600 1600 1856 2216   1200 1200 1208 1238 
 +hsync +vsync  ...plus some _un-documented_ button menu entries 
to the right,  that appeared _after_ the last screen smoke screen. 
;-)

..bad news is, this doesn't quite cut it on the console.
How do I move the picture back into the middle of the glass, 
for both the console and for X, automagically???


..my card can do 230 MHz, sissy XFree86 stops the pixel clock at 162MHz.
I can afford to _smoke_ the card, _not_ the monitor.  


..now, _how_ do I get this card to do _accellerated_ OpenGL?
 How far can I push acellerated OpenGL at say 800x600 or better? 
 bpp???


..and just _how_ do I _smoke_ the damned card???  

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)

  Scenarios always come in sets of three: 
  best case, worst case, and just in case.


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel