November 2007 - Wine-Devel - list.winehq.org

Re: [10/14] WineD3D: Implement the varying map

by Stefan Dösinger

Am Dienstag, 6. November 2007 23:41:40 schrieb Allan Tong: > On 11/6/07, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > > + /* Don't do any register mapping magic if it is not needed, or > > if we can't + * achive anything anyway > > + */ > > + if(highest_reg_used < (GL_LIMITS(glsl_varyings) / 4) || > > + num_regs_used >= (GL_LIMITS(glsl_varyings) / 4) ) { > > + if(num_regs_used >= (GL_LIMITS(glsl_varyings) / 4)) { > > Should it not be "num_regs_used > (GL_LIMITS(glsl_varyings) / 4)"? yes, I think you are right. Thanks for spotting this

Nov. 7, 2007

Re: [5/14] D3D9: Use HAL devices in some tests

by Stefan Dösinger

Am Mittwoch, 7. November 2007 07:13:24 schrieb Vitaliy Margolen: > Stefan Dösinger wrote: > > ------------------------------------------------------------------------ > > > > > > > > @@ -343,7 +343,7 @@ static void test_refcount(void) > > d3dpp.EnableAutoDepthStencil = TRUE; > > d3dpp.AutoDepthStencilFormat = D3DFMT_D16; > > > > - hr = IDirect3D9_CreateDevice( pD3d, D3DADAPTER_DEFAULT, > > D3DDEVTYPE_NULLREF, hwnd, + hr = IDirect3D9_CreateDevice( pD3d, > > D3DADAPTER_DEFAULT, D3DDEVTYPE_HAL, hwnd, > > D3DCREATE_SOFTWARE_VERTEXPROCESSING, &d3dpp, &pDevice ); > > ok(SUCCEEDED(hr), "Failed to create IDirect3D9Device (%s)\n", > > DXGetErrorString9(hr)); if (FAILED(hr)) goto cleanup; > > By doing this change you render all VMs useless to run d3d tests. This is > much bigger loss then broken tests on vista. IMHO VMs are useless for d3d tests anyway, see the past discussions. Vista shows that HAL and NULLREF devices do not behave in the same way even at d3d9 API level, so apparently the NULLREF device should be taken with a grain of salt anyway. The games use HAL devices, not NULLREF ones.

Nov. 7, 2007

What the hell is up with searching google for wine-devel and wine-patches posts?

by Steven Edwards

Hi, I guess this issue is more directed at Dan and the rest of the google guys we have lurking here but has anyone else noticed how hard it is to do a google search for discussions on wine-devel or look for patches that have been submitted? I used to just be able to search as follows wine-patches Steven Edwards and see every patch I ever submitted to wine. Ditto for most threads on wine-devel. This is really getting to be a pain for me because I need to be able to search for patches that might not have been merged in but still have merit for some of my customers. Thanks -- Steven Edwards "There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo

Nov. 7, 2007

Re: [5/14] D3D9: Use HAL devices in some tests

by Vitaliy Margolen

Stefan Dösinger wrote: > > ------------------------------------------------------------------------ > > > > @@ -343,7 +343,7 @@ static void test_refcount(void) > d3dpp.EnableAutoDepthStencil = TRUE; > d3dpp.AutoDepthStencilFormat = D3DFMT_D16; > > - hr = IDirect3D9_CreateDevice( pD3d, D3DADAPTER_DEFAULT, D3DDEVTYPE_NULLREF, hwnd, > + hr = IDirect3D9_CreateDevice( pD3d, D3DADAPTER_DEFAULT, D3DDEVTYPE_HAL, hwnd, > D3DCREATE_SOFTWARE_VERTEXPROCESSING, &d3dpp, &pDevice ); > ok(SUCCEEDED(hr), "Failed to create IDirect3D9Device (%s)\n", DXGetErrorString9(hr)); > if (FAILED(hr)) goto cleanup; By doing this change you render all VMs useless to run d3d tests. This is much bigger loss then broken tests on vista. Vitaliy

Nov. 7, 2007

Re: Develop .h for Wine by looking Microsoft Platform SDK

by King InuYasha

It is not legal at all. Using Microsoft Platform SDK header code is not under the GNU General Public License version 2.0 or its listed compatible licenses, so you have to do it manually WITHOUT looking at the PSDK. I recommend removing the PSDK from your system as a way to remove temptation. On Nov 6, 2007 1:21 PM, Pau Garcia i Quiles <pgquiles(a)elpauer.org> wrote: > Hello, > > How legal (if at all) would be to develop a header file by looking > reading the corresponding header file from the Microsoft Platform SDK > and adapting it to gcc (removing MSVC stuff, etc)? > > I'm interested in supporting annotations[*] and before I start > deducting everything from MSDN documentation, I'd like to know if > there is a fast track. > > [*] More information: > http://msdn2.microsoft.com/en-us/library/aa383701.aspx > http://msdn2.microsoft.com/en-us/library/ms235402(VS.80).aspx<http://msdn2.microsoft.com/en-us/library/ms235402%28VS.80%29.aspx> > > Thank you. > > -- > Pau Garcia i Quiles > http://www.elpauer.org > (Due to my workload, I may need 10 days to answer) > > > >

Nov. 7, 2007

Re: [10/14] WineD3D: Implement the varying map

by Allan Tong

On 11/6/07, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > + /* Don't do any register mapping magic if it is not needed, or if we can't > + * achive anything anyway > + */ > + if(highest_reg_used < (GL_LIMITS(glsl_varyings) / 4) || > + num_regs_used >= (GL_LIMITS(glsl_varyings) / 4) ) { > + if(num_regs_used >= (GL_LIMITS(glsl_varyings) / 4)) { Should it not be "num_regs_used > (GL_LIMITS(glsl_varyings) / 4)"? - Allan

Nov. 6, 2007

Re: [14/14] WineD3D: Release the pixel shader function when destroying the shader

by Stefan Dösinger

Am Dienstag, 6. November 2007 21:38:41 schrieb H. Verbeet: > On 06/11/2007, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > > It would probably be more proper to do stuff like this (destroying the > constants lists as well) in baseshader.c Right yeah. I was just lazy and added it there because the rest was there already :-) This applies to patch 13 as well. I'll send an updated patch tomorrow, please do not apply 13 and 14 yet.

Nov. 6, 2007

%fs, %gs on AROS hosted

by Staf Verhaegen

Hello wine developers, I am an AROS developer (http://www.aros.org) that is an open source implementation of the old AmigaOS. It has also the possiblity to run hosted on other OSes and is thus very similar to wine. I know that this group is for wine posts but I think I could reuse much of the knowledge gained by the wine developers for AROS. Recently there has been discussion about the use of the %fs and %gs segment for AROS purposes and thus also for the hosted version. As wine also has to handle these registers, I am interested to know how wine handles these registers. Or doesn't wine have to take these registers into account ? I did download the 0.9.48 source code of wine and I only did find some places where a proper saving and restoring of these registers was done. Is there something I am overlooking ? Currently wine seems to run on the following platforms: Linux version 2.0.36 or above FreeBSD 6.2 or later Solaris x86 2.5 or later NetBSD-current Mac OS X 10.4 or later I found almost no OS specific code for each of the architectures in the source. Are there special precautions to be taken in one of these OSes to be able to use the segment register in user land code ? My last question is related to an AROS version hosted on Windows. Would Windows put any restrictions on the use of the segment registers for this purpose. Is there a difference between 32bit and 64bit ? thanks, Staf.

Nov. 6, 2007

Re: Bugzilla rights

by L. Rahyen

On Tuesday November 6 2007 19:45, Vitaliy Margolen wrote: > Bugzilla admin, please disallow people to add/remove e-mail addresses > to/from bugs unless they've been given that right. Or at least have rights > to modify any aspect of the bug. > > Thanks, > Vitaliy. I think that we should remove the right to add/remove e-mail addresses ONLY from user who abuse his/her rights (like Toby Brommerich). All other users should have this right - at least the right to add others to CC list.

Nov. 6, 2007

Re: [14/14] WineD3D: Release the pixel shader function when destroying the shader

by H. Verbeet

On 06/11/2007, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > It would probably be more proper to do stuff like this (destroying the constants lists as well) in baseshader.c

Nov. 6, 2007