On Fri, Oct 12, 2018 at 10:52:51AM +0530, tbhar...@codeaurora.org wrote:
> (in 64 bit userspace long is 32-bit)
Not on Linux.
$ cat /tmp/c.c
int main(void)
{
return sizeof(long);
}
$ gcc /tmp/c.c
$ ./a.out; echo $?
8
$ file ./a.out
./a.out: ELF 64-bit LSB pie executable, 64-bit PowerPC or
-ker...@vger.kernel.org; linux-media@vger.kernel.org
Subject: Re: question about V4L2_MEMORY_USERPTR on 64bit applications
sorry for wrong question, I really meet memory address truncated issue, when
use V4L2 kernel APIs.
in a kernel thread created by kernel_thread() I vm_mmap a shmem_file to
sorry for wrong question, I really meet memory address truncated issue,
when use V4L2 kernel APIs.
in a kernel thread created by kernel_thread()
I vm_mmap a shmem_file to addr: 77fa8000
and queue it to V4L2, after dequeue it, and I find the address is
truncated to f7fa8000
I use _
Hi, Ning,
unsigned long userptr; <<<--- this is a 32bit addr.
I think it's wrong here,for LP64 data modelmachine(unix-like systems), the
actual size ofdata type 'unsigned long'is 8(64bits value)whichis equal
to pointer.
On 10/12/2018 11:04 AM, Zhang, Ning A wrote:
> Hi,
>
> I have question a
