From: Maxime Ripard <maxime@cerno.tech>
To: Simon Ser <contact@emersion.fr>
Cc: Brian Starkey <rodrigosiqueiramelo@gmail.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
nd <nd@arm.com>
Subject: Re: [Intel-gfx] [PATCH v7 i-g-t 2/4] kms_writeback: Add initial writeback tests
Date: Wed, 15 Apr 2020 12:06:18 +0200 [thread overview]
Message-ID: <20200415100618.dffhwxhctgarqleq@gilmour.lan> (raw)
In-Reply-To: <0kwho152-gzRe09N-ECBh9KepTGX-b_MU8X-TtBnTdWAQP9o5ni7tOVqGn9LK2U2ormexeYvS8U1uVcBMY5Lv-Le4z0dnnMnRaSbb29xjqo=@emersion.fr>
[-- Attachment #1.1: Type: text/plain, Size: 391 bytes --]
On Wed, Apr 15, 2020 at 09:49:46AM +0000, Simon Ser wrote:
> > > + igt_output_set_prop_value(output, IGT_CONNECTOR_WRITEBACK_OUT_FENCE_PTR, (uint64_t)out_fence_ptr);
> >
> > On ARM (32bits), this cast creates a compilation error since the
> > pointer size isn't an uint64_t.
>
> Does casting to uintptr_t before uint64_t fix it?
It does yep. Casting to uintptr_t alone also works
Maxime
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-04-15 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 0:59 [igt-dev] [PATCH v7 i-g-t 2/4] kms_writeback: Add initial writeback tests Brian Starkey
2020-04-15 9:46 ` [Intel-gfx] " Maxime Ripard
2020-04-15 9:49 ` Simon Ser
2020-04-15 10:06 ` Maxime Ripard [this message]
2020-04-15 10:08 ` [igt-dev] " Petri Latvala
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=20200415100618.dffhwxhctgarqleq@gilmour.lan \
--to=maxime@cerno.tech \
--cc=contact@emersion.fr \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nd@arm.com \
--cc=rodrigosiqueiramelo@gmail.com \
/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