From: Eugene Syromiatnikov <esyr@redhat.com>
To: tbhardwa@codeaurora.org
Cc: "'Zhang, Ning A'" <ning.a.zhang@intel.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: question about V4L2_MEMORY_USERPTR on 64bit applications
Date: Sun, 14 Oct 2018 02:11:26 +0200 [thread overview]
Message-ID: <20181014001126.GA717@asgard.redhat.com> (raw)
In-Reply-To: <000601d461eb$a1f7afc0$e5e70f40$@codeaurora.org>
On Fri, Oct 12, 2018 at 10:52:51AM +0530, tbhardwa@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 cisco 7500, version 1 (SYSV), dynamically linked, interpreter /lib64/ld64.so.2, for GNU/Linux 3.10.0, BuildID[sha1]=dad78822e741b7900dc7568222822d5d63c31a6c, not stripped
prev parent reply other threads:[~2018-10-14 7:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 3:04 question about V4L2_MEMORY_USERPTR on 64bit applications Zhang, Ning A
2018-10-12 3:25 ` Bing Bu Cao
2018-10-12 4:33 ` Zhang, Ning A
2018-10-12 5:22 ` tbhardwa
2018-10-14 0:11 ` Eugene Syromiatnikov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181014001126.GA717@asgard.redhat.com \
--to=esyr@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=ning.a.zhang@intel.com \
--cc=tbhardwa@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox