On 21 July 2010 17:30, Roderick Colenbrander wrote:
> Sure, GL_*_memory_info extensions could help there but I think we
> should be cautious with just adding such support to there. Over the
> past few months I have seen various reports of users who run games
> which say to require lets say 128MB o
On Wed, Jul 21, 2010 at 4:02 AM, Henri Verbeet wrote:
> On 21 July 2010 05:08, Roderick Colenbrander wrote:
>> I think 'select_card_*' should just return the pci device id and the
>> default amount of video memory should be stored in lets say the driver
>> version table (a different name for the
On 21 July 2010 05:08, Roderick Colenbrander wrote:
> I think 'select_card_*' should just return the pci device id and the
> default amount of video memory should be stored in lets say the driver
> version table (a different name for the table might make sense). It
Yeah, this should be based on th
On Tuesday, July 20, 2010 2:54:24 pm Luke Bratch wrote:
> The attached uses that experimental extension [1] to report the correct
> total memory for cards that support it, while sticking with the existing
> hard coded values and code layout for those that don't.
I think the extension should be che
On Wed, Jul 21, 2010 at 3:59 AM, Roderick Colenbrander
wrote:
> On Tue, Jul 20, 2010 at 11:54 PM, Luke Bratch wrote:
>> --- On Tue, 20/7/10, Henri Verbeet wrote:
>>
>>> Negative on using experimental extensions I'm afraid.
>>> Writing a proof
>>> of concept patch is ok, of course, and I'd be wil
On Wed, Jul 21, 2010 at 1:57 AM, Seth Shelnutt wrote:
> For ati there is also GL_ATI_mem_info [1] or WGL_AMD_gpu_association [2] . I
> believe that [1] is now obsolete as from reading some of the wine-dev
> mailing list [3], and some other site it seems AMD is now pushing the using
> of WGL_AMD_gp
On Tue, Jul 20, 2010 at 11:54 PM, Luke Bratch wrote:
> --- On Tue, 20/7/10, Henri Verbeet wrote:
>
>> Negative on using experimental extensions I'm afraid.
>> Writing a proof
>> of concept patch is ok, of course, and I'd be willing to
>> review that,
>> but it can't go in until the extension is f
For ati there is also GL_ATI_mem_info [1] or WGL_AMD_gpu_association [2] . I
believe that [1] is now obsolete as from reading some of the wine-dev
mailing list [3], and some other site it seems AMD is now pushing the using
of WGL_AMD_gpu_association instead. A patch could be written in the exact
sa
--- On Tue, 20/7/10, Henri Verbeet wrote:
> Negative on using experimental extensions I'm afraid.
> Writing a proof
> of concept patch is ok, of course, and I'd be willing to
> review that,
> but it can't go in until the extension is finalized. Note
> that this
> wouldn't allow you to get rid of
On 20 July 2010 19:46, Roderick Colenbrander wrote:
> It is quite easy to add some basic support for it (I
> would not use the free video memory code yet) but I'm not sure if we
> want to support this yet since the extension is experimental. If it is
> fine by Henri, I can add it as it would help
On Tue, Jul 20, 2010 at 1:54 PM, Henri Verbeet wrote:
> On 20 July 2010 15:49, Luke Bratch wrote:
>> Adds detection for the Nvidia 8800GTX card and sets its video memory
>> correctly.
>>
>> I have sent this patch in the past but it got rejected, as this method of
>> calculating video card type/
On 20 July 2010 15:49, Luke Bratch wrote:
> Adds detection for the Nvidia 8800GTX card and sets its video memory
> correctly.
>
> I have sent this patch in the past but it got rejected, as this method of
> calculating video card type/memory wasn't supposed to stay around forever,
> but another
Hey guys, would you stop spamming wine-patches? Please never replay to
wine-patches.
Vitaliy.
Am 08.03.2010 um 22:51 schrieb Ben Klein:
>> Some cards are sold with "enabled special feature X in game Y". The game
>> then looks at the card ID to allow additional configuration options. An
>> example for this is Age of Empires 3 which allows the highest graphics
>> options only for some Gef
On Mon, Mar 8, 2010 at 10:40 PM, Stefan Dösinger wrote:
>
> Am 08.03.2010 um 14:21 schrieb Roderick Colenbrander:
>
>> Hi Luke,
>>
>> We don't want to have all possible GPU models in (there are so many
>> different models). It only gives a hint to apps (yes the proper amount
>> of video memory is
On 9 March 2010 08:40, Stefan Dösinger wrote:
>
> Am 08.03.2010 um 14:21 schrieb Roderick Colenbrander:
>
>> Hi Luke,
>>
>> We don't want to have all possible GPU models in (there are so many
>> different models). It only gives a hint to apps (yes the proper amount
>> of video memory is more serio
Am 08.03.2010 um 14:21 schrieb Roderick Colenbrander:
> Hi Luke,
>
> We don't want to have all possible GPU models in (there are so many
> different models). It only gives a hint to apps (yes the proper amount
> of video memory is more serious) but this should be fixed in a
> different way I thi
Hi Luke,
We don't want to have all possible GPU models in (there are so many
different models). It only gives a hint to apps (yes the proper amount
of video memory is more serious) but this should be fixed in a
different way I think e.g. nv-control. I think I might look into that
again soon.
Rode
18 matches
Mail list logo
