> The definition of the field was always 64bit and when userspace fails to
> properly set the
> upper 32bits than userspace needs to get fixed, not the kernel.
Userspace fails to properly set the upper 32bits and a 32 bit kernel
don't check the upper 32 bits :-)
> Can you try to figure out where
Hi Christian!
Yes, it is. Android-x86 4.0-r1 dos'nt fill right a value fild of the
structture drm_radeon_info_t: high bits are a random value. But I
wrote a compat function for this ioctl which clears this bits only for
32-bit applications. This patch is against a 3.10 kernel.
2014-09-15 15:54 GMT
Hi Sergey,
that probably works, but a compat function is the wrong approach here.
The definition of the field was always 64bit and when userspace fails to
properly set the upper 32bits than userspace needs to get fixed, not the
kernel.
Can you try to figure out where the random bits in the upp
Android-x86 4.0-r1 (32 bit) have problems with x86_64 kernel when he
trying to use a radeon kms. The following change correct a problem:
drivers/gpu/drm/radeon_kms.c (function radeon_info_ioctl):
- value_ptr = (uint32_t *)((unsigned long)info->value);
+ value_ptr = (uint32_t *)((unsigned)info->va
Am 15.09.2014 um 12:09 schrieb Sergey Korshunoff:
> Android-x86 4.0-r1 (32 bit) have problems with x86_64 kernel when he
> trying to use a radeon kms. The following change correct a problem:
>
> drivers/gpu/drm/radeon_kms.c (function radeon_info_ioctl):
>
> - value_ptr = (uint32_t *)((unsigned long
