<div dir="ltr"><br clear="all"><div><div dir="ltr" class="m_6915353159249577360gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Thank you for the information. Yes I have a AMD GPU, It is a Radeon r5 m430. But unfortunately it does not have a video decoder. But I also have an integrated Intel HD 620 GPU, it's a kabylake and It had a video encoder and video decoder. I have already discussed about this with Alex Deuscher and he said that I will be fine with Intel HD 620 and I can carry on with the project.</div><div><br></div><div>If you don't mind can you please let me know if i am on the right track?</div><div><br></div><div>Thank you very much for your time </div><div><br></div><div>P.S:- Sorry for the starting a new thread with the last mail. I am new to mailing list. I will see to that I do not repeat the same mistake. </div><div><br></div><div><div dir="ltr" class="m_6915353159249577360gmail-m_6815021253767739103gmail_signature"><div dir="ltr">P . Naveen Naidu</div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Sun, 9 Sep 2018 at 12:25, <<a href="mailto:mesa-dev-request@lists.freedesktop.org" target="_blank">mesa-dev-request@lists.freedesktop.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send mesa-dev mailing list submissions to<br>
<a href="mailto:mesa-dev@lists.freedesktop.org" target="_blank">mesa-dev@lists.freedesktop.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/mesa-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:mesa-dev-request@lists.freedesktop.org" target="_blank">mesa-dev-request@lists.freedesktop.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:mesa-dev-owner@lists.freedesktop.org" target="_blank">mesa-dev-owner@lists.freedesktop.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of mesa-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: [PATCH v2] gallium: Correctly handle no config context<br>
creation (Elie Tournier)<br>
2. Re: [PATCH 2/2] gallium: try to fix the Windows build (Vinson Lee)<br>
3. [Bug 107870] Undefined symbols for architecture x86_64:<br>
"_util_cpu_caps" (<a href="mailto:bugzilla-daemon@freedesktop.org" target="_blank">bugzilla-daemon@freedesktop.org</a>)<br>
4. [PATCH] utils/u_math: break dependency on gallium/utils<br>
(Dylan Baker)<br>
5. Request for Mentor - XorgEvoc - Piglit for VA-API (Naveen Naidu)<br>
6. Re: Request for Mentor - XorgEvoc - Piglit for VA-API<br>
(Benson Muite)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 9 Sep 2018 04:57:45 +0100<br>
From: Elie Tournier <<a href="mailto:tournier.elie@gmail.com" target="_blank">tournier.elie@gmail.com</a>><br>
To: Marek Olšák <<a href="mailto:maraeo@gmail.com" target="_blank">maraeo@gmail.com</a>><br>
Cc: ML mesa-dev <<a href="mailto:mesa-dev@lists.freedesktop.org" target="_blank">mesa-dev@lists.freedesktop.org</a>><br>
Subject: Re: [Mesa-dev] [PATCH v2] gallium: Correctly handle no config<br>
context creation<br>
Message-ID:<br>
<CA+SrN4ySwRPnD_ku1O-_KCF0wr+iL21RiydU=<a href="mailto:S5xVqxFArgo5w@mail.gmail.com" target="_blank">S5xVqxFArgo5w@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
If you don't mind, can you please push this patch for me?<br>
I don't have git access.<br>
<br>
Thanks a lot,<br>
Elie<br>
On Fri, 7 Sep 2018 at 22:49, Marek Olšák <<a href="mailto:maraeo@gmail.com" target="_blank">maraeo@gmail.com</a>> wrote:<br>
><br>
> Reviewed-by: Marek Olšák <<a href="mailto:marek.olsak@amd.com" target="_blank">marek.olsak@amd.com</a>><br>
><br>
> Marek<br>
><br>
> On Thu, Sep 6, 2018 at 5:46 AM, Elie Tournier <<a href="mailto:tournier.elie@gmail.com" target="_blank">tournier.elie@gmail.com</a>> wrote:<br>
> > This patch fixes the following Piglit test:<br>
> > spec@egl_mesa_configless_context@basic<br>
> > It also fixes few test in a virgl guest.<br>
> ><br>
> > v2: Evaluate the value of no_config (Ilia)<br>
> ><br>
> > Suggested-by: Emil Velikov <<a href="mailto:emil.velikov@collabora.com" target="_blank">emil.velikov@collabora.com</a>><br>
> > Signed-off-by: Elie Tournier <<a href="mailto:elie.tournier@collabora.com" target="_blank">elie.tournier@collabora.com</a>><br>
> > ---<br>
> > src/gallium/include/state_tracker/st_api.h | 2 ++<br>
> > src/gallium/state_trackers/dri/dri_screen.c | 4 +++-<br>
> > src/mesa/state_tracker/st_manager.c | 9 ++++++++-<br>
> > 3 files changed, 13 insertions(+), 2 deletions(-)<br>
> ><br>
> > diff --git a/src/gallium/include/state_tracker/st_api.h b/src/gallium/include/state_tracker/st_api.h<br>
> > index 61152e3546..2b63b8a3d2 100644<br>
> > --- a/src/gallium/include/state_tracker/st_api.h<br>
> > +++ b/src/gallium/include/state_tracker/st_api.h<br>
> > @@ -190,6 +190,8 @@ struct st_egl_image<br>
> > */<br>
> > struct st_visual<br>
> > {<br>
> > + bool no_config;<br>
> > +<br>
> > /**<br>
> > * Available buffers. Bitfield of ST_ATTACHMENT_*_MASK bits.<br>
> > */<br>
> > diff --git a/src/gallium/state_trackers/dri/dri_screen.c b/src/gallium/state_trackers/dri/dri_screen.c<br>
> > index 027e85024f..308e23685e 100644<br>
> > --- a/src/gallium/state_trackers/dri/dri_screen.c<br>
> > +++ b/src/gallium/state_trackers/dri/dri_screen.c<br>
> > @@ -308,8 +308,10 @@ dri_fill_st_visual(struct st_visual *stvis,<br>
> > {<br>
> > memset(stvis, 0, sizeof(*stvis));<br>
> ><br>
> > - if (!mode)<br>
> > + if (!mode) {<br>
> > + stvis->no_config = true;<br>
> > return;<br>
> > + }<br>
> ><br>
> > /* Deduce the color format. */<br>
> > switch (mode->redMask) {<br>
> > diff --git a/src/mesa/state_tracker/st_manager.c b/src/mesa/state_tracker/st_manager.c<br>
> > index 69286b5791..9ed316b0f7 100644<br>
> > --- a/src/mesa/state_tracker/st_manager.c<br>
> > +++ b/src/mesa/state_tracker/st_manager.c<br>
> > @@ -834,6 +834,7 @@ st_api_create_context(struct st_api *stapi, struct st_manager *smapi,<br>
> > struct st_context *shared_ctx = (struct st_context *) shared_stctxi;<br>
> > struct st_context *st;<br>
> > struct pipe_context *pipe;<br>
> > + struct gl_config* mode_ptr;<br>
> > struct gl_config mode;<br>
> > gl_api api;<br>
> > bool no_error = false;<br>
> > @@ -893,7 +894,13 @@ st_api_create_context(struct st_api *stapi, struct st_manager *smapi,<br>
> > }<br>
> ><br>
> > st_visual_to_context_mode(&attribs->visual, &mode);<br>
> > - st = st_create_context(api, pipe, &mode, shared_ctx,<br>
> > +<br>
> > + if (attribs->visual.no_config)<br>
> > + mode_ptr = NULL;<br>
> > + else<br>
> > + mode_ptr = &mode;<br>
> > +<br>
> > + st = st_create_context(api, pipe, mode_ptr, shared_ctx,<br>
> > &attribs->options, no_error);<br>
> > if (!st) {<br>
> > *error = ST_CONTEXT_ERROR_NO_MEMORY;<br>
> > --<br>
> > 2.18.0<br>
> ><br>
> > _______________________________________________<br>
> > mesa-dev mailing list<br>
> > <a href="mailto:mesa-dev@lists.freedesktop.org" target="_blank">mesa-dev@lists.freedesktop.org</a><br>
> > <a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/mesa-dev</a><br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Sat, 8 Sep 2018 22:22:27 -0700<br>
From: Vinson Lee <<a href="mailto:vlee@freedesktop.org" target="_blank">vlee@freedesktop.org</a>><br>
To: Marek Olšák <<a href="mailto:maraeo@gmail.com" target="_blank">maraeo@gmail.com</a>><br>
Cc: ML mesa-dev <<a href="mailto:mesa-dev@lists.freedesktop.org" target="_blank">mesa-dev@lists.freedesktop.org</a>><br>
Subject: Re: [Mesa-dev] [PATCH 2/2] gallium: try to fix the Windows<br>
build<br>
Message-ID:<br>
<CACKvgLEBT5s+ycv2GixwHbfL3FnBQ=<a href="mailto:RCY6Uw4PKj9mAP-Nc84A@mail.gmail.com" target="_blank">RCY6Uw4PKj9mAP-Nc84A@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
On Sat, Sep 8, 2018 at 6:02 PM, Marek Olšák <<a href="mailto:maraeo@gmail.com" target="_blank">maraeo@gmail.com</a>> wrote:<br>
> From: Marek Olšák <<a href="mailto:marek.olsak@amd.com" target="_blank">marek.olsak@amd.com</a>><br>
><br>
> Windows doesn't have thrd_current.<br>
> ---<br>
> src/gallium/auxiliary/util/u_helpers.c | 2 ++<br>
> 1 file changed, 2 insertions(+)<br>
><br>
> diff --git a/src/gallium/auxiliary/util/u_helpers.c b/src/gallium/auxiliary/util/u_helpers.c<br>
> index f773360..8095242 100644<br>
> --- a/src/gallium/auxiliary/util/u_helpers.c<br>
> +++ b/src/gallium/auxiliary/util/u_helpers.c<br>
> @@ -127,20 +127,21 @@ util_upload_index_buffer(struct pipe_context *pipe,<br>
> * The function pins the current thread and driver threads to a group of<br>
> * CPU cores that share the same L3 cache. This is needed for good multi-<br>
> * threading performance on AMD Zen CPUs.<br>
> *<br>
> * \param upper_thread thread in the state tracker that also needs to be<br>
> * pinned.<br>
> */<br>
> void<br>
> util_context_thread_changed(struct pipe_context *ctx, thrd_t *upper_thread)<br>
> {<br>
> +#ifdef HAVE_PTHREAD<br>
> thrd_t current = thrd_current();<br>
> int cache = util_get_L3_for_pinned_thread(current,<br>
> util_cpu_caps.cores_per_L3);<br>
><br>
> /* If the main thread is not pinned, choose the L3 cache. */<br>
> if (cache == -1) {<br>
> unsigned num_caches = util_cpu_caps.nr_cpus /<br>
> util_cpu_caps.cores_per_L3;<br>
> static unsigned last_cache;<br>
><br>
> @@ -151,20 +152,21 @@ util_context_thread_changed(struct pipe_context *ctx, thrd_t *upper_thread)<br>
><br>
> /* Tell the driver to pin its threads to the same L3 cache. */<br>
> if (ctx->set_context_param) {<br>
> ctx->set_context_param(ctx, PIPE_CONTEXT_PARAM_PIN_THREADS_TO_L3_CACHE,<br>
> cache);<br>
> }<br>
><br>
> /* Do the same for the upper level thread if there is any (e.g. glthread) */<br>
> if (upper_thread)<br>
> util_pin_thread_to_L3(*upper_thread, cache, util_cpu_caps.cores_per_L3);<br>
> +#endif<br>
> }<br>
><br>
> /* This is a helper for hardware bring-up. Don't remove. */<br>
> struct pipe_query *<br>
> util_begin_pipestat_query(struct pipe_context *ctx)<br>
> {<br>
> struct pipe_query *q =<br>
> ctx->create_query(ctx, PIPE_QUERY_PIPELINE_STATISTICS, 0);<br>
> if (!q)<br>
> return NULL;<br>
> --<br>
> 2.7.4<br>
><br>
> _______________________________________________<br>
> mesa-dev mailing list<br>
> <a href="mailto:mesa-dev@lists.freedesktop.org" target="_blank">mesa-dev@lists.freedesktop.org</a><br>
> <a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/mesa-dev</a><br>
<br>
Tested-by: Vinson Lee <<a href="mailto:vlee@freedesktop.org" target="_blank">vlee@freedesktop.org</a>><br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Sun, 09 Sep 2018 05:34:28 +0000<br>
From: <a href="mailto:bugzilla-daemon@freedesktop.org" target="_blank">bugzilla-daemon@freedesktop.org</a><br>
To: <a href="mailto:mesa-dev@lists.freedesktop.org" target="_blank">mesa-dev@lists.freedesktop.org</a><br>
Subject: [Mesa-dev] [Bug 107870] Undefined symbols for architecture<br>
x86_64: "_util_cpu_caps"<br>
Message-ID: <<a href="http://bug-107870-598@http.bugs.freedesktop.org/" rel="noreferrer" target="_blank">bug-107870-598@http.bugs.freedesktop.org/</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<a href="https://bugs.freedesktop.org/show_bug.cgi?id=107870" rel="noreferrer" target="_blank">https://bugs.freedesktop.org/show_bug.cgi?id=107870</a><br>
<br>
Bug ID: 107870<br>
Summary: Undefined symbols for architecture x86_64:<br>
"_util_cpu_caps"<br>
Product: Mesa<br>
Version: git<br>
Hardware: x86-64 (AMD64)<br>
OS: Mac OS X (All)<br>
Status: NEW<br>
Keywords: regression<br>
Severity: normal<br>
Priority: medium<br>
Component: Mesa core<br>
Assignee: <a href="mailto:mesa-dev@lists.freedesktop.org" target="_blank">mesa-dev@lists.freedesktop.org</a><br>
Reporter: <a href="mailto:vlee@freedesktop.org" target="_blank">vlee@freedesktop.org</a><br>
QA Contact: <a href="mailto:mesa-dev@lists.freedesktop.org" target="_blank">mesa-dev@lists.freedesktop.org</a><br>
CC: <a href="mailto:baker.dylan.c@gmail.com" target="_blank">baker.dylan.c@gmail.com</a><br>
<br>
CXXLD <a href="http://mesa_dri_drivers.la" rel="noreferrer" target="_blank">mesa_dri_drivers.la</a><br>
Undefined symbols for architecture x86_64:<br>
"_util_cpu_caps", referenced from:<br>
_util_fpstate_get in libmesa.a(libmesautil_la-u_math.o)<br>
_util_fpstate_set_denorms_to_zero in libmesa.a(libmesautil_la-u_math.o)<br>
_util_fpstate_set in libmesa.a(libmesautil_la-u_math.o)<br>
<br>
-- <br>
You are receiving this mail because:<br>
You are the assignee for the bug.<br>
You are the QA Contact for the bug.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.freedesktop.org/archives/mesa-dev/attachments/20180909/d81eb216/attachment-0001.html" rel="noreferrer" target="_blank">https://lists.freedesktop.org/archives/mesa-dev/attachments/20180909/d81eb216/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Sat, 8 Sep 2018 23:39:44 -0700<br>
From: Dylan Baker <<a href="mailto:dylan@pnwbakers.com" target="_blank">dylan@pnwbakers.com</a>><br>
To: <a href="mailto:mesa-dev@lists.freedesktop.org" target="_blank">mesa-dev@lists.freedesktop.org</a><br>
Subject: [Mesa-dev] [PATCH] utils/u_math: break dependency on<br>
gallium/utils<br>
Message-ID: <<a href="mailto:20180909063944.3230-1-dylan@pnwbakers.com" target="_blank">20180909063944.3230-1-dylan@pnwbakers.com</a>><br>
<br>
Currently u_math needs gallium utils for cpu detection. Most of what<br>
u_math uses out of u_cpu_detection is duplicated in src/mesa/x86<br>
(surprise!), so I've just reworked it as much as possible to use the<br>
x86/common_x86_features macros instead of the gallium ones. There is<br>
one small function that was copied over, as promoting u_cpu_detection is<br>
itself a fairly hefty undertaking, as it depends on u_debug, and this<br>
fixes the bug for now.<br>
<br>
bugzilla: <a href="https://bugs.freedesktop.org/show_bug.cgi?id=107870" rel="noreferrer" target="_blank">https://bugs.freedesktop.org/show_bug.cgi?id=107870</a><br>
cc: <a href="mailto:vlee@freedesktop.org" target="_blank">vlee@freedesktop.org</a><br>
---<br>
<br>
I have no idea if this fixes the build on mac, I had this in a branch where I<br>
started replacing more of imports.{h,c} with utils stuff, and this fixes some<br>
build problems on Linux. I don't have a mac to test on and I wont until Monday.<br>
If this works let me know.<br>
<br>
src/util/u_math.c | 43 ++++++++++++++++++++++++++++++++++++++-----<br>
1 file changed, 38 insertions(+), 5 deletions(-)<br>
<br>
diff --git a/src/util/u_math.c b/src/util/u_math.c<br>
index c58af911be7..bf0c398eeec 100644<br>
--- a/src/util/u_math.c<br>
+++ b/src/util/u_math.c<br>
@@ -29,7 +29,7 @@<br>
<br>
#include "pipe/p_config.h"<br>
#include "util/u_math.h"<br>
-#include "util/u_cpu_detect.h"<br>
+#include "x86/common_x86_features.h"<br>
<br>
#if defined(PIPE_ARCH_SSE)<br>
#include <xmmintrin.h><br>
@@ -90,7 +90,7 @@ util_fpstate_get(void)<br>
unsigned mxcsr = 0;<br>
<br>
#if defined(PIPE_ARCH_SSE)<br>
- if (util_cpu_caps.has_sse) {<br>
+ if (cpu_has_xmm) {<br>
mxcsr = _mm_getcsr();<br>
}<br>
#endif<br>
@@ -98,6 +98,31 @@ util_fpstate_get(void)<br>
return mxcsr;<br>
}<br>
<br>
+/* TODO: this was copied from u_cpu_detection. It's another case of duplication<br>
+ * between gallium and core mesa, and it would be nice to get rid of that<br>
+ * duplication as well.<br>
+ */<br>
+#if defined(PIPE_ARCH_X86)<br>
+PIPE_ALIGN_STACK static inline bool sse2_has_daz(void)<br>
+{<br>
+ struct {<br>
+ uint32_t pad1[7];<br>
+ uint32_t mxcsr_mask;<br>
+ uint32_t pad2[128-8];<br>
+ } PIPE_ALIGN_VAR(16) fxarea;<br>
+<br>
+ fxarea.mxcsr_mask = 0;<br>
+#if defined(PIPE_CC_GCC)<br>
+ __asm __volatile ("fxsave %0" : "+m" (fxarea));<br>
+#elif defined(PIPE_CC_MSVC) || defined(PIPE_CC_ICL)<br>
+ _fxsave(&fxarea);<br>
+#else<br>
+ fxarea.mxcsr_mask = 0;<br>
+#endif<br>
+ return !!(fxarea.mxcsr_mask & (1 << 6));<br>
+}<br>
+#endif<br>
+<br>
/**<br>
* Make sure that the fp treats the denormalized floating<br>
* point numbers as zero.<br>
@@ -108,13 +133,21 @@ unsigned<br>
util_fpstate_set_denorms_to_zero(unsigned current_mxcsr)<br>
{<br>
#if defined(PIPE_ARCH_SSE)<br>
- if (util_cpu_caps.has_sse) {<br>
+ if (cpu_has_xmm) {<br>
/* Enable flush to zero mode */<br>
current_mxcsr |= _MM_FLUSH_ZERO_MASK;<br>
- if (util_cpu_caps.has_daz) {<br>
+ /* x86_64 cpus always have daz, as do cpus with sse3 in fact, there's<br>
+ * basically only a handful of very early pentium 4's that have sse2 but<br>
+ * not daz.<br>
+ */<br>
+# if !defined(PIPE_ARCH_x86_64) && !defined(PIPE_ARCH_SSSE3)<br>
+ if (sse2_has_daz()) {<br>
+# endif<br>
/* Enable denormals are zero mode */<br>
current_mxcsr |= _MM_DENORMALS_ZERO_MASK;<br>
+# if !defined(PIPE_ARCH_x86_64) && !defined(PIPE_ARCH_SSSE3)<br>
}<br>
+#endif<br>
util_fpstate_set(current_mxcsr);<br>
}<br>
#endif<br>
@@ -130,7 +163,7 @@ void<br>
util_fpstate_set(unsigned mxcsr)<br>
{<br>
#if defined(PIPE_ARCH_SSE)<br>
- if (util_cpu_caps.has_sse) {<br>
+ if (cpu_has_xmm) {<br>
_mm_setcsr(mxcsr);<br>
}<br>
#endif<br>
-- <br>
2.18.0<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Sun, 9 Sep 2018 12:11:45 +0530<br>
From: Naveen Naidu <<a href="mailto:naveennaidu479@gmail.com" target="_blank">naveennaidu479@gmail.com</a>><br>
To: <a href="mailto:mesa-dev@lists.freedesktop.org" target="_blank">mesa-dev@lists.freedesktop.org</a><br>
Subject: [Mesa-dev] Request for Mentor - XorgEvoc - Piglit for VA-API<br>
Message-ID:<br>
<CAB=7UR0+2ENn5y7u3pov=yt9aduG-hG3-WG_CboL_=o=<a href="mailto:J0kxsw@mail.gmail.com" target="_blank">J0kxsw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hello Everyone,<br>
<br>
I am Naveen a Junior year computer science undergrad from India. I really<br>
apologize for disturbing you all again. But I have been going through the<br>
available projects for the XorgEVoC program and the project *Piglit for<br>
VA-API *caught my attention. I have mailed last week looking out for<br>
mentors for the project, but unfortunately this email did not receive<br>
attention due to the busy schedule at Xorg I guess.<br>
<br>
I have been working on the project since the last time I mailed asking for<br>
directions. As Alex mentioned in his reply, I have read through the piglit<br>
documentation and am now sufficiently familiar with piglit.<br>
<br>
Things that I have done until now:-<br>
<br>
1. Read through the Piglit documentation (Capable of understanding and<br>
writing small tests using piglit)<br>
2. Compiled gstreamer, and also set up the gst-uninstalled environment.<br>
3. Understood about the architecture of gstreamer.<br>
4. Currently reading about VA-API.<br>
5. Planning to implement a simple VA-API app to better understand the<br>
type of tests I need to write for VA-API<br>
<br>
<br>
I am comfortable with both C and Python and given the skill set I am<br>
confident of accomplishing the project. I would thus like to discuss the<br>
details and deliverable of the project with my potential mentor and would<br>
like to know how I can proceed with the project.<br>
<br>
Since no potential mentor was mentioned in the Idea's Page, it would be<br>
really kind of someone if they are willing to be a mentor for the project.<br>
I can assure you that I will put the best of my efforts and dedication into<br>
the project and will see that the project is completed.<br>
<br>
Thank you for your valuable time.<br>
<br>
Regards,<br>
Naveen Naidu<br>
<a href="https://github.com/Naveenaidu" rel="noreferrer" target="_blank">https://github.com/Naveenaidu</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.freedesktop.org/archives/mesa-dev/attachments/20180909/b5f18641/attachment-0001.html" rel="noreferrer" target="_blank">https://lists.freedesktop.org/archives/mesa-dev/attachments/20180909/b5f18641/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Sun, 9 Sep 2018 09:54:06 +0300<br>
From: Benson Muite <<a href="mailto:benson.muite@ut.ee" target="_blank">benson.muite@ut.ee</a>><br>
To: <a href="mailto:mesa-dev@lists.freedesktop.org" target="_blank">mesa-dev@lists.freedesktop.org</a><br>
Subject: Re: [Mesa-dev] Request for Mentor - XorgEvoc - Piglit for<br>
VA-API<br>
Message-ID: <<a href="mailto:44cad40b-a1c3-cc91-625e-856644a65181@ut.ee" target="_blank">44cad40b-a1c3-cc91-625e-856644a65181@ut.ee</a>><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
Welcome! From the page:<br>
<br>
<a href="https://www.x.org/wiki/SummerOfCodeIdeas/" rel="noreferrer" target="_blank">https://www.x.org/wiki/SummerOfCodeIdeas/</a><br>
<br>
Might try and ping Christian König. Do you have an AMD GPU?<br>
<br>
Benson<br>
<br>
On 09/09/2018 09:41 AM, Naveen Naidu wrote:<br>
> Hello Everyone,<br>
><br>
> I am Naveen a Junior year computer science undergrad from India. I <br>
> really apologize for disturbing you all again. But I have been going <br>
> through the available projects for the XorgEVoC program and the <br>
> project *Piglit for VA-API *caught my attention. I have mailed last <br>
> week looking out for mentors for the project, but unfortunately this <br>
> email did not receive attention due to the busy schedule at Xorg I guess.<br>
><br>
> I have been working on the project since the last time I mailed asking <br>
> for directions. As Alex mentioned in his reply, I have read through <br>
> the piglit documentation and am now sufficiently familiar with piglit.<br>
><br>
> Things that I have done until now:-<br>
><br>
> 1. Read through the Piglit documentation (Capable of understanding<br>
> and writing small tests using piglit)<br>
> 2. Compiled gstreamer, and also set up the gst-uninstalled environment.<br>
> 3. Understood about the architecture of gstreamer.<br>
> 4. Currently reading about VA-API.<br>
> 5. Planning to implement a simple VA-API app to better understand the<br>
> type of tests I need to write for VA-API<br>
><br>
><br>
> I am comfortable with both C and Python and given the skill set I am <br>
> confident of accomplishing the project. I would thus like to discuss <br>
> the details and deliverable of the project with my potential mentor <br>
> and would like to know how I can proceed with the project.<br>
><br>
> Since no potential mentor was mentioned in the Idea's Page, it would <br>
> be really kind of someone if they are willing to be a mentor for the <br>
> project. I can assure you that I will put the best of my efforts and <br>
> dedication into the project and will see that the project is completed.<br>
><br>
> Thank you for your valuable time.<br>
><br>
> Regards,<br>
> Naveen Naidu<br>
> <a href="https://github.com/Naveenaidu" rel="noreferrer" target="_blank">https://github.com/Naveenaidu</a><br>
><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.freedesktop.org/archives/mesa-dev/attachments/20180909/9585c507/attachment.html" rel="noreferrer" target="_blank">https://lists.freedesktop.org/archives/mesa-dev/attachments/20180909/9585c507/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
mesa-dev mailing list<br>
<a href="mailto:mesa-dev@lists.freedesktop.org" target="_blank">mesa-dev@lists.freedesktop.org</a><br>
<a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/mesa-dev</a><br>
<br>
<br>
------------------------------<br>
<br>
End of mesa-dev Digest, Vol 102, Issue 134<br>
******************************************<br>
</blockquote></div></div>