Marcus Meissner wrote:
On Tue, Aug 12, 2008 at 11:44:20PM -0600, Vitaliy Margolen wrote:
While debugging some force-feedback issues ran into an interesting problem.
The size of one struct from include/linux differs between 32-bit and 64-bit.
That wouldn't be a major problem except that size
2008/8/13 Vitaliy Margolen [EMAIL PROTECTED]:
While debugging some force-feedback issues ran into an interesting problem.
The size of one struct from include/linux differs between 32-bit and 64-bit.
That wouldn't be a major problem except that size is the part of the ioctl()
request. Which
Am Mittwoch, den 13.08.2008, 09:07 +0200 schrieb H. Verbeet:
Maybe I misunderstand the issue, but doesn't Wine currently always get
compiled for 32-bit? (Iow, we always get the 32-bit version of the
structure)
Yes, but if wine runs on a 64 bit kernel, the kernel does not handle the
request, as
2008/8/13 Michael Karcher [EMAIL PROTECTED]:
Yes, but if wine runs on a 64 bit kernel, the kernel does not handle the
request, as it only recognizes the 64 bit request, if I understood
Vitaliy correct. I consider that a kernel bug.
I'd say so, yeah.
Vitaliy Margolen [EMAIL PROTECTED] wrote:
While debugging some force-feedback issues ran into an interesting problem.
The size of one struct from include/linux differs between 32-bit and 64-bit.
That wouldn't be a major problem except that size is the part of the ioctl()
request. Which
On Tue, Aug 12, 2008 at 11:44:20PM -0600, Vitaliy Margolen wrote:
While debugging some force-feedback issues ran into an interesting problem.
The size of one struct from include/linux differs between 32-bit and 64-bit.
That wouldn't be a major problem except that size is the part of the
While debugging some force-feedback issues ran into an interesting problem.
The size of one struct from include/linux differs between 32-bit and 64-bit.
That wouldn't be a major problem except that size is the part of the ioctl()
request. Which results in EINVAL.
In more details:
input.h:
