[Dri-devel] Mach64-0-0-4-branch currently unusable

2002-04-25 Thread Felix Kühling
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? Peter

[Dri-devel] Tired Of Your High Mortgage Rate - REFINANCE TODAY...

2002-04-25 Thread Sanda8285u13
Warning Unable to process data: multipart/mixed;boundary="=_NextPart_000_00A2_56E41D5C.D5662C28"

[Dri-devel] Radeon Card Features DRI Checklist.

2002-04-25 Thread Smitty
Howzit? Here is my "alpha" list of features I would apreciate feedback on what should be on the feature checklist, the grouping and most importantly the *status* of these features. (I deliberately included everything bar the kitchen sink that I can find so that I dont have to add them in futu

Re: [Dri-devel] Mach64 for ppc xf86-log etc

2002-04-25 Thread Peter Andersson
Perhaps this will solve some questions about what happens when the system craches when i run glxgears. After close inspection of the screen i get aftewards i have been able to make out the following by trying to combine the symbols in the "two" windows. But don´t trust the numbers or any detai

Re: [Dri-devel] Linux DRM update to 2.4.18 first draft.

2002-04-25 Thread Thomas Winischhofer
Keith Whitwell wrote: > > Thomas Winischhofer wrote: > > > > Jens Owen wrote: > > > > So far, nobody could explain to me what direction the current > > > > development is going which makes it necessary to update the SiS driver > > > > in a way that requires additional docs. The 3D routines are al

Re: [Dri-devel] Linux DRM update to 2.4.18 first draft.

2002-04-25 Thread Keith Whitwell
Thomas Winischhofer wrote: > > Jens Owen wrote: > > > So far, nobody could explain to me what direction the current > > > development is going which makes it necessary to update the SiS driver > > > in a way that requires additional docs. The 3D routines are all there, > > > changing the API is p

Re: [Dri-devel] Linux DRM update to 2.4.18 first draft.

2002-04-25 Thread Thomas Winischhofer
Jens Owen wrote: > > So far, nobody could explain to me what direction the current > > development is going which makes it necessary to update the SiS driver > > in a way that requires additional docs. The 3D routines are all there, > > changing the API is primitive... I am far from being an exper

Re: [Dri-devel] Linux DRM update to 2.4.18 first draft.

2002-04-25 Thread Jens Owen
Thomas, I'll let Mike respond to most of your questions, since he's creating the patch. Thomas Winischhofer wrote: > So far, nobody could explain to me what direction the current > development is going which makes it necessary to update the SiS driver > in a way that requires additional docs.

[Dri-devel] Quick question about FreeBSD

2002-04-25 Thread Adam K Kirchhoff
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 BSD specific branch? In short, is it possible to get DRI

Re: [Dri-devel] Mach64 for ppc xf86-log etc

2002-04-25 Thread Leif Delgass
On Thu, 25 Apr 2002, José Fonseca wrote: > >> Before attempt to do the above get debug info from the DRM, doing from > >> a X console as root: > >> After the computer has crashed send that kmsg. > > > > Attached aswell... > > There is no kernel oops there. Don't know if the last call there cou

Re: [Dri-devel] Linux DRM update to 2.4.18 first draft.

2002-04-25 Thread Mike Mestnik
--- Jens Owen <[EMAIL PROTECTED]> wrote: > > Mike Mestnik <[EMAIL PROTECTED]> wrote: > > *** FIX ME *** > > *** removing agpgart dependency on radeon *** > > was the only big change I made. > > Was this because the PCI GART functionality was added to the Radeon > driver? > > > Other changes made

Re: [Dri-devel] Linux DRM update to 2.4.18 first draft.

2002-04-25 Thread Thomas Winischhofer
Jens Owen wrote: > > Mike Mestnik wrote: > > > > sis renamed to i830 (or one was removed and the other added), I don't know about 830, but SiS has been added. These are not the same... > I realize the SiS driver is lagging behind in the current development > branch and will probably end up with

Re: [Dri-devel] Linux DRM update to 2.4.18 first draft.

2002-04-25 Thread Jens Owen
Mike Mestnik wrote: > > I have a good start on a Linux DRM update. Alan was right all linux-drm-2.4.0 > needed was rming Make.linux Imake mv Make.kernel to Make, theses are a given > for any and Linux DRM update, Great. > and *** FIX ME *** > *** removing agpgart dependency on radeon *** > was

Re: [Dri-devel] Mach64 for ppc xf86-log etc

2002-04-25 Thread Oly
Actually, this sounds like what happens if X crashes and drops you to a terminal without resetting some of the video. The screen is probably twice as wide and high as it should be for console, so the left "console window" is scan lines 0,2,4,.. and the right one is scan lines 1,3,5 - which wo

[Dri-devel] Linux DRM update to 2.4.18 first draft.

2002-04-25 Thread Mike Mestnik
I have a good start on a Linux DRM update. Alan was right all linux-drm-2.4.0 needed was rming Make.linux Imake mv Make.kernel to Make, theses are a given for any and Linux DRM update, and *** FIX ME *** *** removing agpgart dependency on radeon *** was the only big change I made. Other changes m

Re: [Dri-devel] Mach64 for ppc xf86-log etc

2002-04-25 Thread Peter Andersson
Michel Dänzer wrote: >On Thu, 2002-04-25 at 14:52, Peter Andersson wrote: > - Do the same steps as above with your opengl application. I can´t see that because i have to kill it before the computer (telnet) >> >responds to any commands. At least i think i am killing it (i am pr

RE: [Dri-devel] Mach64 for ppc xf86-log etc

2002-04-25 Thread Michel Dänzer
On Thu, 2002-04-25 at 14:27, Alexander Stohr wrote: > > Please do the following tasks via telnet and report > > back to the list: > > - See if there is any application consuming all processor (top). > > - Copy the Xfree86.0.log to a safe place and post it here. > > - Check if X is still run

Re: [Dri-devel] Mach64 for ppc xf86-log etc

2002-04-25 Thread Michel Dänzer
On Thu, 2002-04-25 at 14:52, Peter Andersson wrote: > > >> - Do the same steps as above with your opengl application. > >> > >> I can´t see that because i have to kill it before the computer (telnet) >> >responds to any commands. At least i think i am killing it (i am > >> pressing the x butto

Re: [Dri-devel] Mach64 for ppc xf86-log etc

2002-04-25 Thread Peter Andersson
>> - Do the same steps as above with your opengl application. >> >> I can´t see that because i have to kill it before the computer (telnet) >> responds >to any commands. At least i think i am killing it (i am >> pressing the x button and then things seem to work again (if you are >> using tel

RE: [Dri-devel] Mach64 for ppc xf86-log etc

2002-04-25 Thread Alexander Stohr
> Please do the following tasks via telnet and report > back to the list: > - See if there is any application consuming all processor (top). > - Copy the Xfree86.0.log to a safe place and post it here. > - Check if X is still running or not (ps -A | grep X) and > point down > it's pid, an

Re: [Dri-devel] Mach64 for ppc xf86-log etc

2002-04-25 Thread Michel Dänzer
On Thu, 2002-04-25 at 09:29, José Fonseca wrote: > > You could try to start the GL app (or even the X afterwards) by a remote > telnet connection. Just do > > gdb glxgears > run > continue(it always breakspoints due to the SSE extensions > check) No SSE on PPC, and no altive

Re: [Dri-devel] How to allocate DMA memory

2002-04-25 Thread José Fonseca
On 2002.04.24 23:53 José Fonseca wrote: > Since my last reply that Yahoo hasn't delivering emails to me and I'm > not sure if you'll receive this one or not either. To make things even > worse I'll be away for the next couple days and I don't expect to be > able to check my mail. It's working

Re: [Dri-devel] Mach64 for ppc xf86-log etc

2002-04-25 Thread José Fonseca
Peter, This is just a very quick reply on the few minutes I have before leaving. I'm sure that someone else on the list may elaborate further and give you indications to what try next. On 2002.04.25 02:02 Peter Andersson wrote: > ... > >> - Copy the Xfree86.0.log to a safe place and post it