On Sun, Jul 11, 2010 at 4:21 PM, Roderick Colenbrander <
thunderbir...@gmail.com> wrote:
>
> The PCI id is something else. For instance run 'lspci -x':
> 01:00.1 Audio device: ATI Technologies Inc RV620 Audio device [Radeon
> HD 34xx Series]
> 00: 02 10 28 aa 07 01 10 40 00 00 03 04 10 00 80 00
>
On 07/10/2010 09:27 PM, Roderick Colenbrander wrote:
> The issue is more complicated than that. We also need the PCI id and
> that's one of the reasons why the code is at is right now.
> GLX_NVX_memory_info / GL_ATI_memory_info only provide the amount of
> video memory. In order to retrieve the pci
On Sat, Jul 10, 2010 at 6:30 PM, Seth Shelnutt wrote:
>
>
> On Sat, Jul 10, 2010 at 3:57 PM, Henri Verbeet wrote:
>>
>> What kind of issue? (Just curious.)
>>
> Well a 8300 isn't cuda capable, and even with the forcegpu nvidia_g80 flag,
> wine still makes the client think it's an 8300 not an 850
On 11 July 2010 11:30, Seth Shelnutt wrote:
> The gl_ati_meminfo extension has been around longer than
> the Nvidia extension so it should have an even greater presence (since
> catalyst 9.2). Anyone who has a 3xxx or newer from ATI or a 4xx from Nvidia
> is guaranteed to have the extension for de
On 11 July 2010 11:30, Seth Shelnutt wrote:
> Looking through the whole directx.c file I see what you mean. I'm not really
> sure there is any better way to do it then what it already done. It seems
> like it should be made more dynamic so everyone doesn't have to go hardcode
> in all the differen
On Sat, Jul 10, 2010 at 3:57 PM, Henri Verbeet wrote:
>
> What kind of issue? (Just curious.)
>
> Well a 8300 isn't cuda capable, and even with the forcegpu nvidia_g80
flag, wine still makes the client think it's an 8300 not an 8500. So then
fah errors out with:
Initializing Nvidia gpu library
On 10 July 2010 16:22, Seth Shelnutt wrote:
> I'm not sure if this is appropriate for a code freeze or not but I think it
> is. We just ran into an issue with the folding gpu client in wine with
> someone. Turns out it's because wine reports the card as a 8300 not an 8500.
What kind of issue? (Jus
I'm not sure if this is appropriate for a code freeze or not but I think it
is. We just ran into an issue with the folding gpu client in wine with
someone. Turns out it's because wine reports the card as a 8300 not an 8500.
Looking at directx.c I see that that is probably because an 8500 is not
lis