Re: savage cvs driver with xorg 7.1

On 8/18/06, Manfred Paul <[email protected]> wrote:
> On Friday, 18. August 2006 17:33, you wrote:
> > On 8/18/06, Manfred Paul <[email protected]> wrote:
> > > Hi,
> > >
> > > I am using Xorg 7.1 (from Debian experimental). I would like to test the
> > > EXA extension for the savage driver. Three days ago i build xorg from
> > > git, but this wasn't good (wrong fonts..., savage driver found just 8 MB
> > > ram instead of 16). So it there a possibility to get the git/cvs xorg
> > > savage driver run under xorg 7.1. I mean, the exa API is the same, isn't
> > > it? If this is not possible, could somebody write me some lines how to
> > > get xorg cvs funning correcly.
> >
> > Can you try the savage driver from git prior to Ian's memmap changes?
> How to get them? (You mean an older driver?) I am a bit confused ;-)
>

yes.  Try the driver with Ian's changes reverted:
http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-savage.git;a=summary
you can use git bisect to rollback changes:
http://wiki.freedesktop.org/wiki/UsingGit

> I downloaded the savage-driver from git, compiled it and installed it.
> But like I said, the driver doesn't find the correct videoram size.
> ( i compiled against xorg 7.1 and mesa from debian)
>
> the git driver:
> (II) SAVAGE(0): Primary V_BIOS segment is: 0xc000
> (II) SAVAGE(0): VESA BIOS detected
> (II) SAVAGE(0): VESA VBE Version 2.0
> (II) SAVAGE(0): VESA VBE Total Mem: 15168 kB
> (II) SAVAGE(0): VESA VBE OEM: S3 Incorporated. Paramont BIOS
> (II) SAVAGE(0): VESA VBE OEM Software Rev: 1.0
> (II) SAVAGE(0): VESA VBE OEM Vendor: S3 Incorporated.
> (II) SAVAGE(0): VESA VBE OEM Product: VBE 2.0
> (II) SAVAGE(0): VESA VBE OEM Product Rev: Rev 1.0
> (--) SAVAGE(0): Chip: id 8c2e, "SuperSavage/IXC 64"
> (--) SAVAGE(0): Engine: "SuperSavage"
> (--) SAVAGE(0): AGP card detected
> (==) SAVAGE(0): Using AGP DMA
> (II) SAVAGE(0): DMA is not supported on SuperSavages.
> (==) SAVAGE(0): DMA disabled
> (**) SAVAGE(0): Using AGP 4x mode
> (**) SAVAGE(0): Using 16 MB AGP aperture
> (==) SAVAGE(0): Using gamma correction (1.0, 1.0, 1.0)
> (--) SAVAGE(0): probed videoram:  8192k
> (==) SAVAGE(0): Write-combining range (0xe8000000,0x4000000)
> (==) SAVAGE(0): Write-combining range (0xe4000000,0x4000000)
>
> the xorg 7.1 driver:
> (II) SAVAGE(0): Primary V_BIOS segment is: 0xc000
> (II) SAVAGE(0): VESA BIOS detected
> (II) SAVAGE(0): VESA VBE Version 2.0
> (II) SAVAGE(0): VESA VBE Total Mem: 15168 kB
> (II) SAVAGE(0): VESA VBE OEM: S3 Incorporated. Paramont BIOS
> (II) SAVAGE(0): VESA VBE OEM Software Rev: 1.0
> (II) SAVAGE(0): VESA VBE OEM Vendor: S3 Incorporated.
> (II) SAVAGE(0): VESA VBE OEM Product: VBE 2.0
> (II) SAVAGE(0): VESA VBE OEM Product Rev: Rev 1.0
> (--) SAVAGE(0): Chip: id 8c2e, "SuperSavage/IXC 64"
> (--) SAVAGE(0): Engine: "SuperSavage"
> (--) SAVAGE(0): AGP card detected
> (==) SAVAGE(0): Using AGP DMA
> (II) SAVAGE(0): DMA is not supported on SuperSavages.
> (==) SAVAGE(0): DMA disabled
> (**) SAVAGE(0): Using AGP 4x mode
> (**) SAVAGE(0): Using 16 MB AGP aperture
> (II) SAVAGE(0): mapping MMIO @ 0xc0100000 with size 0x80000
> (==) SAVAGE(0): Using gamma correction (1.0, 1.0, 1.0)
> (--) SAVAGE(0): probed videoram:  16384k
>
> Do you know how to fix the probe bug?

I think it's probably do to Ian's memmap changes.

>
> > > Another problem. I have two monitos, with xinerama extension. One
> > > 1400x1050 with 60Hz and another with 1024x768 with 75Hz. When I want to
> > > watch a movie, i can just watch it on the frist (the large) screen. The
> > > other stays always blue (the movie on the second screen)? It is just
> > > possible to watch something on the smaller screen, when i disable
> > > xinerama, and have two different desktops. But KDE has some problems with
> > > that, so this doesn't make fun at all. Is this a driver, X or my problem?
> > > ;-)
> >
> > The problem is the no one has gotten the overlay on the second crtc
> > working correctly.  I tried at one point, but didn't have much luck.
> > So for now, there is only an overlay available on the first crtc.  It
> > doesn't matter whether you use xinerama or not.  You can tell your
> > video app to not use Xv if you want the video on both heads.
> >
> Where do i disable this (e.g. in xine?)

I don't recall off-hand for xine, but you'd want to switch the output
type from Xv to X11 or something like that.

Alex

>
> Manne
>
> > Alex
> >
> > > regards
> > >
> > > manne
>

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
--