[Dri-devel] M10 support
Who is working on support for the M10? Anyone? I'm about to get one and I'm a little worried about using the ati drivers since they can crash the system on suspend/resume. This is a laptop system so I'm going to want suspend/resume and I don't want to be restarting X every time I resume. I could help with adding the support. I'm a decent programmer (although this is something I've never tried). But I thought I'd ask if anyone else was working on this yet. I would rather get the technical info from someone on the project then have to ask ati for it. I imagine the M10 support would be a specialization of the rv350 support. But I could be wrongI'm new to this and have always bought nvidia cards in the past. Jason --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] when I had the choice ....
On Thu, Oct 02, 2003 at 10:12:21AM +0200, Thomas Emmel wrote: Hello, we are currently looking for the best graphics cards for linux and OpenGL. Can someone give me a hint which of the currently available cards are the best to use for extensive 3D applications in technical field (CAD, visualization of finite element data etc., no games). Well, I'm currently using a Radeon 9000 card. It's my impression that the radeon cards are far more stable than the NVIDIA cards. I've had a GeForce card before, and the drivers really suck.It was just heaven, when i bought radeon. I must say that the DRI team have done a very good job on the radeon drivers. Thank you very much... --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] merging to branches
On Fri, 3 Oct 2003 17:57:47 -0500 (CDT) [EMAIL PROTECTED] wrote: It would be good to have someone with hardware who could test the 4.2.0 libGL/savage_dri.so against the CVS DDX before and after a trunk merge to see if it breaks things. Unfortunately, from what I've been told now the savage card I have (an MX) won't work. I'll see if I can set up something like that. I would have to try and run an Xserver and savage DDX driver from the savage-1_0_0-branch with an old libGL and savage_dri.so. I would need to get Xfree86 4.2 sources and the original S3 code in order to compile a working 3D driver, right. That won't happen before some time next week. I have 4.2 sources and will try Rafael's patch with the savage branch, please explain me what test do you want done and I'll try to do it. I couldn't get the 4.2.0 dri drivers to work because my apps are linked against a newer libGL Thanks for the offer. Sounds like all you can do for now is test if the 2D driver works on your hardware. But what we really need to test is the 3D driver from S3 together with the 2D driver from S3 and the 2D driver merged from XFree86 CVS. In other words, we want to be sure that changes to the 2D driver don't break 3D. You could try to get 3D working with XFree 4.2 though. Generally it should be no problem to install a different libGL. What kind of errors do you get? Maybe libGL is installed in a different path on your system. What does ldd `which glxinfo` tell you? You can make sure that the XFree 4.2 libGL is used by pointing the environment variable LD_LIBRARY_PATH to the right directory. Regards, Felix __\|/_____ ___ - Felix ___\_e -_/___/ __\___/ __\_ You can do anything, Kühling (_\Ä// /_/ /) just not everything [EMAIL PROTECTED] \___/ \___/ Uat the same time. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] M10 support
xfree86 and DRI CVS have 2D support for m10 already. 3D is not possible as no one has sponsored development of an opensource driver and no one has the databooks for the r300 yet. So, if you want 3D, you'll have to use the ati binary driver. Alex --- Jason Dagit [EMAIL PROTECTED] wrote: Who is working on support for the M10? Anyone? I'm about to get one and I'm a little worried about using the ati drivers since they can crash the system on suspend/resume. This is a laptop system so I'm going to want suspend/resume and I don't want to be restarting X every time I resume. I could help with adding the support. I'm a decent programmer (although this is something I've never tried). But I thought I'd ask if anyone else was working on this yet. I would rather get the technical info from someone on the project then have to ask ati for it. I imagine the M10 support would be a specialization of the rv350 support. But I could be wrongI'm new to this and have always bought nvidia cards in the past. Jason --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] shared memory segment size limit is too low
Hi, Why is shmmax setting so low by default (at least in kernel version 2.4.21)? Images are often very large and shared memory is needed when sharing images between applications and window system. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] DRI savage driver status
At 01:07 PM 1/10/2003, Ian Romanick wrote: Just out of curiosity, will the Via driver support the Savage 2000? IIRC, the rasterization core was based on the Savage4 line, but the TCL unit was new (obviously). I *know* it wouldn't support the TCL unit, but the benchmarks that I remember showed that the TCL unit slowed things down. :) I'm just curious about the rasterization part. The original Via driver support Savage 2000 (that's what i think) but i don't have the hardware to test but I expect that savage 2000 will be supported on the driver that i'm working on but i'll need help because i don't have a savage 2000 here :) bye. Rafael Máximo --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] merging to branches
On Fri, 2003-10-03 at 13:55, Felix Kühling wrote: On Fri, 03 Oct 2003 12:14:32 -0700 Eric Anholt [EMAIL PROTECTED] wrote: Okay, I was going to merge trunk to the savage-1_0_0-branch, since updates to the savage driver in trunk help out with that work I've been Are you referring to the patch that Rafael Máximo sent yesterday? I was going to look at it, but I didn't have time yet. After a quick glance it looks like it reverts lots of changes S3 made to the driver. told. I went to the CvsPolicy wiki page and based on that did a tag on the savage branch of savage-1_0_0-trunk-premerge. Then I did cvs update -d -j HEAD. It ran for a while, and produced a large number of conflicts. Why should there be conflicts in files that weren't touched by the savage-branch? Is there a way to avoid having to deal with all of those? This is probably related to keyword substitutions. There is a node Merging and keywords in the CVS info documentation. Basically you should add -kk to the cvs update command line. This way keywords are not substituded and can't cause phantom conflicts. The -kk didn't seem to help at all (cvs up -kk -d -j HEAD). I still got C in 537 files. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] merging to branches
On Sat, 04 Oct 2003 16:02:53 -0700 Eric Anholt [EMAIL PROTECTED] wrote: On Fri, 2003-10-03 at 13:55, Felix Kühling wrote: On Fri, 03 Oct 2003 12:14:32 -0700 Eric Anholt [EMAIL PROTECTED] wrote: Okay, I was going to merge trunk to the savage-1_0_0-branch, since updates to the savage driver in trunk help out with that work I've been Are you referring to the patch that Rafael Máximo sent yesterday? I was going to look at it, but I didn't have time yet. After a quick glance it looks like it reverts lots of changes S3 made to the driver. told. I went to the CvsPolicy wiki page and based on that did a tag on the savage branch of savage-1_0_0-trunk-premerge. Then I did cvs update -d -j HEAD. It ran for a while, and produced a large number of conflicts. Why should there be conflicts in files that weren't touched by the savage-branch? Is there a way to avoid having to deal with all of those? This is probably related to keyword substitutions. There is a node Merging and keywords in the CVS info documentation. Basically you should add -kk to the cvs update command line. This way keywords are not substituded and can't cause phantom conflicts. The -kk didn't seem to help at all (cvs up -kk -d -j HEAD). I still got C in 537 files. Same problems here. I'm trying to merge the trunk to the config branch. It is strange that cvs even attempts to merge files that I never committed any new revisions for on the branch. I also checked that I don't have any accidental local changes before I started. On some (many) of the files that I didn't change rcsmerge reports conflicts. I don't know what's going on. Is it a problem with my client or with the server? I can't imagine that this is normal CVS operation :-/ The fact that we're both having the same problems would point to the server. I'm working on a TCL script that resolves conflicts automatically. It just copies the new versions and discards the old ones. To be used on directories that you are sure were not changed on the branch. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] Felix __\|/_____ ___ - Felix ___\_e -_/___/ __\___/ __\_ You can do anything, Kühling (_\Ä// /_/ /) just not everything [EMAIL PROTECTED] \___/ \___/ Uat the same time. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] M10 support
Alex Deucher wrote (on Sat, 4 Oct 2003 at 08:49 -0700): xfree86 and DRI CVS have 2D support for m10 already. 3D is not possible as no one has sponsored development of an opensource driver and no one has the databooks for the r300 yet. So, if you want 3D, you'll have to use the ati binary driver. Are you sure about xfree86, I checked their website last night and they list support via the ati driver, which I took to mean the driver provided by ati. I checked the status page for dri and nothing is mentioned about the M10. Shouldn't that page be updated if you have 2d support now? Has anyone tried to get the databooks for the M10 or 9600 yet? How hard is this? Do you guys have an established reputation with ati? I noticed in the FAQ that it said you don't give out the info once they give it to you. Why is that? And why do they only give out the info to companies. Seems a bit silly. Could I just claim to have my own company and get the data? Why yes, I'm the CEO of Just for DRI, a new company that is making drivers for DRI. Ya know, or something equally silly. When you say sponsored development do you mean monetary sponsorship, or do you mean something else? Thanks for the reply, sorry I have so many questions that are probably really silly. Thanks, Jason Alex --- Jason Dagit [EMAIL PROTECTED] wrote: Who is working on support for the M10? Anyone? I'm about to get one and I'm a little worried about using the ati drivers since they can crash the system on suspend/resume. This is a laptop system so I'm going to want suspend/resume and I don't want to be restarting X every time I resume. I could help with adding the support. I'm a decent programmer (although this is something I've never tried). But I thought I'd ask if anyone else was working on this yet. I would rather get the technical info from someone on the project then have to ask ati for it. I imagine the M10 support would be a specialization of the rv350 support. But I could be wrongI'm new to this and have always bought nvidia cards in the past. Jason --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] M10 support
--- Jason Dagit [EMAIL PROTECTED] wrote: Alex Deucher wrote (on Sat, 4 Oct 2003 at 08:49 -0700): xfree86 and DRI CVS have 2D support for m10 already. 3D is not possible as no one has sponsored development of an opensource driver and no one has the databooks for the r300 yet. So, if you want 3D, you'll have to use the ati binary driver. Are you sure about xfree86, I checked their website last night and they list support via the ati driver, which I took to mean the driver provided by ati. I checked the status page for dri and nothing is mentioned about the M10. Shouldn't that page be updated if you have 2d support now? the DRI and xfree86 recently synced up so, they are, right now, for most intents and purposes the same code base. Right now there is 2D support only for r3xx series cards. I haven't checked the web pages in a while. the ati driver is the name of the xfree86 driver for ati cards. it's not provided by ati although they do contribute code to it. Has anyone tried to get the databooks for the M10 or 9600 yet? How hard is this? Do you guys have an established reputation with ati? I heard the gatos people got the databooks for the r3xx cards but I'm not sure if that includes 3D registers as well or just 2d and overlay stuff. many xfree86 and DRI developers have a good relationship with ati. ati contributes quite a bit of code. I'm not sure if anyone has tried to get databooks for the 3D stuff yet; I don't even know if ati will release them. I noticed in the FAQ that it said you don't give out the info once they give it to you. Why is that? And why do they only give out the info to companies. Seems a bit silly. Could I just claim to have my own company and get the data? Why yes, I'm the CEO of Just for DRI, a new company that is making drivers for DRI. Ya know, or something equally silly. If you want the databooks, you'll need to register on their website. if you are not a company, then put in something like opensource developer or hobbyist. When you say sponsored development do you mean monetary sponsorship, or do you mean something else? Yes monetary sponsorship. writing a 3D driver for a new chip like the r3xx chips is no small undertaking. it's a lot of work. the weather channel funded the development of the r2xx drivers. Thanks for the reply, sorry I have so many questions that are probably really silly. Thanks, Jason __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] NWN lighting?
Is someone looking at the NWN issues with R200 (and probably R100 too)? There is still random flickering, and the lighting isn't correct neither (both issues only with TCL). Keith changes (end of july) changed the lighting, but now it basically looks like some light is completely missing. This is how it looked before the changes, http://homepage.hispeed.ch/rscheidegger/nwn_with_tcl.jpg; how it looks after the changes, http://homepage.hispeed.ch/rscheidegger/nwn_newlight.jpg; and how it should look in the future ;-) (with R200_NO_TCL) http://homepage.hispeed.ch/rscheidegger/nwn_without_tcl.jpg. Another screenshot highlighting the flickering, http://homepage.hispeed.ch/rscheidegger/nwn_without_tcl.jpg I've tried to look into this but without much success (well I got rid of the flickering by accident when I tried to change the lighting - but it was really just a side-effect by hitting R200_DB_STATE more often so definitely not a proper fix) Roland --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
