Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-12-04 07:27 ---
(In reply to comm
Christopher,
On Tue, Dec 02, 2003 at 02:57:50PM -0500, Christopher Gleba wrote:
>
> Hello Jose,
>
> Thank you for the response.
>
> > Do you have a PCI card? If not make sure the agpgart kernel module is
> > loaded before the mach64 module, by adding
> >
> > pre-install mach64 modprobe -k ag
On Thu, 4 Dec 2003, Chris Ison wrote:
>I realize replies will be resticted under NDA, but I am unable to refine
>my questions until I can find the answers to the following questions in
>relation to ATI docs some developers have access too.
>
>1. Do the ATI docs outline or detail expected PCI acces
On Wed, Dec 03, 2003 at 04:45:46PM -0500, Brendan Burns wrote:
> Jose,
> thanks for the quick response, here are the details:
>
> Intel 440BX motherboard
> Intel Pentium III (Coppermine) 500mhz
> 192Mb RAM
> ATI Rage Pro (On the motherboard) 4mb graphics memory
Well, nothing special here. The har
On Thu, 2003-12-04 at 11:48, Mike A. Harris wrote:
>
> THe first step to me, would be to oprofile things, and find where
> the bottleneck is, then try to determine why.
Good idea, but beware that the gprof output was rather confusing when I
first saw this problem, the time would appear to be spe
Michel DÃnzer wrote:
On Thu, 2003-12-04 at 11:48, Mike A. Harris wrote:
THe first step to me, would be to oprofile things, and find where
the bottleneck is, then try to determine why.
Good idea, but beware that the gprof output was rather confusing when I
first saw this problem, the time would
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-12-04 13:55 ---
None of the given
Roland Scheidegger wrote:
Michel DÃnzer wrote:
On Thu, 2003-12-04 at 11:48, Mike A. Harris wrote:
THe first step to me, would be to oprofile things, and find where the
bottleneck is, then try to determine why.
Good idea, but beware that the gprof output was rather confusing when I
first saw this
> Good idea, but beware that the gprof output was rather confusing when I
> first saw this problem, the time would appear to be spent in random 3D
> driver functions when in fact it seemed to be waiting for the hardware
> most of the time. oprofile may do a better job there, but you've been
> warne
just a few words for the future, nothing serious...
> -Original Message-
> From: Christopher Gleba [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 04, 2003 23:02
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: [Dri-devel] mach64-0-0-6-branch dri bug report
> Size: 220 k
Hi,
as I'm trying to port the savage driver I stumbled over this. The mga
and r128 drivers define different values for DEPTH_SCALE in xxx_tris.c.
This is a parameter of t_dd_tritmp.h and specifies the minimum
resolvable unit of depth coordinates for computing polygon offsets. In
mgatris.c it is de
On Thu, Dec 04, 2003 at 12:44:06AM +, Alan Hourihane wrote:
> I've created a newmesa branch that I'll be updating the Imakefiles so
> that we can use the new Mesa trunk code with XFree86.
>
> It's late in the UK now, but I've made a start and I'll start adding
> the Imakefiles I've done tomorr
Hello,
I am trying to get a Radeon 9000 pro to work using the latest DRI CVS
tree, but encountering a few problems.
The system in question is a pair of opterons running on a Tyan S2885
board, with Suse 9.0 Professional (AMD64) installed and the latest
2.4.21-149 kernel.
I get the same results wh
Alan Hourihane wrote:
On Thu, Dec 04, 2003 at 12:44:06AM +, Alan Hourihane wrote:
I've created a newmesa branch that I'll be updating the Imakefiles so
that we can use the new Mesa trunk code with XFree86.
It's late in the UK now, but I've made a start and I'll start adding
the Imakefiles I've
On Thu, Dec 04, 2003 at 11:57:10PM +, Alan Hourihane wrote:
> On Thu, Dec 04, 2003 at 04:44:49PM -0700, Brian Paul wrote:
> > Alan Hourihane wrote:
> > >On Thu, Dec 04, 2003 at 12:44:06AM +, Alan Hourihane wrote:
> > >
> > >>I've created a newmesa branch that I'll be updating the Imakefiles
On Thu, Dec 04, 2003 at 04:44:49PM -0700, Brian Paul wrote:
> Alan Hourihane wrote:
> >On Thu, Dec 04, 2003 at 12:44:06AM +, Alan Hourihane wrote:
> >
> >>I've created a newmesa branch that I'll be updating the Imakefiles so
> >>that we can use the new Mesa trunk code with XFree86.
> >>
> >>It'
Alan Hourihane wrote:
On Thu, Dec 04, 2003 at 04:44:49PM -0700, Brian Paul wrote:
Alan Hourihane wrote:
On Thu, Dec 04, 2003 at 12:44:06AM +, Alan Hourihane wrote:
I've created a newmesa branch that I'll be updating the Imakefiles so
that we can use the new Mesa trunk code with XFree86.
It'
On Fri, Dec 05, 2003 at 12:14:18AM +0100, Felix Kühling wrote:
> Hi,
>
> as I'm trying to port the savage driver I stumbled over this. The mga
> and r128 drivers define different values for DEPTH_SCALE in xxx_tris.c.
> This is a parameter of t_dd_tritmp.h and specifies the minimum
> resolvable uni
18 matches
Mail list logo
