wine-devel November 2007

wine-devel@winehq.org

117 participants
275 discussions

Re: WineD3D: Implement detection of ATI cards with Mesa DRI drivers
by James Hawkins 21 Nov '07

21 Nov '07

On Nov 21, 2007 5:15 PM, Roman Mamedov <roman(a)rm.pp.ru> wrote: > Hello. > > Presently, if an ATI card uses open-source DRI drivers from the Mesa > project ( http://dri.freedesktop.org/wiki/ATI ), Wine will report it to > Windows applications as being some generic nVIDIA model, based on D3D > capabilities of the card. > > This patch adds detection of the used ATI video card, based on Mesa DRI > module name, which is returned by drivers in GL Renderer string. In my > opinion, returning even an approximate ATI card model should be better, > than the present condition, disguising the ATI card as some equally > generic model from nVIDIA. Also, the patch adds detection of VENDOR_MESA > from GL Renderer string, as Mesa DRI drivers may have various things as > GL Vendor, but the GL Renderer name always contains the string "Mesa". > This patch resolves the bug #7267, "Lineage 2 complains about outdated > NVIDIA drivers using ATI card with Mesa drivers" - > http://bugs.winehq.org/show_bug.cgi?id=7267 . > If you send in a fixed patch, you need to add some variation of 'try X' in the subject, where X is the number of tries you're on. On top of this, you need to say in the body what you've changed between submissions. -- James Hawkins

2 1

Re: WineD3D: Implement detection of ATI cards with Mesa DRI drivers
by James Hawkins 21 Nov '07

21 Nov '07

On Nov 21, 2007 4:51 PM, Roman Mamedov <roman(a)rm.pp.ru> wrote: > Sorry, a small mistake. Always check everything twice, and when you > checked twice - check the third time :( > > --- > dlls/wined3d/directx.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/dlls/wined3d/directx.c b/dlls/wined3d/directx.c > index fa844b0..7e09014 100644 > --- a/dlls/wined3d/directx.c > +++ b/dlls/wined3d/directx.c > @@ -1145,7 +1145,7 @@ BOOL IWineD3DImpl_FillGLCaps(WineD3D_GL_Info > *gl_info) { > } else if (strstr(gl_info->gl_renderer, "R300")) { /* > r300_dri - all R3xx and R4xx-based cards */ > gl_info->gl_card = CARD_ATI_RADEON_9500; > vidmem = 128; > - } else if (strstr(gl_info->gl_renderer, "Radeon")) { /* > radeon_dri, for all R3xx-based cards */ > + } else if (strstr(gl_info->gl_renderer, "Radeon")) { /* > radeon_dri - all R100-based cards */ > /* This one should be the last case, so if the word > "Radeon" ever added to Mesa gl_renderer > * string of R200 or R300, this detection code will > keep working properly. > */ > -- > 1.5.3.4 > If you make a mistake, you have to fix the first patch and resend it. -- James Hawkins

1 0

No release this week
by Alexandre Julliard 21 Nov '07

21 Nov '07

Folks, Because of the Thanksgiving weekend, there won't be a release this Friday. 0.9.50 will most likely be on next Friday. -- Alexandre Julliard julliard(a)winehq.org

1 0

Removing Windows and Solaris from the Downloads page
by Scott Ritchie 21 Nov '07

21 Nov '07

It appears that the links for the Windows and Solaris versions on the winehq downloads page are very, very old. Since they're no longer maintained, we should just remove them, yes? Thanks, Scott Ritchie

7 9

Re: d3dx8 [patch 5/7] Implement D3DXQuaternionLn
by Andrew Talbot 21 Nov '07

21 Nov '07

David.Adam(a)math.cnrs.fr wrote: > Hi David, There was no code in this patch. -- Andy.

1 0

something wrong with patches?
by Kirill K. Smirnov 21 Nov '07

21 Nov '07

Hi, Is there anything wrong with the following patches? "winhelp: add basic support for ancient win3.0 help files" http://www.winehq.org/pipermail/wine-patches/2007-November/046886.html and comctl32: Implemented algorithm is a mergesort, not a quicksort http://www.winehq.org/pipermail/wine-patches/2007-November/046943.html Did I miss something important? Regards Kirill

1 0

Re: [6/9] d3d9: add a test for vertex shader input matching
by Alexandre Julliard 21 Nov '07

21 Nov '07

Stefan Dösinger <stefan(a)codeweavers.com> writes: > From 44f176ad4fcbc92ea66d8526670a1ec573ffa9f0 Mon Sep 17 00:00:00 2001 > From: Stefan Doesinger <stefan(a)codeweavers.com> > Date: Mon, 19 Nov 2007 10:53:26 +0100 > Subject: [PATCH] d3d9: add a test for vertex shader input matching This fails with the usual rounding errors: ../../../tools/runtest -q -P wine -M d3d9.dll -T ../../.. -p d3d9_test.exe.so visual.c && touch visual.ok visual.c:4716: Test failed: Input test: Quad 1(2crd) returned color 0x00ffff7f, expected 0x00FFFF80 visual.c:4721: Test failed: Input test: Quad 3(2crd-wrongidx) returned color 0x00ff007f, expected 0x00FF0080 visual.c:4704: Test failed: Input test: Quad 1(2crd) returned color 0x00ffff7f, expected 0x00FFFF80 visual.c:4710: Test failed: Input test: Quad 3(2crd-wrongidx) returned color 0x00ff007f, expected 0x00FF0080 visual.c:4704: Test failed: Input test: Quad 1(2crd) returned color 0x00ffff7f, expected 0x00FFFF80 visual.c:4710: Test failed: Input test: Quad 3(2crd-wrongidx) returned color 0x00ff007f, expected 0x00FF0080 visual.c:4849: Test failed: Input test: Quad 2(color-ubyte) returned color 0x00407ffe, expected 0x014080ff visual.c:4849: Test failed: Input test: Quad 2(color-ubyte) returned color 0x00407ffe, expected 0x014080ff visual.c:4849: Test failed: Input test: Quad 2(color-ubyte) returned color 0x00407ffe, expected 0x014080ff make[2]: *** [visual.ok] Error 9 -- Alexandre Julliard julliard(a)winehq.org

1 0

[0/3] RSA AES provider to rsaenh
by Vijay Kiran Kamuju 20 Nov '07

20 Nov '07

On Nov 20, 2007 4:23 PM, Juan Lang <juan.lang(a)gmail.com> wrote: > > The test fail due to missing implementation, Hence I put them in todo's. > > After the implementation is there, they do not fail. > > I think thats the procedure followed. > > I have put the remove todo's in separate patch, as its large. > > James is correct, patches 2 and 3 should be concatenated. 2 is > already necessarily large, and adding 3 to it doesn't add much to its > size. > --Juan > Damn, I have to reset the git tree. Then apply patches manually and resend them :( Should I wait.................? :( --- VJ

2 1

Re: [0/3] RSA AES provider to rsaenh
by Juan Lang 20 Nov '07

20 Nov '07

> Damn, I have to reset the git tree. > Then apply patches manually and resend them :( This isn't hard. Assuming you have these as the last three patches in your tree: git reset HEAD~2 git commit -a This will rewind your tree two steps without changing your local files, then commit them again. The more manual method, assuming you have the last patches named 2 and 3: git reset --hard HEAD~2 patch -p1 < 2 patch -p1 < 3 git commit -a This latter method isn't necessary in this case, but it sometimes comes in handy when you have some patches intermingled, and you want to commit several of them in a bunch without committing some in between. E.g. if you wanted to merge patches 1 and 3 into a single patch, you could do it this way instead. HTH, --Juan

1 0

Re: [0/3] RSA AES provider to rsaenh
by James Hawkins 20 Nov '07

20 Nov '07

On 11/20/07, Vijay Kiran Kamuju <infyquest(a)gmail.com> wrote: > Hi, > > This is a description of patch series which I am now going to send. > It adds the new Enhanced RSA AES provider to the rsaenh. > The one application which I know uses it is Office 2007. > The first patch contains the tests for the RSA AES provider. > the second patch contains the RSA AES provider implementation > the last patch removes the todo's in the tests. > > The implementation and tests have been verified by Juan Lang. > You can't fix the tests and remove the todo_wines in separate patches. The tests will fail inbetween commits. -- James Hawkins

3 2

← Newer
1
...
8
9
10
11
12
13
14
...
28
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel November 2007