Re: R300 DRI report

2005-07-29 Thread Martin Spott
Vladimir Dergachev wrote: > You could also try FlightGear as far as games go. Yep, this had been proven to trigger even the obscurest bug during the emergence of the r200 driver ;-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! --

Re: R300 success stories

2005-02-16 Thread Martin Spott
Hello, Adam K Kirchhoff wrote: > These are the games I've tried with the latest CVS from this afternoon: [...] > Frankly, I'm thrilled at the handful of games that are now working! Those who are looking for additional stress-test cases for OpenGL- (especially R300-, I don't have one myself) dri

Re: [Mesa3d-dev] Doom3 works on R200!

2004-10-25 Thread Martin Spott
Vladimir Dergachev wrote: > What could work, however, is to make a *board* that is capable of decent > 3d. Put lots of memory, lots of bandwidth and several DSP to approximate > the same level of raw floating-point power as 3d GPUs. Leave everything > else to the software. This reminds me of "

Re: [Dri-devel] new API/DRM/fb discsusion..

2004-05-06 Thread Martin Spott
Vladimir Dergachev wrote: > Also, I would venture an opinion that, at the moment, the only Unices we > care about is Linux, BSD and Hurd - all open source. The current design > of XFree86 (with everything done in userspace) was motivated by the need > to support commercial Unices (like Solaris or

Re: [Dri-devel] Which DRI driver/card is usable for modern games?

2004-05-06 Thread Martin Spott
Svante Signell wrote: > However, my original question remain: Which card is usable with DRI open > source drivers for modern games? I probably don't run "modern games" but I use FlightGear which apparently has quite a few sophisticated requirements. I use Radeon9100/9200 cards and I'm very happy

Re: [Dri-devel] Gains from doing 2D drawing using OpenGL/mesa

2004-04-26 Thread Martin Spott
Martin Spott wrote: > Alex Deucher wrote: >> I don't know about that. I can forsee IGP becoming _the_ standard >> method for video. Look at sgi... all of their video systems use >> system memory, [...] > Really ? Which one ? > I know the O2 does, but MGRAS an

Re: [Dri-devel] Gains from doing 2D drawing using OpenGL/mesa

2004-04-22 Thread Martin Spott
Alex Deucher wrote: > --- Martin Spott <[EMAIL PROTECTED]> wrote: >> Really ? Which one ? >> I know the O2 does, but MGRAS and VPro ? I'm not absolutely sure >> but I assume they have memory on their respective graphic boards, at >> least they have t

Re: [Dri-devel] Gains from doing 2D drawing using OpenGL/mesa

2004-04-22 Thread Martin Spott
Alex Deucher wrote: > I don't know about that. I can forsee IGP becoming _the_ standard > method for video. Look at sgi... all of their video systems use > system memory, [...] Really ? Which one ? I know the O2 does, but MGRAS and VPro ? I'm not absolutely sure but I assume they have me

Re: [Dri-devel] New DRI driver interface (Re: CVS Update: xc (branch:

2004-02-12 Thread Martin Spott
Ian Romanick <[EMAIL PROTECTED]> wrote: > It looks like I should be able to convert the MGA driver today, but I > can't make any guarantees. I'd prefer the 'radeon' driver, because I gave my r200 card to my friend ;-) Martin. -- Unix _IS_ user friendly - it's just selective about who its fri

Re: [Dri-devel] New DRI driver interface (Re: CVS Update: xc (branch:

2004-02-12 Thread Martin Spott
Ian Romanick <[EMAIL PROTECTED]> wrote: >> 3. After some testing and "cool down" period, merge the branch into the >> trunk. I expect this to happen fairly quickly. > In-progress. Please test this branch! :) Would I notice any difference on a non-r200 card or do your changes affect r200 only

Re: [Dri-devel] DRI newmesa merge

2003-12-10 Thread Martin Spott
"David D. Hagood" <[EMAIL PROTECTED]> wrote: > Felix Kühling wrote: >> It would be annoying for people with dialup connections if make required >> access to a remote CVS repository. > And how would that be any different than syncing up with the main DRI > CVS repo? If you are building one from C

Re: [Dri-devel] Adding hardware detection to DRI drivers

2003-10-16 Thread Martin Spott
Alex Deucher <[EMAIL PROTECTED]> wrote: > Would he be interested in contributing his work back? or maybe > explaining how/if he got it working? Sorry, currently he's forced to finish his dissertation. He says you might have to wait at least a month until he'll be able to deal with that, Martin. -

Re: [Dri-devel] Adding hardware detection to DRI drivers

2003-10-16 Thread Martin Spott
On Thu, Oct 16, 2003 at 06:30:53AM -0700, Alex Deucher wrote: > Would he be interested in contributing his work back? or maybe > explaining how/if he got it working? I'll ask him - he moved to southern Germany earlier this year, Martin. -- Unix _IS_ user friendly - it's just selective ab

Re: [Dri-devel] Major mergedFB rework committed to CVS

2003-10-16 Thread Martin Spott
Alex Deucher <[EMAIL PROTECTED]> wrote: > I can switch back to the old order in the mean time, however, I'm not > sure if it is any more or less reliable than the current code. both > work fine on my hardware. I just rebuilt the stuff with a CVS checkout from one hour before now. When I do _not_

Re: [Dri-devel] Adding hardware detection to DRI drivers

2003-10-16 Thread Martin Spott
Ville Syrj?l? <[EMAIL PROTECTED]> wrote: > On Wed, Oct 15, 2003 at 03:48:38PM -0700, Alex Deucher wrote: >> there's also this driver: >> >> http://www.instmath.rwth-aachen.de:8000/linux/G450-PCI/ >> >> I'm not sure how the G4/550 and G200 differ in regard to PCI vs. AGP... > AFAIK G450 PCI cards

Re: [Dri-devel] Major mergedFB rework committed to CVS

2003-10-13 Thread Martin Spott
On Mon, Oct 13, 2003 at 09:03:38AM -0700, Alex Deucher wrote: > That's what I'm not clear on. when you say "XFree86 X server binary" > do you mean /usr/X11R6/bin/XFree86 or radeon_drv.o? I assume you mean > the latter. /usr/X11R6/bin/XFree86 has no mergedfb specific code in > it. that is all t

Re: [Dri-devel] Major mergedFB rework committed to CVS

2003-10-13 Thread Martin Spott
On Mon, Oct 13, 2003 at 06:56:32AM -0700, Alex Deucher wrote: > Can you clarify what you tried and what the problem is? When I restart the 'new' (with MergedFB) XFree86 X server binary with the old XF86Config (attached) I get a flickering screen with a resolution that is obviously below what I usu

Re: [Dri-devel] Video Memory Corruption

2003-10-13 Thread Martin Spott
Chris Ison <[EMAIL PROTECTED]> wrote: > --Boundary_(ID_KcARw6HFWym7RIWbxkMyIg) > Content-type: text/plain > Content-transfer-encoding: 7BIT > > can someome please tell me whats causing the video corruption in the > attached png image, and explain how to fix it. I'd say the main bug is _YOU_ post

Re: [Dri-devel] Major mergedFB rework committed to CVS

2003-10-13 Thread Martin Spott
Alex Deucher <[EMAIL PROTECTED]> wrote: > I just committed a major rework of mergedfb to CVS. almost all of the > code is now in radeon_mergedfb.c/h. I also committed Hui's latest code > drop from xfree86 CVS. Let me know if anyone has any problems. I'm fine with running the 'new' X server _modu

Re: [Dri-devel] config branch merge schedule

2003-09-30 Thread Martin Spott
Jos? Fonseca <[EMAIL PROTECTED]> wrote: > Anyway, I'm now building a snapshot. If it succeeds please do a public > request for testing on the dri-users and dri-devel. probably combined with a short list of common pitfalls ? Martin. -- Unix _IS_ user friendly - it's just selective about wh

Re: [Dri-devel] FlightGear test with recent CVS

2003-09-17 Thread Martin Spott
Martin Spott <[EMAIL PROTECTED]> wrote: > I just did a small test with FlightGear against the recent CVS checkout > from freedesktop and I'm delighted. Everything works as expected, I forgot to mention, that I'm running stock DRM kernel modules from Linux-2.6.0-test5

[Dri-devel] FlightGear test with recent CVS

2003-09-17 Thread Martin Spott
I just did a small test with FlightGear against the recent CVS checkout from freedesktop and I'm delighted. Everything works as expected, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -

Re: [Dri-devel] Merge fixups

2003-09-16 Thread Martin Spott
Alan Hourihane <[EMAIL PROTECTED]> wrote: > O.k. I've completed the merge fixups and doing a test build now. Great. > I'm going to tag the trunk with trunk-20030916 if everything goes well. It would be helpful if Jose would update his mirror so other people could test as well, Martin. -- Unix

Re: [Dri-devel] XFree86 merge

2003-09-12 Thread Martin Spott
Alan Hourihane <[EMAIL PROTECTED]> wrote: > But I also tagged it before starting, so if someone wants to branch for > a stable tree you can do it off the trunk-20030912 tag. Did this already happen on 'freedesktop.org' or still on SF ? Martin. -- Unix _IS_ user friendly - it's just selective a

Re: [Dri-devel] Re: CVS Update: xc (branch: trunk)

2003-09-09 Thread Martin Spott
Alex Deucher <[EMAIL PROTECTED]> wrote: > [...] you can still find > 300/305 PCI/AGP cards on some websites usually labeled as "sis 305 > 32mb" or similar. Thanks for explaining. I assume I found a card with an SiS 315. I'll see if it works, otherwise I'll give it to a friend running Windows .

Re: [Dri-devel] Re: CVS Update: xc (branch: trunk)

2003-09-08 Thread Martin Spott
Alex Deucher <[EMAIL PROTECTED]> wrote: >> Eric Anholt <[EMAIL PROTECTED]> wrote: >> >> > If anyone wants to test, [...] >> >> Which video card would you recommend for trying ? I'd see if I can >> get one, >> > An card from the 300 series sis cards should work: > 300, 305, 540, 630/S/ST, 730 O

Re: [Dri-devel] Re: CVS Update: xc (branch: trunk)

2003-09-06 Thread Martin Spott
Eric Anholt <[EMAIL PROTECTED]> wrote: > If anyone wants to test, [...] Which video card would you recommend for trying ? I'd see if I can get one, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -

Re: [Dri-devel] Re: [OT] Sourceforge CVS

2003-09-03 Thread Martin Spott
Chris Ison <[EMAIL PROTECTED]> wrote: > DRI is still quite young and alot of people still have the "Screw you > Billy Goat" attitude, [...] Please remember that DRI is not Linux, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! --

Re: [Dri-devel] Re: [OT] Sourceforge CVS

2003-09-03 Thread Martin Spott
Larry McVoy <[EMAIL PROTECTED]> wrote: > People claim that our license is a problem but the only real problem is > the people making the noise. [...] Things are getting ridiculous when you start to superimpose your attitude towards ethics on others - especially when you are obviously lacking the

Re: [Dri-devel] Re: [OT] Sourceforge CVS

2003-09-03 Thread Martin Spott
Larry McVoy <[EMAIL PROTECTED]> wrote: > On Wed, Sep 03, 2003 at 02:17:19PM +0100, Alan Cox wrote: >> On Maw, 2003-09-02 at 19:42, Jon Smirl wrote: >> > There are 31 people with write access to dri.sf.net. The simplest solution >> > would be for those 31 to switch to BitKeeper. > If thos 31 are OK

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-03 Thread Martin Spott
Larry McVoy <[EMAIL PROTECTED]> wrote: > On Wed, Sep 03, 2003 at 02:17:19PM +0100, Alan Cox wrote: >> On Maw, 2003-09-02 at 19:42, Jon Smirl wrote: >> > There are 31 people with write access to dri.sf.net. The simplest solution >> > would be for those 31 to switch to BitKeeper. > If thos 31 are O

Re: [Dri-devel] radeon error

2003-09-03 Thread Martin Spott
Keith Whitwell <[EMAIL PROTECTED]> wrote: > Martin Spott wrote: >> I'm running a quite up-to-date mirror in Germany - currently without public >> access, but we could change this. Though this mirror suffers from absence of >> the SF server too > What sort

[Dri-devel] Re: CVS Update: xc (branch: trunk)

2003-09-03 Thread Martin Spott
Ian Romanick <[EMAIL PROTECTED]> wrote: > CVSROOT: /cvsroot/dri > Module name: xc > Repository: xc/xc/lib/GL/glx/ > Changes by: [EMAIL PROTECTED] 03/09/02 14:47:24 > Log message: > Fixed a typo that caused problems linking (but not running) > applications. Thanks a lot - I was

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-02 Thread Martin Spott
Jon Smirl <[EMAIL PROTECTED]> wrote: > The BitKeeper people have said they would love to be the host for DRI/Mesa > source. We would still leave bug tracking, web pages, etc at Sourceforge. Only > the source code would move. This reheats the discussion about a BK to CVS gateway. There is one for t

Re: [Dri-devel] radeon error

2003-09-02 Thread Martin Spott
Thomas Emmel <[EMAIL PROTECTED]> wrote: > and this message means that the CVS-server is full. > I think this was mentioned before two days ago. > Some days before I had the problem that the download hangs in > xc/xc/util/patch infinitely. Now I tried to download completely > from scratch without

Re: [Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: trunk)

2003-08-25 Thread Martin Spott
Martin Spott <[EMAIL PROTECTED]> wrote: > Ian Romanick <[EMAIL PROTECTED]> wrote: >> CVSROOT: /cvsroot/dri >> Module name: xc >> Repository: xc/xc/programs/Xserver/hw/xfree86/drivers/ati/ >> Changes by: [EMAIL PROTECTED] 03/08/08 13:34:08 >&

[Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: trunk)

2003-08-14 Thread Martin Spott
Ian Romanick <[EMAIL PROTECTED]> wrote: > CVSROOT: /cvsroot/dri > Module name: xc > Repository: xc/xc/programs/Xserver/hw/xfree86/drivers/ati/ > Changes by: [EMAIL PROTECTED] 03/08/08 13:34:08 > Log message: > Removed the R{ADEON,200}_AGP_TEX_OFFSET contant as it's not really a >

Re: [Dri-devel] Congratulations to recent changes

2003-07-29 Thread Martin Spott
Keith Whitwell <[EMAIL PROTECTED]> wrote: > Anyway, I'm glad this fixed your problem. Yep, now I can continue to promote the use ATI boards in the FlightGear manua ;-) If anyone likes, I now have a different one. This shows up with HW-TCL only when I use more komplex textured aircrafts. Wit

[Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: trunk)

2003-07-29 Thread Martin Spott
Michel Daenzer <[EMAIL PROTECTED]> wrote: > CVSROOT: /cvsroot/dri > Module name: xc > Repository: xc/xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/ > Changes by: [EMAIL PROTECTED] 03/07/29 03:11:48 > Log message: > * IRQ code cleanup suggested by Linus Torvalds >

[Dri-devel] Congratulations to recent changes

2003-07-28 Thread Martin Spott
Currently I don't know _what_ has been changed because ATM I don't have access to the mailing list. But there _must_ have been substantial changes because apparently the "too dark lightning with TCL on Radeon" bug has been fixed. Running FlightGear on a Radeon9100 with the R200 driver I can't tell

Re: [Dri-devel] searching for other CVS or RSYNC mirror of DRI trunk

2003-07-23 Thread Martin Spott
Martin Zimmermann <[EMAIL PROTECTED]> wrote: > Maybe we can collect a list of all known and maybe tested mirror pages ... > and repost on [EMAIL PROTECTED] > > 1. rsync -avz --delete rsync://mefriss1.swan.ac.uk/dri/HEAD/ HEAD/ > > 2. I'm currently trying to collect experience on how reliable I

Re: [Dri-devel] 3 bugs with DRI on ATI radeon 7500 M7 card

2003-07-21 Thread Martin Spott
Michel D?nzer <[EMAIL PROTECTED]> wrote: > On Mon, 2003-07-21 at 22:33, Martin Spott wrote: >> Ian Romanick <[EMAIL PROTECTED]> wrote: >> [...] >> > 3. Since all three cases center around the use of materials, I think >> > it's really just

Re: [Dri-devel] FW: What's going on DRI cvs server

2003-07-21 Thread Martin Spott
Alexander Stohr <[EMAIL PROTECTED]> wrote: > can someone answer this request for DRI tarballs? The required link is about on the middle of the WWW main page, I think he can't miss it if he tries, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! --

Re: [Dri-devel] 3 bugs with DRI on ATI radeon 7500 M7 card

2003-07-21 Thread Martin Spott
Ian Romanick <[EMAIL PROTECTED]> wrote: [...] > 3. Since all three cases center around the use of materials, I think > it's really just one bug. Does anyone know if NWN or Fightgear use > glMaterial? Maybe some FlightGear developer can comment on this ? Martin. -- Unix _IS_ user friendly - i

Re: [Dri-devel] radeon 9200 tester available

2003-07-09 Thread Martin Spott
Rupert Levene <[EMAIL PROTECTED]> wrote: > On Thu, Jul 03, 2003 at 01:07:28AM +0200, Michel Dänzer wrote: >> PS: http://levene.dyndns.org/invisible-text/normal.png does show a >> driver problem - the lighting is wrong with HW TCL - but you didn't >> report that... ;) > Well I'd assumed that _this

Re: [Dri-devel] Only "normal" DRI and Mesa CVS access as developer, now?

2003-06-23 Thread Martin Spott
Jos? Fonseca <[EMAIL PROTECTED]> wrote: > If not then the solution would imply moving the CVS repository to a new > machine, but where would that be? XFree86.org? Some SF look-a-like? As far as I know BerliOS is hosting quite a few OpenSource projects. This is intended to be some SF alternative.

Re: [Dri-devel] Torque Engine causes machine lockup on radeon mobility M7

2003-06-20 Thread Martin Spott
Zik Saleeba <[EMAIL PROTECTED]> wrote: > Running the Torque Engine example application > (http://www.garagegames.com/) runs for a few frames and then locks the > system up. X is completely hung and it can't be killed. Remote logins > to the machine are possible but the display is frozen until reboo

Re: [Dri-devel] CVS Update: xc (branch: trunk)

2003-06-18 Thread Martin Spott
Jos? Fonseca <[EMAIL PROTECTED]> wrote: > I'm going to see if I can reproduce the problem and solve it. I'd like to help if anyone suggests how to do so, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! ---

Re: [Dri-devel] CVS Update: xc (branch: trunk)

2003-06-16 Thread Martin Spott
Roland Scheidegger <[EMAIL PROTECTED]> wrote: > FWIW, I get that now always when I start the X server, then shut down > the X server and start it again. DRI will never work again, unless I > rmmod the radeon module manually before I restart the X server. Sounds > like some initialization thing.

Re: [Dri-devel] CVS Update: xc (branch: trunk)

2003-06-16 Thread Martin Spott
On Mon, Jun 16, 2003 at 03:47:10PM +0200, Martin Spott wrote: > I've attached the DRM patch I'm talking about the whole time. You might > compare it with yours to see, if my CVS tree is missing some part. The patch > applies against stock 2.4.20 kernel DRM. Stupid - sorry f

Re: [Dri-devel] CVS Update: xc (branch: trunk)

2003-06-16 Thread Martin Spott
On Mon, Jun 16, 2003 at 02:31:45PM +0100, José Fonseca wrote: > On Mon, Jun 16, 2003 at 01:48:35PM +0200, Martin Spott wrote: > > (II) RADEON(0): Direct rendering disabled > > This can't be. This log can't possible match the other one you gave me. > In the /var/lo

Re: [Dri-devel] CVS Update: xc (branch: trunk)

2003-06-16 Thread Martin Spott
On Mon, Jun 16, 2003 at 11:46:43AM +0100, José Fonseca wrote: > And everything else looks normal - the AGP seems to be alive and > kicking. Do you still get "direct rendering: No" in glxinfo or "AGP not > available" in /var/log/messages ? As I already said: Yes. Now I rebuilt the kernel modules f

Re: [Dri-devel] CVS Update: xc (branch: trunk)

2003-06-16 Thread Martin Spott
On Mon, Jun 16, 2003 at 11:46:43AM +0100, José Fonseca wrote: > And everything else looks normal - the AGP seems to be alive and > kicking. Do you still get "direct rendering: No" in glxinfo or "AGP not > available" in /var/log/messages ? Yep: 1.) /var/log/XFree86.0.log tells me (II) RADEON(0):

Re: [Dri-devel] CVS Update: xc (branch: trunk)

2003-06-16 Thread Martin Spott
Hello Jose (I don't know how to type the accent on my keyboard), On Sun, Jun 15, 2003 at 09:21:18PM +0200, Martin Spott wrote: > I'll redo the debug output on monday - just to make shure I did not make any > mistake. I'm doing this with an OEM Radeon9100. Unfortu

Re: [Dri-devel] CVS Update: xc (branch: trunk)

2003-06-15 Thread Martin Spott
On Sun, Jun 15, 2003 at 07:47:35PM +0100, José Fonseca wrote: > Something fishy is going on here. My debug statements never appear in > your log and I've just retested on my test box with the latest CVS and > everything works as expected with the radeon driver: [...] > Martin, are you're sure you'

Re: [Dri-devel] CVS Update: xc (branch: trunk)

2003-06-13 Thread Martin Spott
Martin Spott <[EMAIL PROTECTED]> wrote: > I applied both of Jose's patches and loaded the 'radeon' module with > drm_opts=debug as suggested my Michel. I attached the compressed debug > output from loading the module until X server startup that I found in > /va

Re: [Dri-devel] CVS Update: xc (branch: trunk)

2003-06-13 Thread Martin Spott
> Content-Disposition: attachment; filename="drm_agp-debug2.diff" I applied both of Jose's patches and loaded the 'radeon' module with drm_opts=debug as suggested my Michel. I attached the compressed debug output from loading the module until X server startup that I found in /var/log/messages. If

Re: [Dri-devel] CVS Update: xc (branch: trunk)

2003-06-12 Thread Martin Spott
On Thu, Jun 12, 2003 at 12:19:17PM +0200, Michel Dänzer wrote: > On Thu, 2003-06-12 at 08:42, Martin Spott wrote: > > I applied your patch but I did not notice where the expected debug output > > should appear. Should it show up on STDERR, in the syslog, in XFree ? > > W

Re: [Dri-devel] CVS Update: xc (branch: trunk)

2003-06-11 Thread Martin Spott
Hello Jose, > Since it's easy for you to rebuild the kernel module, try the attached > patch which adds a debug output line. That line should appear, and both > pointers should be non-NULL. I applied your patch but I did not notice where the expected debug output should appear. Should it show up

Re: [Dri-devel] CVS Update: xc (branch: trunk)

2003-06-11 Thread Martin Spott
On Wed, Jun 11, 2003 at 07:25:06PM +0100, José Fonseca wrote: > How can't see how the above two logs match. Which driver version are you > using, the latest? The base I'm running tests on is the XFree86-4.3.0 update to SuSE-8.1 (which I have a backup of ;-) Then I'm running 'make World' in a co

[Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: trunk)

2003-06-11 Thread Martin Spott
Jose Fonseca <[EMAIL PROTECTED]> wrote: > CVSROOT: /cvsroot/dri > Module name: xc > Repository: xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/ > Changes by: [EMAIL PROTECTED] 03/06/03 16:27:02 > Log message: > Split declarations/definitions in drm_scatter.h into d

Re: [Dri-devel] [RFC] New Xv adapter using MESA_ycbcr_texture

2003-06-06 Thread Martin Spott
"Matt Sealey" <[EMAIL PROTECTED]> wrote: >> > I'm sure that MPlayer or Xine actually support an OpenGL output >> > plugin already. Chances are it's Xine, but I haven't touched it in >> > 6 months, maybe they removed it? >> >> I believe it's still there. Before propagating the use of 'new' API's i

Re: [Dri-devel] [RFC] New Xv adapter using MESA_ycbcr_texture

2003-06-05 Thread Martin Spott
"Matt Sealey" <[EMAIL PROTECTED]> wrote: > I'm sure that MPlayer or Xine actually support an OpenGL output > plugin already. Chances are it's Xine, but I haven't touched it in > 6 months, maybe they removed it? I believe it's still there. Before propagating the use of 'new' API's in Xinre for exa

Re: [Dri-devel] Fresh DRI driver snapshots - call for testers

2003-04-04 Thread Martin Spott
On Fri, Apr 04, 2003 at 03:59:16PM +0200, Michel Dänzer wrote: > On Fre, 2003-04-04 at 14:56, Martin Spott wrote: > > This remembers me of a question that came up recently: Some of the changes > > that recently were made to the XFree86 CVS repository touch files that are > >

Re: [Dri-devel] Fresh DRI driver snapshots - call for testers

2003-04-04 Thread Martin Spott
Jos? Fonseca <[EMAIL PROTECTED]> wrote: > FYI these snapshots were built by checking out the DRI CVS over the > XFree86 4.3.0 source [...] This is tough - I didn't think it would work :-) This remembers me of a question that came up recently: Some of the changes that recently were made to the X

Re: [Dri-devel] thanks for the XFree-merge

2003-03-31 Thread Martin Spott
Martin Spott <[EMAIL PROTECTED]> wrote: > Ian Romanick <[EMAIL PROTECTED]> wrote: >> I'm going to freeze the texmem-0-0-1 branch and begin the arduous task of >> merging the trunk. Since I'm not quite as experienced at doing merges >> as Alan,

Re: [Dri-devel] thanks for the XFree-merge

2003-03-28 Thread Martin Spott
Ian Romanick <[EMAIL PROTECTED]> wrote: > Since it appears that the filp work has been merged in to the trunk, [...] Oh, I noticed too late > I'm going to freeze the texmem-0-0-1 branch and begin the arduous task of > merging the trunk. Since I'm not quite as experienced at doing merges

[Dri-devel] thanks for the XFree-merge

2003-03-28 Thread Martin Spott
I'd like to express my thanks for the merge of XFree86-4.3 and the related work. The current 'trunk' is the most stable and accurate implementation of hw- accelerated OpenGL I've seen on Linux with a Radeon (in my case) for quite some time (as long as you factor out the light position issues with

Re: [Dri-devel] XFree86-4.3 DRI and kernel-2.5.X

2003-03-25 Thread Martin Spott
Louis Garcia <[EMAIL PROTECTED]> wrote: > Is their anyway I can get a diff for XFree86-4.3 DRI against 2.5.latest? > I'm starting to play with this kernel and want dri working for my > radeon. Diff against what ? XFree86-4.3.0 should work fine 'out of the box' with Linux-2.5.x. I've already tried

Re: [Dri-devel] 4.3.0 merge

2003-03-24 Thread Martin Spott
Jens Owen <[EMAIL PROTECTED]> wrote: > Keith Whitwell wrote: >> Alan Hourihane wrote: >> >>> I'm going to start the 4.3.0 merge. Be prepared for breakage. >>> >>> I'll post another followup when I'm finished. >> >> >> Thanks for doing this, Alan. > Definitely. Thanks, Alan. Oh yes, this way w

Re: [Dri-devel] Re: [forum] Re: [XFree86] Invitation for public discussion about the future of X

2003-03-20 Thread Martin Spott
Philip Brown <[EMAIL PROTECTED]> wrote: > Perhaps then, this will provide enough incentive for DRI to move back into > a pure extension module form, rather than its current xfree tree > entanglement. You don't want to imply that people touch bigger areas as is would be necessary for DRI developme

Re: [Dri-devel] Re: [forum] Re: [XFree86] Invitation for public discussion about

2003-03-20 Thread Martin Spott
Keith Whitwell <[EMAIL PROTECTED]> wrote: > It's always a shock to see that what is meant to tease when written comes out > looking more like a direct attack when read back... Oh, I would agree even if it was considered as sort of an attack, Martin. -- Unix _IS_ user friendly - it's just sele

Re: [Dri-devel] Serious Sam: 2nd Edition crash

2003-03-17 Thread Martin Spott
Michel D?nzer <[EMAIL PROTECTED]> wrote: > BTW, are you actually using 4x transfer rate? If so, have you tried > lowering it? I't like to note that the lockups I saw with FlightGear and Solace were completely independent from the AGP transfer rate of my Radeon7500. I did quite a few tests to be s

Re: [Dri-devel] Serious Sam: 2nd Edition crash

2003-03-17 Thread Martin Spott
Michel D?nzer <[EMAIL PROTECTED]> wrote: > You could try to set the environment variables RADEON_NO_CODEGEN, > RADEON_NO_VTXFMT and RADEON_TCL_FORCE_DISABLE [...] BTW, I just aquired a Radeon9100 clone to see if serveral 'features' resemble the behav

Re: [Dri-devel] Serious Sam: 2nd Edition crash

2003-03-17 Thread Martin Spott
On Mon, Mar 17, 2003 at 02:41:43PM +0100, Michel Dänzer wrote: > On Mon, 2003-03-17 at 14:11, Martin Spott wrote: > > Michel D?nzer <[EMAIL PROTECTED]> wrote: > > Changes by: [EMAIL PROTECTED] 03/03/12 05:54:45 > > > > Log message: > > Fix recycle l

Re: [Dri-devel] Serious Sam: 2nd Edition crash

2003-03-17 Thread Martin Spott
Michel D?nzer <[EMAIL PROTECTED]> wrote: > The texmem branch doesn't have the FlushVertices fix yet, which seems to > help with a number of lockups. Try > http://penguinppc.org/~daenzer/DRI/applied/r200-radeon-flushvertices.diff If it does not work, try this one - I never experienced any Radeon-l

Re: [Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: mesa-4-0-4-branch)

2003-03-13 Thread Martin Spott
Martin Spott <[EMAIL PROTECTED]> wrote: > Keith Whitwell <[EMAIL PROTECTED]> wrote: >> CVSROOT: /cvsroot/dri >> Module name: xc >> Repository: xc/xc/programs/Xserver/hw/xfree86/drivers/ati/ >> Changes by: [EMAIL PROTECTED] 03/03/12 05:54:45

[Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: mesa-4-0-4-branch)

2003-03-12 Thread Martin Spott
Keith Whitwell <[EMAIL PROTECTED]> wrote: > CVSROOT: /cvsroot/dri > Module name: xc > Repository: xc/xc/programs/Xserver/hw/xfree86/drivers/ati/ > Changes by: [EMAIL PROTECTED] 03/03/12 05:54:45 > Log message: > Fix recycle lockup (Michel Danzer) > Modified files: > xc/xc/

Re: [Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: trunk)

2003-03-04 Thread Martin Spott
Martin Spott <[EMAIL PROTECTED]> wrote: > Michel Daenzer <[EMAIL PROTECTED]> wrote: >> CVSROOT: /cvsroot/dri >> Module name: xc >> Repository: xc/xc/lib/GL/mesa/src/drv/radeon/ >> Changes by: [EMAIL PROTECTED] 03/03/03 17:02:35 >> Log mess

[Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: trunk)

2003-03-04 Thread Martin Spott
Michel Daenzer <[EMAIL PROTECTED]> wrote: > CVSROOT: /cvsroot/dri > Module name: xc > Repository: xc/xc/lib/GL/mesa/src/drv/radeon/ > Changes by: [EMAIL PROTECTED] 03/03/03 17:02:35 > Log message: > Set Mesa hooks to flush vertices on state changes (Keith Whitwell) Whps, it

Re: [Dri-devel] Remote OpenGL

2003-03-03 Thread Martin Spott
Philip Brown <[EMAIL PROTECTED]> wrote: > On Sun, Mar 02, 2003 at 10:33:15PM +0000, Martin Spott wrote: >> I don't know _why_ this works > because you're not using DRI. > DRI essentially for Xserver-side stuff. The X server is on the SGI. That's quite cl

[Dri-devel] Remote OpenGL

2003-03-02 Thread Martin Spott
Hello, did you know that remote display of OpenGL apps is partially functional with DRI ? At least the client side works ! I'm currently running FlightGear on a Linux PC against an SGI Octane functioning as X terminal. Performance is not bad - at least better than running FlightGear native on the (

Re: [Dri-devel] Re: future of DRI? -> why no one plays with Glide3.

2003-03-01 Thread Martin Spott
"Mike A. Harris" <[EMAIL PROTECTED]> wrote: > On Sat, 1 Mar 2003, Smitty wrote: >>Which is probably why Molton is trying to instigate a divorce >>from Glide for the V3. > I certainly support that move. Anholt was working on Glide3 > recently a bit as well. I dunno how far he got, but I've been

Re: [Dri-devel] GL image distortions with Radeon VE

2003-02-28 Thread Martin Spott
Nick Kurshev <[EMAIL PROTECTED]> wrote: > Image distortion became visible in oct 2002. This probably was the time when hardware-TCL came into play !? You could try to set $RADEON_TCL_FORCE_DISABLE to 't' and see if it makes any difference, Martin. -- Unix _IS_ user friendly - it's just selecti

Re: [Dri-devel] Using DRI to implement 2D X drivers

2003-02-27 Thread Martin Spott
Michel D?nzer <[EMAIL PROTECTED]> wrote: > The radeon driver uses the DRM for 2D acceleration when DRI is enabled, Is the radeon driver the only one doing so ? Is it possible that heavy simultaneous use of 2D and 3D graphics is responsible for the DRM freezing the X server with FlightGear ? You r

[Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: drm-filp-0-1-branch)

2003-02-26 Thread Martin Spott
Keith Whitwell <[EMAIL PROTECTED]> wrote: > CVSROOT: /cvsroot/dri > Module name: xc > Repository: xc/xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/ > Changes by: [EMAIL PROTECTED] 03/02/24 19:59:01 > Log message: > Use file pointers instead of pids for resource and

Re: [Dri-devel] Radeon 9000Pro hangs with current DRM

2003-02-26 Thread Martin Spott
Alan Cox <[EMAIL PROTECTED]> wrote: > What chipset. My problems are AGP 1x on AMD 75x series Mine runs on a Via Apollo Pro (ASUS P3V 4X), AGP 1x crashes as well as AGP 4x. I tried playing "EnablePageflip", but this does not make any difference either, Martin. -- Unix _IS_ user friendly - it's

Re: [Dri-devel] Radeon 9000Pro hangs with current DRM

2003-02-24 Thread Martin Spott
Alan Cox <[EMAIL PROTECTED]> wrote: > With the older code I could play cube for hours, with the texture upload > that fixes the hang on fg, its a matter of mintues Oh, I know, some of the CVS branches that were floating around have been quite stable with FlightGear. Ian's 'texmem-0-0-1' was quite

Re: [Dri-devel] Radeon 9000Pro hangs with current DRM

2003-02-24 Thread Martin Spott
Alan Cox <[EMAIL PROTECTED]> wrote: > With a 747 it starts up, I get a cockpit, I turn up the engines taxi down > the runway and embed the nose in the ground. I can't fly a 747 but I don't > see the problem you reported Thanks for the test. Maybe we have too look at the differences between a Rade

Re: [Dri-devel] module release method, threads, pids

2003-02-24 Thread Martin Spott
Felix K?hling <[EMAIL PROTECTED]> wrote: > No idea, just a comment. This reminded me of the famous X hangs when > flightgear exits. Recently I read in some posts on the plib-users > mailing list that flightgear is multi-threaded, too. The situation is > somewhat different, though. There is only on

Re: [Dri-devel] Radeon 9000Pro hangs with current DRM

2003-02-24 Thread Martin Spott
Alan Cox <[EMAIL PROTECTED]> wrote: > I updated the radeon DRM to include the texture upload changes. My > radeon hang with flightgear now happens every two hours instead of > instantly. Would you please be so kind to try the B747 ? Please run FG with the option: --aircraft=747-yasim > When it d

Re: [Dri-devel] Lock problem with Radeon DRI

2003-02-18 Thread Martin Spott
On Tue, Feb 18, 2003 at 02:34:29PM -0500, Leif Delgass wrote: > On Tue, 18 Feb 2003, Martin Spott wrote: > > So are we going to see XFree86-4.3.0 with broken Radeon DRI drivers ? > I noticed that Michel's fix for large textures in > radeon_cp_dispatch_texture() has only been

Re: [Dri-devel] Lock problem with Radeon DRI

2003-02-18 Thread Martin Spott
> How can get a new module? Do I have to build XF86 from source No, you don't have to rebuild the whole XFree86. I usually take the Sources from: xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/ xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/ and adjust the Makefile

Re: [Dri-devel] Lock problem with Radeon DRI

2003-02-18 Thread Martin Spott
On Fri, Feb 14, 2003 at 04:51:24PM +, Alan Cox wrote: > On Fri, 2003-02-14 at 14:52, Martin Spott wrote: > > Where did you take the DRM sources from ? I usually take the source for the > > DRM module from the same DRI CVS tree I use to build the whole DRI thing, > > Mike

Re: [Dri-devel] Lock problem with Radeon DRI

2003-02-14 Thread Martin Spott
On Fri, Feb 14, 2003 at 04:51:24PM +, Alan Cox wrote: > On Fri, 2003-02-14 at 14:52, Martin Spott wrote: > > > My lockup with flightgear on the 9000 with 4.2.99 based tree and a recent > > > DRM module. > > > > Where did you take the DRM sources from ?

Re: [Dri-devel] Lock problem with Radeon DRI

2003-02-14 Thread Martin Spott
[... Alan Cox wrote ...] > On Fri, 2003-02-14 at 13:37, Michel Dänzer wrote: >> That DRM is pretty old, is the 3D driver from the same date? Someone >> said on an XFree86 list that the flightgear lockups went away for him >> with XFree86 4.3.0rc1. > My lockup with flightgear on the 9000 with 4.2.

Re: [Dri-devel] MindRover+Radeon+DRI=crash

2003-02-14 Thread Martin Spott
> 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. [...] I'm glad to see that FlightGear is not the only reliable test case for the

[Dri-devel] Re: Flightgear and lighting (WAS: SWTCL vertex data corruption)

2003-02-13 Thread Martin Spott
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

Re: [Dri-devel] [patch] SWTCL vertex data corruption

2003-02-13 Thread Martin Spott
> 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

Re: [Dri-devel] mach64-0-0-6-branch

2003-02-12 Thread Martin Spott
> [...] Since the GATOS head is now based > on current XFree86 cvs, I may not have a new patch until 4.3.0 is released > and changes get propagated back to the DRI and GATOS trees. Could anyone tell me if I'll find recent GATOS stuff merged into the current XFree86-4.3 pre-releases ? I did not fin

  1   2   >