On Sun, Feb 15, 2004 at 08:02:51AM -0800, Alex Deucher wrote:
> >
> > Savage2000's 3D engine has a T&L unit that, IIRC, S3 never even could
> > get working right. I think it worked in D3D but they disabled it in
> > OpenGL due to hardware problems or something. So there would be
> > another
> >
--- Ryan Underwood <[EMAIL PROTECTED]> wrote:
>
> On Sat, Feb 14, 2004 at 11:46:19PM -0800, Alex Deucher wrote:
> > To elaborate on what felix said, savage2000 is a different beast
> than
> > any of the other savages. regarding the 2D driver, I have no idea
> how
> > its bitmap descripters are l
On Sat, Feb 14, 2004 at 11:46:19PM -0800, Alex Deucher wrote:
> To elaborate on what felix said, savage2000 is a different beast than
> any of the other savages. regarding the 2D driver, I have no idea how
> its bitmap descripters are laid out. The 3D engine is a whole nother
> ball of wax... if
--- cunha17 <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'm experiencing some problem with my
> Savage2000(Viper II) card and DRI.
> Just for the records, I followed all
> recomendation I could find in and out
> of this list.
>
> First of all I recompiled my
> kernel(vanilla 2.4.24, since
> fedora/
Hi Cristiano,
short answer to a long mail: The Savage driver does not support
Savage2000 chips at the moment. We have no hardware documentation nor a
reference driver implementation. Unless this changes it's unlikely that
Savage2000 support will be available any time soon. :-/
At the moment the d
# lspci -n
00:00.0 Class 0600: 8086:1130 (rev 02)
00:01.0 Class 0604: 8086:1131 (rev 02)
00:1e.0 Class 0604: 8086:244e (rev 02)
00:1f.0 Class 0601: 8086:2440 (rev 02)
00:1f.1 Class 0101: 8086:244b (rev 02)
00:1f.2 Class 0c03: 8086:2442 (rev 02)
00:1f.3 Class 0c05: 8086:2443 (rev 02)
00:1f.4 Class 0
Hi all,
I'm experiencing some problem with my
Savage2000(Viper II) card and DRI.
Just for the records, I followed all
recomendation I could find in and out
of this list.
First of all I recompiled my
kernel(vanilla 2.4.24, since
fedora/redhat kernel-source has some
incompatibilities) without DRM,