I am working with km v4l module (http://gatos.sf.net) and I have come
accross a strange issue with mach64 DMA engine. For some reason it would
not work unless I reset it using BUS_CNTL.
I.e.:
a=readl(kms->reg_aperture+MACH64_BUS_CNTL);
writel(a & (~(1<<6)), kms->reg_aperture+MACH6
Apologies for the hit and run posting, but the thread was pointed out
to me and I could not resist dropping in to offer the KGI 2 duckets.
This conversation is eerily familiar, to the point where we've not only
had it during the initial discussion that spawned KGI, we've had it
many times when e
On Tuesday 23 October 2001 11:28, Manuel Teira wrote:
> This is an interesting problem. How are other drivers dealing with this? I
> suppose that the mach64 driver only should try to load the agpgart when the
> card is agp based. I'm trying to see how could this be made.
The Utah-GLX code's got
On Monday 22 October 2001 23:04, Derrik Pates wrote:
> Not to burst anyone's bubble here, guys, but shades of GGI going on. Do
> you guys really want to dredge up all this debate, covering (pretty much)
> the same points you guys are addressing here? I'm not saying your ideas
> are bad, I'm not p
On Monday 22 October 2001 22:41, R C wrote:
> With Mach64, perhaps. With Radeon PCI, it locks up horribly in Xserver
> initialization.
There could be several reasons for that- the code should be checking for the
lack of AGP support and do the right things. As for it needing it to be
loaded, w
On Monday 22 October 2001 18:58, Malte Cornils wrote:
> BTW, why does mach64 module insertion
> fail when agpgart isn't installed if it doesn't use any features
> from AGP?
While we're opening the device, we're not using it because the code that we
have was stalled at DMA operations (It's just
what are the current developement status for radeon 7500 and 8500?
i know thers had talk about it before but many developement had advence sience.
thank you.
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-d
To the ones testing the Mach64 PCI devices.
I think that the problem is in the mach64.h file:
...
/* General customization:
*/
#define __HAVE_AGP 1
#define __MUST_HAVE_AGP 1
#define __HAVE_MTRR 1
...
You should change:
#define __MUST_HAVE_AGP 1
by
#de
El Mar 23 Oct 2001 06:17, Leif Delgass escribió:
> On Tue, 23 Oct 2001, Malte Cornils wrote:
>
> [snip]
>
> > gltron does 5-15 on mach64, 5-15 on plain mesa, too; although it
> > subjectively seems to be a bit jerkier. Anyway, with the old Utah code
> > I got more (at least 20fps, but on a K6-2 33