Re: [gentoo-user] Re: ebuild for recent ATI driver, whom to go to?

2008-12-14 Thread Miguel Ramos
2008/12/14 James wirel...@tampabay.rr.com: should have said profiler Breaking down algorithms and make a fundamentally better algo for a gpu, will require a really good profiler to imho. So far I'd be happy at being able to run something and leave the evaluation of gains at a theoretical

[gentoo-user] Re: ebuild for recent ATI driver, whom to go to?

2008-12-13 Thread James
Miguel Ramos 2008 at miguel.ramos.name writes: http://techreport.com/discussions.x/15886 I sure hope we get at least a function level profile that works with gcc with Catalyst 8.12. should have said profiler Breaking down algorithms and make a fundamentally better algo for a gpu, will

[gentoo-user] Re: ebuild for recent ATI driver, whom to go to?

2008-12-11 Thread James
Miguel Ramos 2008 at miguel.ramos.name writes: I'm new to these lists. I have just come up with an ebuild for the most recent ATI driver for FirePro/FireGL chips. Previous ebuilds didn't work due to problems compiling fgl_glxgears; so this one is better because it solves these issues and

Re: [gentoo-user] Re: ebuild for recent ATI driver, whom to go to?

2008-12-11 Thread Miguel Ramos
2008/12/11 James [EMAIL PROTECTED]: ATI Stream Computing Support It seems that with ATI Catalyst 8.12, we commoners can finally access and program so that the GPU is another available processor for us to access and use. Anyone with information, particularly relate to 'howto' use an ATI

[gentoo-user] Re: ebuild for recent ATI driver, whom to go to?

2008-12-11 Thread James
Miguel Ramos 2008 at miguel.ramos.name writes: Thanks for the info. It really looks like the 8.12 is more recent than the 8.54.3 after all... I'm going to try to install this one and I'll get back to you. As to GPU programming, I'm certainly there too! However, there is another obstacle on

Re: [gentoo-user] Re: ebuild for recent ATI driver, whom to go to?

2008-12-11 Thread Miguel Ramos
2008/12/11 James wirel...@tampabay.rr.com: Did you see this? http://techreport.com/discussions.x/15886 I sure hope we get at least a function level profile that works with gcc with Catalyst 8.12. I await your respone. I took a look at your link but I can't see what I was expected to see.

[gentoo-user] Re: ebuild for recent ATI driver, whom to go to?

2008-12-11 Thread Nikos Chantziaras
Miguel Ramos wrote: 2008/12/11 Volker Armin Hemmann volker.armin.hemm...@tu-clausthal.de: But the result isn't very good. I have the following behaviour consistently: boot system, X starts fine, I close X on purpose, second time X doesn't start, receives signal 11, third time on starting X my

Re: [gentoo-user] Re: ebuild for recent ATI driver, whom to go to?

2008-12-11 Thread Miguel Ramos
2008/12/11 Nikos Chantziaras rea...@arcor.de: Same here, plus that switching to VTs and back to X a couple of times hangs the machine. That's has always the case with fglrx, with any version ever produced, on any distro you can imagine. Oh, I can't believe! I'm almost sure at some point this

[gentoo-user] Re: ebuild for recent ATI driver, whom to go to?

2008-12-11 Thread Nikos Chantziaras
Neil Bothwick wrote: On Thu, 11 Dec 2008 22:16:59 +, Miguel Ramos wrote: I did put the lengthly list of files in package.keywords with ~amd64, but I'm not sure this is the beast approach in the long run. Make /etc/portage/package.keywords a directory, then run autounmask

Re: [gentoo-user] Re: ebuild for recent ATI driver, whom to go to?

2008-12-11 Thread Alan McKinnon
On Friday 12 December 2008 01:24:27 Nikos Chantziaras wrote: Neil Bothwick wrote: On Thu, 11 Dec 2008 22:16:59 +, Miguel Ramos wrote: I did put the lengthly list of files in package.keywords with ~amd64, but I'm not sure this is the beast approach in the long run. Make

[gentoo-user] Re: ebuild for recent ATI driver, whom to go to?

2008-12-11 Thread Nikos Chantziaras
Alan McKinnon wrote: On Friday 12 December 2008 01:24:27 Nikos Chantziaras wrote: [...] Then did the above command. All it did was creating a file autounmask-xorg-server with this inside: # --- # BEGIN: x11-base/xorg-server-1.5.3 # --- =x11-base/xorg-server-1.5.3 ~amd64 # --- #