I wrote that MindRover crashes X with Radeon VE and DRI. Last days I asked few
people on irc to test MindRover-demo with their Radeons (TCL and no-TCL, DRI
from current CVS and older). All of them got X locked. MindRover works well on
Voodoo3 (DRI), Matrox (DRI), Radeon (ATI closed source drivers),
I've looked and looked and looked and I can't work
out why so maybe someone else with more experience can look at the Radeon
DRM and find the cause..
With trunk, I managed to get the radeon 9000 to
work till I upgraded my puter, and cvs up'd at the same time.
Now, with trunk and texmem, a
Adam K Kirchhoff wrote:
Program received signal SIGSEGV, Segmentation fault.
r200UpdateTextureEnv (ctx=0x8391a38, unit=0) at r200_texstate.c:739
739const GLenum format = tObj->Image[tObj->BaseLevel]->Format;
(gdb) bt
#0 r200UpdateTextureEnv (ctx=0x8391a38, unit=0) at r200_texstate.c:739
So I finally got home and gave DRI on NetbSD on try. Unfortunately, I'm
not having any luck.
The first two times I loaded the radeon kernel module, and then started X,
the entire machine locked, require me to hit the reset button. The 3rd
time I got around to hooking up a laptop to the serial p
On Thu, 13 Feb 2003 10:35:53 +0100
Felix Kühling <[EMAIL PROTECTED]> wrote:
> On Thu, 13 Feb 2003 00:49:36 -0700
> Keith Whitwell <[EMAIL PROTECTED]> wrote:
>
> > Excellent.
> >
> > Can someone commit this? Does this fix *all* the problems? I don't know if
> > it would.
>
> It fixes all SW T
On Thu, Feb 13, 2003 at 01:38:06PM -0500, Forge wrote:
> Is there anything that can be done to cut down the spam on dri-devel?
> Several other mailing lists I'm on hold submissions by non-subscribers
> for approval. I'd even be willing to sort the non-subscribed emails, so
> that everyone else c
> I have never tried WineX myselves in recent times
> but i am confident that the next ATI Linux driver release
> will address that thing so that this conflict is solved.
>
> -Alex.
When is the next release going be? Any guesstimations?
Joe
---
Alexander Stohr wrote:
WineX is clobbering a register that the OpenGL part
of the driver has already sort of "claimed"?
Then their software is sort of "broken". ;-)
I very respectfully disagree. If I'm not mistaken, fs is one of the
registers that the Linux ABI lists as callee-saved, just like
WineX is clobbering a register that the OpenGL part
of the driver has already sort of "claimed"?
Then their software is sort of "broken". ;-)
I have never tried WineX myselves in recent times
but i am confident that the next ATI Linux driver release
will address that thing so that this conflict i
tir, 2003-02-11 kl. 12:26 skrev Alexander Stohr:
> development for the Linux platform has not stopped,
> surely not, it is just that there were no releases
> in the last two months or so. i have to admit that
> there were some problems as for any driver out there,
> but none was so fundamental seri
>
> Right. locators.h is generated by config(8), which is not used by lkms.
> I wasn't sure what the 'right way' to fix this was, and keep forgetting to ask
> a smart NetBSD person. touching locators.h in
> xc/programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel works for the moment.
>
> touchi
Quoth Adam K Kirchhoff:
>
>Hey guys,
>
> I got the server to build, but when I go to build the drm module,
>I'm getting further errors:
>
>[ root@sorrow - /home/adamk/dri/xc/xc/programs/Xserver/hw/xfree86/os-support/bsd/drm
>/kernel/radeon ]: make
>cc -O2 -I. -I.. -ffreestanding -Werror -
Hey guys,
I got the server to build, but when I go to build the drm module,
I'm getting further errors:
[ root@sorrow -
/home/adamk/dri/xc/xc/programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel/radeon ]:
make
cc -O2 -I. -I.. -ffreestanding -Werror -nostdinc -I.
-I/home/adamk/dri
Is there anything that can be done to cut down the spam on dri-devel?
Several other mailing lists I'm on hold submissions by non-subscribers
for approval. I'd even be willing to sort the non-subscribed emails, so
that everyone else could avoid them...
Or am I just being obnoxious?
Rich 'Forg
On Thu, Feb 13, 2003 at 04:12:46PM +0100, Felix Kühling wrote:
> On Thu, 13 Feb 2003 15:29:44 +0100 (CET)
> Martin Spott <[EMAIL PROTECTED]> wrote:
> > It probably fixes SW TCL bugs - as Felix states - but it does not touch the
> > HW TCL related problems with the radeon driver. They still exist,
So, in summary, I have no idea what is going on. X internals are a bit
over my head at this point. This seems to have been triggered by a
DRI-related hardware lock, but please also note that the above (current
state of things) happens with 'radeon' even when DRI is not being
loaded!
Does poweri
On Thu, 13 Feb 2003 15:29:44 +0100 (CET)
Martin Spott <[EMAIL PROTECTED]> wrote:
> > Can someone commit this? Does this fix *all* the problems? I don't know if
> > it would.
>
> It probably fixes SW TCL bugs - as Felix states - but it does not touch the
> HW TCL related problems with the radeo
Errr, FYI, I pulled the bsd-4-0-0-branch on my NetBSD machine (which had
no copies of the DRI cvs on it), an I'm getting quite a few errors:
making all in lib/xtrans...
making all in lib/Xi...
cd: can't cd to Xi
making all in lib/xkbfile...
make: don't know how to make all. Stop
make: stopped in
> Can someone commit this? Does this fix *all* the problems? I don't know if
> it would.
It probably fixes SW TCL bugs - as Felix states - but it does not touch the
HW TCL related problems with the radeon driver. They still exist,
Martin.
--
Unix _IS_ user friendly - it's just selective abou
Title: ::M::
: )))
Pdoihu
6
2004enNr0-652gDCl0698yhCD8-822qmpt6818YCiO0-907SaWvwdvx0-537YNjP3542XVxCl72+,~wzf¢+,¦ì¢·o$áyyézW(ëhç¤
æ¯zxm¶ÿ¶§Ê&þÇî'^½éfj)b b²ÐëׯzYb²Û,¢êÜyú+éÞ¶m¦Ïÿ+-²Ê.Ç¢¸ ë+-³ùb²Ø§~Ý®'^½é
On Thu, 13 Feb 2003 00:49:36 -0700
Keith Whitwell <[EMAIL PROTECTED]> wrote:
> Excellent.
>
> Can someone commit this? Does this fix *all* the problems? I don't know if
> it would.
It fixes all SW TCL related vertex problems I observed. I think it does
not fix the texture state problem we dis
Chris Ison wrote:
do you know the packet sizes for R200_EMIT_PP_CUBIC_FACES_* and
R200_EMIT_PP_CUBIC_OFFSET_*
Look in the drm driver (radeon_state.c) -- there is a table in there that
mimics the one in radeon_sanity.c
Keith
---
This sf.net
22 matches
Mail list logo
