gdi32: Don't let the gdi32 driver allocate memory in the dplayx region.

[Alexei Svitkine]

Sorry, I wasn't subscribed to wine-patches and the first two mails only
went through to wine-devel, but didn't get through to wine-patches.


On Fri, Jul 26, 2013 at 2:04 AM, Nikolay Sivov <bunglehead at gmail.com> wrote:

>  On 7/26/2013 08:48, Alexei Svitkine wrote:
>
>
>
>
> On Mon, Jul 22, 2013 at 10:45 PM, Alexei Svitkine <
> alexei.svitkine at gmail.com> wrote:
>
>> Don't let the gdi32 driver allocate memory in the dplayx region.
>>
>> Fixes bug: http://bugs.winehq.org/show_bug.cgi?id=34095
>>
>> The issue is that the dplayx code in wine needs to allocate some
>> memory at a static address (0x50000000) and loading the Mac native gdi
>> driver ends up using that part of the address space.
>>
>> This patch fixes that by reserving that part of memory while the
>> display driver is initialized and releasing it after.
>>
>> ---
>>  dlls/gdi32/driver.c | 10 ++++++++++
>>  1 file changed, 10 insertions(+)
>>
>   Please stops resending this. Looks like dplay should be fixed to not
> depend on that reserved address area.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20130726/83084931/attachment.html>