I have a new version of DRM at bk://mesa3d.bkbits.net/drm
In it's current form it's 2.6 kernel only. Some support is generic but I've
mainly be working on an R200. It is still under development with lots of work to
do.
Major features:
1) Get VBIOS ROM contents IOCTL
2) Driver automaps the registe
--- Jon Smirl <[EMAIL PROTECTED]> wrote:
> I'm working on some code for the R200 I2C devices. There are four of
> them. It's
> obvious what CRT, CRT2, and DVI do. But what does MONID do?
>
the same thing as the others. ATI wires their cards to correspond to
the respective names, but some oems w
I'm working on some code for the R200 I2C devices. There are four of them. It's
obvious what CRT, CRT2, and DVI do. But what does MONID do?
=
Jon Smirl
[EMAIL PROTECTED]
__
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo
Okay I've checked in the DRM and Xserver changes to the above branch, I've
added the PCI ids I think are correct for the chip variations,
I'll hopefully get around to testing it in the next couple of days, (just
have to drag out the laptop :-)
If anyone else has a chance feel free to give it
like the R200 one.
It doesnt contain intendation fixup yet.
I tried only with q3a.
best regards,
Andreas
mesa_radeon_texcombine_refactor.diff
Description: Binary data
Hi,
I built the module with the -f flag which made the difference. I copied it to
my modules directory in my kernel tree and then did a modprobe savage. Then I
killed X and restarted it. My XFRee86.0.log shows
(II) SAVAGE(0): [junkers] sarea_priv_offset:0x0898
(II) SAVAGE(0): Direct r
Am 2004.02.07 09:44:39 +0100 schrieb(en) Ian Romanick:
[...]
> as well. I'll try to have a patch tomorrow. The server-side of things
Looks like its fixed in DRI CVS with/since your patch.
I have to admit that I only tried with the new libGL.so and old
Xserver/libs, not with old libGL and new Xs
--- Felix Kühling <[EMAIL PROTECTED]> wrote:
> On Sun, 8 Feb 2004 09:28:51 -0800 (PST)
> Alex Deucher <[EMAIL PROTECTED]> wrote:
>
> >
> > --- Felix K_hling <[EMAIL PROTECTED]> wrote:
> > > Alex,
> > >
> > > I'm working on 3D support for Savage IX right now. I've added
> > > register
> > > stru
--- George Lengel <[EMAIL PROTECTED]> wrote:
> On Saturday 07 February 2004 02:48 pm, Felix Kühling wrote:
> > On Fri, 6 Feb 2004 09:36:48 -0800 (PST)
> > Alex Deucher <[EMAIL PROTECTED]> wrote:
> >
> > [snip]
> >
> > > http://www.botchco.com/alex/savage/savage-20040206.tar.gz
> >
> > Nice work! I
On Sun, 8 Feb 2004 09:28:51 -0800 (PST)
Alex Deucher <[EMAIL PROTECTED]> wrote:
>
> --- Felix K_hling <[EMAIL PROTECTED]> wrote:
> > Alex,
> >
> > I'm working on 3D support for Savage IX right now. I've added
> > register
> > structures for SavageIX. Now I need to find out the chipset type in
>
--- Felix Kühling <[EMAIL PROTECTED]> wrote:
> Alex,
>
> I'm working on 3D support for Savage IX right now. I've added
> register
> structures for SavageIX. Now I need to find out the chipset type in
> the
> 3D driver. That requires a few small modifications to the 2D driver.
> I'm
> not sure if
Alex,
I'm working on 3D support for Savage IX right now. I've added register
structures for SavageIX. Now I need to find out the chipset type in the
3D driver. That requires a few small modifications to the 2D driver. I'm
not sure if I should work with the old or your new 2D driver. I'd prefer
to
Am Sonntag, 8. Februar 2004 15:14 schrieb Dieter Nützel:
> Ian Romanick wrote:
> > Roland Scheidegger wrote:
Ups, forgotten something.
Do you see such huge DRI-Devel List delays, too?
I haven't even received your mails about this topic...
Greetings,
Dieter
-
13 matches
Mail list logo
