FW: [Dri-users] ProSavageDDR, No DRI Thusfar

[Nathan O. <na...@pi...>]

Sorry, I'm new to mailing lists, I sent this just to Alex. Meant to send =
it to everyone.

-----Original Message-----
From: Nathan Olberding=20
Sent: Wednesday, October 06, 2004 2:26 PM
To: 'Alex Deucher'
Subject: RE: [Dri-users] ProSavageDDR, No DRI Thusfar


I grabbed the snapshot for savage from Felix's site and, without X =
running, ran install.sh. It produced no errors, and there are no errors =
in the dri.log file. I restarted the X server, and glxinfo still reports =
no DRI support. lsmod now says the "savage" module is being used by "2" =
(when X is running), but doesn't say what's using it. I've changed =
nothing else from my previous post. To be certain, I rebooted, and still =
no DRI.

-----Original Message-----
From: Alex Deucher [mailto:ale...@gm...]
Sent: Wednesday, October 06, 2004 1:33 PM
To: Nathan Olberding
Subject: Re: [Dri-users] ProSavageDDR, No DRI Thusfar


On Wed, 6 Oct 2004 13:22:39 -0700, Nathan Olberding
<na...@pi...> wrote:
> Thanks for the response! I got the impression from what I saw of news =
posts and release notes that, if I enabled development drivers at =
compile time, the savage driver would have DRI support. I guess I was =
mistaken. I'll get Felix's snapshots.
>=20
> With the Xorg 6.8.1 release comes a driver called savage, as specified =
in my xorg.conf file. I was wondering what the difference is between it =
and the VESA driver (sorry if it's kind of a newbie question... you'd =
think after the amount of time I've spent on this, I wouldn't have any =
newbie questions!).
>=20

the savage driver is an accelerated X server for savage chips.  the
vesa driver is a generic non-accelerated driver for vesa compliant
video cards (most modern cards are vesa compliant).

Alex

>=20
>=20
> -----Original Message-----
> From: Alex Deucher [mailto:ale...@gm...]
> Sent: Wednesday, October 06, 2004 1:16 PM
> To: Nathan Olberding
> Cc: dri...@li...
> Subject: Re: [Dri-users] ProSavageDDR, No DRI Thusfar
>=20
> On Wed, 6 Oct 2004 12:42:56 -0700, Nathan Olberding
> <na...@pi...> wrote:
> > I'm trying to get DRI accelleration on my Averatec 3150P laptop. It =
has a VIA Apollo Pro266 chipset (as detected by agpgart) and a =
ProSavageDDR (ProSavage8) video chipset.
> >
> > Here is the output from lsmod:
> >
> > Module                  Size  Used by
> > savage                 51816  0
> > via_agp                 7104  1
> > snd_via82xx            23364  0
> > snd_ac97_codec         65732  1 snd_via82xx
> > snd_mpu401_uart         5824  1 snd_via82xx
> > snd_rawmidi            19556  1 snd_mpu401_uart
> > i2c_prosavage           3328  0
> > i2c_algo_bit            8904  1 i2c_prosavage
> > i2c_core               18768  1 i2c_algo_bit
> >
> > Notice especially that "savage" and "i2c_prosavage" aren't being =
used.
> >
> > I'm using Xorg 6.8.1, compiled from source, on Slackware 10. Kernel =
version is 2.6.8.1.
>=20
> xorg 6.8.1 does not have dri support for savage.  you need xorg from =
cvs.
> either build from source:
> http://dri.sourceforge.net/cgi-bin/moin.cgi/Building
> or use one of Felix' snapshots:
> http://freedesktop.org/~fxkuehl/snapshots/
>=20
> <snip>
> >
> > I guess I have a few questions;
> >
> > 1) What's the difference between the "savage" driver I've got =
loaded, with no accelleration, and the VESA driver?
>=20
> what "savage" are you talking about?  the drm kernel module or the
> xorg 2d driver?  the Xorg 2d driver provides an accelerated 2d, Xv,
> and advanced mode setup for savage hardware.
>=20
> >
> > 2) What all is possible with my hardware, at the moment, as far as =
accelleration? Is any accelleration possible?
>=20
> 2d accel and Xv support in the 2d driver, 3d support in xorg and mesa =
cvs.
>=20
> >
> > 3) What is the i2c driver for? It said "prosavageddr" somewhere in =
the kernel conf help page, so I went ahead and compiled it, but I still =
don't know what it's for.
>=20
> It's an i2c driver for accessing the i2c bus on savage chips.  I'm not
> sure it has any real use.
>=20
> Alex
>=20
> >
> > Thanks for at least reading this much, and much more thanks for any =
sort of response!
> >
>