From: Jani Nikula <jani.nikula@linux.intel.com>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] README: Document how to avoid Waffle with piglit
Date: Fri, 20 Dec 2013 17:32:50 +0200 [thread overview]
Message-ID: <87ioujzgf1.fsf@intel.com> (raw)
In-Reply-To: <1387551041-23872-1-git-send-email-daniel.vetter@ffwll.ch>
On Fri, 20 Dec 2013, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> Suggested by Paulo.
>
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> ---
> README | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/README b/README
> index 246e24c47ffe..f108b2087a98 100644
> --- a/README
> +++ b/README
> @@ -40,6 +40,16 @@ tests/
> piglit-sources $ cd bin
> piglit-sources/bin $ ln $i-g-t-sources igt -s
>
> + To avoid some hassles with piglit's use of Waffle just disable it. Run
> +
> + piglit-soruces $ cmake -D PIGLIT_USE_WAFFLE=OFF .
> +
> + With
> +
> + piglit-soruces $ ccmake .
Yup, only do this in the soruces directory. :p
BR,
Jani.
> +
> + you can check your configuration with a curses interface, too.
> +
> The tests in the i-g-t sources need to have been built already. Then we
> can run the testcases with (as usual as root, no other drm clients
> running):
> --
> 1.8.4.3
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
prev parent reply other threads:[~2013-12-20 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 14:50 [PATCH] README: Document how to avoid Waffle with piglit Daniel Vetter
2013-12-20 15:32 ` Jani Nikula [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=87ioujzgf1.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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