Hi,
I cvs updated mach64-0-0-4-branch last night and recompiled (previous
update was on sunday). Right after starting glxgears the screen switched
off (like with xset dpms force off) and the machine hung. The sysrq keys
didn't work.
Maybe Peter Anderson's problems are not PowerPC specific?
I'm now trying mach64-0-0-4-branch with Rage Mobility-M PCI (LR). The
compiled X server does not work in a setting more than 800x600 16bpp.
How much video memory is needed to use Mach64 DRI in general?
I bet you have 8M video RAM! So do I. Today, Mach64 DRI driver does not
use GART so it
On Fri, 2002-04-26 at 00:41, Peter Andersson wrote:
Vector 800 at pc - d58fb02c , lr -d58fb64
mxr - 9032, xp -4200
current - c99fc000, pid - 1077, comm -glxgears
mon
When i type ? the following menu rolls up:
d dump bytes
didump instructions
dfdump float values
dd
I can't remember, is your card PCI or AGP? Do you see a kernel oops in
the system log?
On Fri, 26 Apr 2002, Felix Kühling wrote:
Hi,
I cvs updated mach64-0-0-4-branch last night and recompiled (previous
update was on sunday). Right after starting glxgears the screen switched
off (like
On Fri, 26 Apr 2002, Kaz Sasayama wrote:
I'm now trying mach64-0-0-4-branch with Rage Mobility-M PCI (LR). The
compiled X server does not work in a setting more than 800x600 16bpp.
How much video memory is needed to use Mach64 DRI in general?
I have an 8MB card, and I run the X server at
--- Thomas Winischhofer [EMAIL PROTECTED] wrote:
Jens Owen wrote:
Mike Mestnik wrote:
sis renamed to i830 (or one was removed and the other added),
I recommend leaving the SiS support in the kernel, for now. Also, the
sis_ds.c patch appears to be reversed.
What did that
It lookes like there is some one making changes that I think we should be aware
of. This could be something done by the back-port project. In any case it
looks like this should be put into the CVS, if not all ready there. I'm going
to start pruning my patch of things that get removed, and
Mike Mestnik wrote:
It lookes like there is some one making changes that I think we should be aware
of. This could be something done by the back-port project. In any case it
looks like this should be put into the CVS, if not all ready there. I'm going
to start pruning my patch of things
On Tue, Apr 23, 2002 at 12:49:20AM +0100, Keith Whitwell wrote:
Ian Romanick wrote:
On Tue, Apr 23, 2002 at 12:31:46AM +0100, Keith Whitwell wrote:
Ian Romanick wrote:
What ends up happening is glXGetProcAddress returns the address of the
glBegin symbol from my executable (in
On Fri, Apr 26, 2002 at 03:09:46AM +0200, Smitty wrote:
I'm not the most qualified to answer this, but I think most of the more
qualified people are pretty busy adding some of these features. :)
ATI R100 (Radeon)
=
Anti-aliasing
=
Full Screen No
On Wed, Apr 24, 2002 at 04:49:34PM -0600, Brian Paul wrote:
Brian Paul wrote:
Perhaps you should try out this change before I commit it to the DRI.
Try editing build/xc/lib/GL/GL/Makefile, look for the line that has the
string -Wl,-soname and replace it with -Wl,-Bsymbolic,-soname.
On 2002.04.25 19:23 Leif Delgass wrote:
...
Jose, I just tried removing agpgart before starting X, and I'm getting a
kernel NULL pointer dereference. I think it's because we are using
dev_priv-buffers-handle to read the vertex buffers -- for PCI, there's
no DRM_FIND_MAP for
Ian Romanick wrote:
On Wed, Apr 24, 2002 at 04:49:34PM -0600, Brian Paul wrote:
Brian Paul wrote:
Perhaps you should try out this change before I commit it to the DRI.
Try editing build/xc/lib/GL/GL/Makefile, look for the line that has the
string -Wl,-soname and replace it with
First off, I haven't checked this in yet, because I need to do some
cleanup, but I've got synchronous DMA working for vertex buffers on both
AGP and PCI (PCI for me meaning with agpgart unloaded). Unfortunately, at
the moment it's actually slower than MMIO, since it's synchronous (wait
for
On 2002.04.26 20:17 Leif Delgass wrote:
First off, I haven't checked this in yet, because I need to do some
cleanup, but I've got synchronous DMA working for vertex buffers on both
AGP and PCI (PCI for me meaning with agpgart unloaded). Unfortunately,
at
the moment it's actually slower than
The mach64-0-0-4-branch should be working now for PCI cards, though I
don't know if this will be enough to fix ppc -- probably not yet. It uses
the correct pointer to read the vertex buffer and thus avoids a NULL
pointer dereference in the kernel module. I did find out that on
big-endian
On Fri, 2002-04-26 at 21:17, Leif Delgass wrote:
It took me awhile to figure out how to properly pass the physical address of
the buffers to the card. What I'm doing for pci is using:
address = (u32) virt_to_phys((void *)buf-address)
That doesn't look right. If the physical and bus
On Fri, 26 Apr 2002 11:22:08 -0400 (EDT)
Leif Delgass [EMAIL PROTECTED] wrote:
I can't remember, is your card PCI or AGP? Do you see a kernel oops
in the system log?
It's an AGP card. And no, there was probably no more time to write out a
kernel oops to disc. The last thing I see in the
On Thu, 2002-04-25 at 13:43, Adam K Kirchhoff wrote:
Can anyone fill me in really quickly about the status of the DRI under
FreeBSD? I know that some cards work (Voodoo3 and G400, iirc), but is the
latest code on the trunk usable under FreeBSD? Do you still need to pull
the code from the
--- Jens Owen [EMAIL PROTECTED] wrote:
Finally, it looks like it would also be a good idea to review and
possibly move the kernel development changes back into our repository.
Specifically, I'm talking about changes to the schedule wait queses as
were done to drm_fops.h; changes to the page
On Fri, 26 Apr 2002 08:41:08 +0200
Felix Kühling [EMAIL PROTECTED] wrote:
Hi,
I cvs updated mach64-0-0-4-branch last night and recompiled (previous
update was on sunday). Right after starting glxgears the screen switched
off (like with xset dpms force off) and the machine hung. The sysrq
Howzit Ian?
Thanks for your response.
I'm not the most qualified to answer this, but I think most of the more
qualified people are pretty busy adding some of these features. :)
Noted. But if yours is the only response and / or there are no differing answers guess
what, you will become
22 matches
Mail list logo
