From: Daryll S. <da...@pr...> - 1999-12-15 18:34:25
|
We've got 40 people signed up on the list. That's great. Does anyone want to talk about what they want to do now that they're here? I'm interested in what projects people are tackling and perhaps there will be other people interested in working together on a project. - |Daryll |
From: Flavio V. <dr...@ge...> - 1999-12-16 00:03:13
|
Hi, I'm Flavio Villanustre, happy owner of a Voodoo Banshee. Not having anything but linux installed in my home machine I'm using Daryll's drivers since I got my Banshee (near 10 months ago). I'm sorry I don't have nor the knowledge neither the time to help in the development. I'll happily help with bug reports (if that helps...). In case it's relevant this is my hardware: Pentium II 333, 128 Mb RAM, Diamond Monster Fusion Voodoo Banshee, Creative SB Live, Creative DVD, Creative DXR2, intel eepro 10/100. Of course it's a "only linux box" (no winshit, even not VMWare :-). OTOH I've reported two bugs related to texture and windows corruption... :-) Cheers, Flavio. On Wed, 15 Dec 1999, Daryll Strauss wrote: > We've got 40 people signed up on the list. That's great. Does anyone > want to talk about what they want to do now that they're here? I'm > interested in what projects people are tackling and perhaps there will > be other people interested in working together on a project. > > - |Daryll > > > _______________________________________________ > Dri-devel mailing list > Dri...@li... > http://lists.sourceforge.net/mailman/listinfo/dri-devel > |
From: Jason R. <ja...@cc...> - 1999-12-16 00:21:04
|
On Wed, 15 Dec 1999, Daryll Strauss wrote: > We've got 40 people signed up on the list. That's great. Does anyone > want to talk about what they want to do now that they're here? I'm > interested in what projects people are tackling and perhaps there will > be other people interested in working together on a project. > Daryll, For starters how about posting a todo list? It's a bit more difficult for those of us who don't know the X server and Mesa inside and out :) to know what needs to be taken care of. Also, I'll have a second PIII-500 in my box within the next few weeks, so I'll be more than happy to test & debug any code that is SMP-dependent. Jason -- Jason Rappleye Canisius College, Computer Science & Math major email: rap...@ca... rap...@ac... "The woods are lovely, dark and deep, But I have promises to keep, And lines to code before I sleep, And lines to code before I sleep" |
From: Daryll S. <da...@pr...> - 1999-12-16 00:39:44
|
On Wed, Dec 15, 1999 at 07:18:59PM -0500, Jason Rappleye wrote: > For starters how about posting a todo list? It's a bit more difficult for > those of us who don't know the X server and Mesa inside and out :) to know > what needs to be taken care of. Also, I'll have a second PIII-500 in my > box within the next few weeks, so I'll be more than happy to test & debug > any code that is SMP-dependent. That's not a bad idea. Of course, the first TODO list is simply to look at the buglist! :-) Beyond that it is mostly a matter of improving the existing drivers. For example, performer town uses GL_BLEND texture mode, and the driver doesn't implement that, so it falls back to software. I'm also convinced that Q3A slows down a lot when the blood clouds are rendered. I'm not sure why, but I suspect we're hitting a non optimized path. The 2D driver could have a lot more optimized paths. So all three of those are projects involved with improving/optimizing the current support. I need to do some work on the web pages, so I'll see about making a "Suggested Projects" page. I also suspect people on the list have noticed things they'd want to change/improve. They could post their ideas to get discussions going. - |Daryll |
From: Nathan <bl...@rt...> - 1999-12-16 01:29:45
|
I'm not much into coding anymore, but wherever I see I can help, I will. But, in the meantime, I'll be assisting with bug reports all that I can. I'm currently running an RH6.1 system customized to the hilt Dual 450SMP with a V3-3000 and 128M SDRAM kernel 2.3.14 I'm probably going to play around with slack 7 on this machine as well, so I'll post bugs either way, and I can test out any SMP dependent code as well. -N8 We Fremen have a saying, "God created Arrakis to train the faithful." One cannot go against the word of God. -Paul Atreides Dune - Frank Herbert ___________________________________________________________ My life is a pilgrimage across Arrakis with too much Melange in my system and no worm at my feet. -Me |
From: rsd <da...@cy...> - 1999-12-17 17:27:05
|
Hey All. How do you want to proceed with adding platforms into the code base? Should I take the current code and #ifdef __alpha__, or what? Should I just fork my own for the time being.. and look at the amount of change before deciding? My current mindset is just to do an update and ravage the code to my own will.. but uhh ;) Roger |
From: Daryll S. <da...@pr...> - 1999-12-17 17:36:43
|
On Fri, Dec 17, 1999 at 11:22:05AM -0600, rsd wrote: > How do you want to proceed with adding platforms into the code base? > Should I take the current code and #ifdef __alpha__, or what? Should I > just fork my own for the time being.. and look at the amount of change > before deciding? > > My current mindset is just to do an update and ravage the code to my > own will.. but uhh ;) OK, that's not the best choice. :-) I think we're going to need to end up with #ifdef __alpha__ around things. Hopefully the set of changes ends up being small. The question is how to get there. I suspect you probably want to start by making a copy of the tree. Any changes that are Alpha specific should have ifdefs around it. Then check out a fresh version of the tree, and do diffs. I'd prefer multiple smaller diffs to one giant one. It just makes it easier to look over. Then I'll check them back into the main tree, you do an update on your copy, and you're ready to roll again. If everything you do is within #ifdefs then it should be trivial. I don't believe that will happen. It'll make more sense to change some things in a generic way for all architectures so we'll need to be careful about merging those. How's that sound for a plan? - |Daryll |
From: Marc v. W. <van...@ne...> - 1999-12-24 23:40:39
|
> I think we're going to need to end up with #ifdef __alpha__ around > things. Hopefully the set of changes ends up being small. I sincerly hope that you don't mean __alpha__ implies __linuxalpha__, otherwise I imagine our BSD alpha crowd will get really unhappy at some point. Regards, Marc |
From: Davenport <da...@cy...> - 1999-12-25 08:02:39
|
Well.. I'm now working on the XFree driver. The code used in the #ifdef__alpha__ should be 100% cross-os. (So far, most changes are adding memory barrier calls. XF3.9 seems to require a more in depth lookie) The drm is os specific, so there won't be any compatibility issues arrising from there. Maybe the only place I can think it may be tricky is in the initialization code for the glide lib, and maybe in the initilization code for the X driver? (Seeing how it is totally foobar now on alpha.. it is a moot point until it's working, really) I'm more than willing to work with __Anyalpha__ BSD Alpha people! ;-) Roger Marc van Woerkom wrote: > > > I think we're going to need to end up with #ifdef __alpha__ around > > things. Hopefully the set of changes ends up being small. > > I sincerly hope that you don't mean __alpha__ implies __linuxalpha__, > otherwise I imagine our BSD alpha crowd will get really unhappy > at some point. > > Regards, > Marc -- There's nothing left but Faith. - The Cure |
From: Turchanov S. <tur...@ot...> - 1999-12-17 01:36:13
|
On Wed, Dec 15, 1999 at 10:33:48AM -0800, Daryll Strauss wrote: > We've got 40 people signed up on the list. That's great. Does anyone > want to talk about what they want to do now that they're here? I'm > interested in what projects people are tackling and perhaps there will > be other people interested in working together on a project. Hi all! I'm an unhappy person to have TNT2-based card as it lacks any decent support in Linux from nVidia. But I hope that they will release their driver for DRI and that will be the time I'll step out of darkness and start active coding. But if that won't happen (not sure how long would I wait) then I'll probably start implementing driver using their SDK or using their sources for glx driver. So for now I mostly watching & waiting. Bye. |
From: Marc v. W. <van...@ne...> - 1999-12-24 23:21:52
|
> I'm an unhappy person to have TNT2-based card as it lacks any decent support > in Linux from nVidia. > But I hope that they will release their driver for > DRI and that will be the time I'll step out of darkness and start active > coding. But if that won't happen (not sure how long would I wait) then > I'll probably start implementing driver using their SDK or using their > sources for glx driver. While being tempted to change to a manufacturer who takes us more seriously I still believe their cards are the top ones for a while. So I am mentally preparing for the second option. While we are at it - anyone bullied nvdidia's Dave Schmenck lately? He went quiet at some point and has not been seen again. :( Regards, Marc |
From: teunis <te...@co...> - 1999-12-17 06:44:35
|
On Wed, 15 Dec 1999, Daryll Strauss wrote: > We've got 40 people signed up on the list. That's great. Does anyone > want to talk about what they want to do now that they're here? I'm > interested in what projects people are tackling and perhaps there will > be other people interested in working together on a project. Am interested in bugfixing, stablizing, then writing a game :) One gets -very- tired of database hacking for clients... I'm going back into student mode after a few years of abject poverty so I might not be all that helpful at times but ya never know, eh? Anyways, I usually program under the console due to X being so unusable (for a person who dislikes using mice) and am interested in getting Mesa accelerated through the fbdev drivers if that's possible... (or through KGI - a GGI kernel driver project) G'day, eh? :) - Teunis - Finally accelerated 3D. I've been hacking my own software routines for 10 years now but hardware's so much nicer :) |