All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] glmark2 and mesa3d-demos
Date: Sun, 12 Oct 2014 17:37:29 +0200	[thread overview]
Message-ID: <20141012173729.0a6a883e@free-electrons.com> (raw)

Hello Bernd,

Since you are our OpenGL/X.org guy, I wanted to know if you could be
interested by taking over the glmark2 and mesa3d-demos patches. As you
probably know those are OpenGL test programs, that could be interesting
to have in Buildroot test/check the OpenGL installation.

Historically, those patches were written by Spenser Gilliland, as part
of GSoC 2013. Unfortunately, they were not merged as a few issues
remained, and the GSoC ended before Spenser could provide a
mainline-acceptable solution. As part of the GSoC 2014, Hadrien also
tried to push this a bit further, but ran into issues.

Would you be interested in picking up those patches?

Here are the patchwork URLs:

  http://patchwork.ozlabs.org/patch/278304/
  http://patchwork.ozlabs.org/patch/278305/

Note that one of them depended on a specific (older) version of libpng,
so there were also other patches related to libpng
(http://patchwork.ozlabs.org/patch/278300/ and
http://patchwork.ozlabs.org/patch/278301/). Maybe a more recent version
of glmark2 or mesa3d-demos will use the more recent libpng API, and
therefore avoid the dependency on a specific version of libpng.

I'll mark the patches as "Changes Requested" in patchwork in the mean
time, hoping that you'll accept to take over them.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

             reply	other threads:[~2014-10-12 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-12 15:37 Thomas Petazzoni [this message]
2014-10-12 15:50 ` [Buildroot] glmark2 and mesa3d-demos Bernd Kuhls
2014-10-12 16:04   ` Thomas Petazzoni

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=20141012173729.0a6a883e@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.