On Fre, 2002-11-01 at 22:04, [EMAIL PROTECTED] wrote:
> I tried several times today to download the texmem-0-0-1 branch. Each
> time, when it reaches /cvsroot/dri/xc/xc/extras/x86emu/include, I get
> the message
>
> cvs server: [12:53:47] waiting for anoncvs_dri's lock in
> /cvsroot/dri/xc/xc/ext
On Fri, Nov 01, 2002 at 04:04:45PM -0500, [EMAIL PROTECTED] wrote:
> I tried several times today to download the texmem-0-0-1 branch. Each
> time, when it reaches /cvsroot/dri/xc/xc/extras/x86emu/include, I get
> the message
>
> cvs server: [12:53:47] waiting for anoncvs_dri's lock in
> /cvsroot/
> After looking at the source, support for multiple cards is only enabled
> in the tdfx DRM yet. The attached hack might serve as a quick'n'dirty
> way to find out the next problem. :)
I added in the #define from the patch.
When I insmod, it now sees both cards. I get something like:
[drm] Ini
Felipe,
On Fri, Nov 01, 2002 at 04:18:31PM +, Felipe Bugno wrote:
My question is about the voodoo and SLI.
First I would like to point out that I don't fully understand what you
mean with SLI (Scan Line Interleave I suppose) and its implications with
the voodoo driver. Spite of that, the co
I tried several times today to download the texmem-0-0-1 branch. Each
time, when it reaches /cvsroot/dri/xc/xc/extras/x86emu/include, I get
the message
cvs server: [12:53:47] waiting for anoncvs_dri's lock in
/cvsroot/dri/xc/xc/extras/x86em/include
It then prints the same message at every minute
On Fri, Nov 01, 2002 at 04:18:31PM +, Felipe Bugno wrote:
> Why the radeon developers don't donate 30 minutes per day (or per week)
> to colaborate with SLI work??
As one of the people making contributions to the Radeon driver, I'll try to
answer that.
1. Every day the interested in 3dfx har
My question is about the voodoo and SLI.
I'm a user of voodoo 5 5500 board and i love this board.
So, i'm (and most of 3dfx users with linux) have much interess
to see SLI work in linux.
Observing the list of devels, my conclusion is:
the radeon devel is much more implemented in relation as
other
José Fonseca wrote:
Actually my main interest is the learning experience of making a DRI driver
from ground up - experience which I plan to share by writing a thorough
HOWTO describing the steps and explaining the working of a driver from
the high-level structure to the low-level implementation d
On Fri, Nov 01, 2002 at 03:27:23PM +, Keith Whitwell wrote:
> Ian Romanick wrote:
> > I'm running Viewperf for the first time. The drv-08 test doesn't look right
> > to me using the R100 driver. For most of the test, the screen is totally
> > black. When there is something on the screen, it
On Fri, 2002-11-01 at 08:38, Michel Dänzer wrote:
> On Fre, 2002-11-01 at 16:30, Russ Dill wrote:
> > On Fri, 2002-11-01 at 08:15, Alan Hourihane wrote:
> > > On Fri, Nov 01, 2002 at 08:02:10AM -0700, Russ Dill wrote:
> > > > related note: I was setting up a mach64 for one of my friends, and X
> >
On Fre, 2002-11-01 at 16:30, Russ Dill wrote:
> On Fri, 2002-11-01 at 08:15, Alan Hourihane wrote:
> > On Fri, Nov 01, 2002 at 08:02:10AM -0700, Russ Dill wrote:
> > > related note: I was setting up a mach64 for one of my friends, and X
> > > dying with a SIGILL. It looks like the snapshots are bei
On Mit, 2002-10-30 at 00:48, James Fung wrote:
> > I suppose both cards work with DRI disabled? Please provide config
> > files, logs and kernel output, preferrably somewhere on the web.
>
> Oops - my XF86Config-4 file had some whitespace problems which I fixed.
> I've got two PCI radeons worki
Ian Romanick wrote:
I'm running Viewperf for the first time. The drv-08 test doesn't look right
to me using the R100 driver. For most of the test, the screen is totally
black. When there is something on the screen, it looks like the far
clip-plane isn't set quite right. It does NOT look like t
On Fri, 2002-11-01 at 08:15, Alan Hourihane wrote:
> On Fri, Nov 01, 2002 at 08:02:10AM -0700, Russ Dill wrote:
> > related note: I was setting up a mach64 for one of my friends, and X
> > dying with a SIGILL. It looks like the snapshots are being compiled with
> > 686 optimizations (this was a k6)
On Fri, Nov 01, 2002 at 08:02:10AM -0700, Russ Dill wrote:
> related note: I was setting up a mach64 for one of my friends, and X
> dying with a SIGILL. It looks like the snapshots are being compiled with
> 686 optimizations (this was a k6)
If you've ended up using the XFree86 4.2.99.2 Xserver wit
related note: I was setting up a mach64 for one of my friends, and X
dying with a SIGILL. It looks like the snapshots are being compiled with
686 optimizations (this was a k6)
---
This sf.net email is sponsored by: See the NEW Palm
Tungsten T
On Fri, Nov 01, 2002 at 01:50:38PM +, Sergey V. Udaltsov wrote:
I'll have to fix this, probably by using a seperate install.sh for
mach64, or by specifing the necessary XFree86 version on the package
describing file.
Great. But why X server from 2.99.1 is not compatible with mach64?? I
thou
> I'll have to fix this, probably by using a seperate install.sh for
> mach64, or by specifing the necessary XFree86 version on the package
> describing file.
Great. But why X server from 2.99.1 is not compatible with mach64?? I
though I should not break things at least. Why does it?
Anyway, I'l
Sergey,
On Fri, Nov 01, 2002 at 01:01:20PM +, Sergey V. Udaltsov wrote:
Hi all
They are only bleeding-edge snapshots because the DRI cvs HEAD no longer
can produce binary compatible snapshots. All new snapshots require to
download and install XFree86-4.2.99.2 server from
http://dri.sourcefo
On Thu, 2002-10-31 at 21:59, Alan Hourihane wrote:
> That's debateable.
>
> In current kernels, if it's not defined you've more than likely
> built your kernel with i386 rather than i486 or later, because
> building for i486 or later automatically turns on CONFIG_X86_CMPXCHG.
> I understand that i
Hi all
> They are only bleeding-edge snapshots because the DRI cvs HEAD no longer
> can produce binary compatible snapshots. All new snapshots require to
> download and install XFree86-4.2.99.2 server from
> http://dri.sourceforge.net/snapshots/extras/ . The 'install.sh' script
> attempts to deter
21 matches
Mail list logo
