On Wed, Jun 5, 2013 at 10:33 PM, Chad Versace
wrote:
> Divick, you created two EGLDisplays. Did you obtain each EGLDisplay by
> passing the same
> native display to eglGetDisplay? If so, then EGL should have returned the
> same EGLDisplay
> pointer. The EGL spec requires that, and Mesa's libEGL h
Hi Brian,
thanks for your reply.
On Tue, May 28, 2013 at 9:33 PM, Brian Paul wrote:
> I took at look at eglCreateContext(). It's basically:
>
> EGLContext
> eglCreateContext(EGLDisplay dpy, EGLConfig config, EGLContext share_list,
> const EGLint *attrib_list)
> {
>
create shared context.
I would appreciate any help,
Thanks & Regards,
Divick
On Mon, May 27, 2013 at 1:35 PM, Divick Kishore
wrote:
> Hi,
> Does anyone know if mesa supports creation of shared context using egl?
>
> When I create a shared context with a call to eglCreateContext w
Hi,
Does anyone know if mesa supports creation of shared context using egl?
When I create a shared context with a call to eglCreateContext where
the third argument is a valid context, I get EGL_BAD_CONTEXT error.
Thanks & Regards,
Divick
___
mesa-de
Hi Matt,
> From the "build" in your path, it looks like you might be trying to do
> an out-of-tree build. I don't remember if that completely worked with
> 9.1.
>
> I just untarred 9.1.3 and did
>
> libtoolize --force
> ./autogen.sh --with-dri-drivers=i965,swrast
> --with-gallium-drivers=swrast --
Hi Matt,
On Thu, May 23, 2013 at 8:38 PM, Matt Turner wrote:
> On Thu, May 23, 2013 at 3:39 AM, Divick Kishore
>>>
>>> Could someone please help me build mesa 9.1.1?
>
> I think this is a build system bug caused by not building any classic
> hardware DRI driver
Hi,
I have written a simple program which shares data like texture and
shaders across two different GLContexts but it doesn't seem to work.
Is sharing of texture and shaders supported in Mesa EGL backend?
I first bind the first context and do the drawing and then I bind the
second context to c
Bump .. could someone please help me with this? Possibly I am missing
something small but can't seem to figure out.
Any help is appreciated.
Divick
On Thu, May 16, 2013 at 12:58 PM, Divick Kishore
wrote:
> Hi,
> I am trying to compile mesa 9.1.1 on my debian wheezy machine
Hi,
if I get the egl specs correctly then shouldn't querying these
attributes return the maximum supported pbuffer size? Does 0 mean the
size is unlimited or is it a bug in mesa egl implementation.
I am using mesa version 8.
Thanks & Regards,
Divick
___
> vblank_mode was broken for a long time in EGL, but current 9.0 and 9.1
> have it fixed. Not sure what version you're on.
I am using version 8.0.5. I have been unable to build the 9.1 for
softpipe renderer using the same options that I was using for building
8.0.5. I have posted separately on th
>> By default we sync to vblank, which for you is 60. The software
>> rasterizer lacks this feature.
I meant that even with h/w rasterizer I get fps = 60 with vblank=0 set.
> The weird thing is that he said he ran it with vblank_mode=0. Makes me
> wonder if we have a bug in our handling of tha
Hi,
I have a simple GLES2 based application which does not do much in
the either of the vertex and fragment shaders. It simply draws a
rotating spiral made from a simple triangle strip. When I try to run
this application using the mesa with h/w renderer, it gives me a
performance which is almos
Hi,
I am trying to compile mesa 9.1.1 on my debian wheezy machine but
I get compilation error during the build.
The configure options that I have used are:
../../configure --prefix=~/lib/mesa/dri_llvm --build=x86_64-linux-gnu
--with-dri-drivers="swrast" --with-dri-driverdir=~/lib/mesa/dri_llv
Hi Patrick,
> Perhaps 16-bit color isn't supported? Maybe try other color bits or set
> R/G/B individually and see what happens. Also, there is an eglinfo tool
> source code in Mesa that can probably tell you a whole lot more.
>
I see that es and es2 renderables are not supported due to which
egl
Hi Chia,
> I haven't tried that for a while, but it should not have X11
> dependencies. You probably need to disable other stuffs such as
> --disable-glx and etc. It might still require X11 at compile time,
> because eglplatform.h may include Xlib.h, but it should not need X11
> at runtime.
>
A
Just in case someone else faces the same issue. Resolved the issue and
was able to build the gallium softpipe renderer with llvm.
>. Could you guide me on how to
> build llvmpipe driver?
I was able to build the driver with llvm but I had to modify the
configure.ac (in mesa 8.0.5) to avoid specifi
Hi Patrick,
>
> I don't know a whole lot about Mesa's structure, but I know that the
> LLVMpipe driver is supposed to be the fastest software driver for x86 CPUs.
> The reason is that it JIT compiles vertex/fragment programs into x86/x64
> assembly using LLVM as the code generator. LLVM contains e
>
> Doesn't your glxgears tell you about it? Mine does:
It does. Just that I did not pay enough attention to it and did not
know how to avoid it to sync with vsync.
Thanks & Regards,
Divick
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http:/
Hi,
I have compiled mesa with the following options:
.././configure --prefix=~/lib/mesa/swrast/ --build=x86_64-linux-gnu
--with-gallium-drivers= --with-driver=xlib --enable-egl --enable-gles1
--enable-gles2 --with-egl-platforms="x11" CFLAGS="-Wall -g -O2"
CXXFLAGS="-Wall -g -O2"
but when I ru
Hi Chia,
> $ ./configure --disable-dri --enable-gallium-egl --with-egl-platforms=null \
> --with-gallium-drivers=swrast
>
> It will give you an EGL/GLES driver that uses a software renderer and
> supports only pbuffers (and FBOs).
The egl lib built so I see has dependency o
Hi,
is there a possibility in mesa to have egl backend based on
complete offscreen buffers and complete s/w only gles renderer? If
yes, then could someone please guide me how to build it?
Thanks & Regards,
Divick
___
mesa-dev mailing list
mesa-dev@li
Hi Patrick,
thanks for the reply. Could you guide me on how to
build llvmpipe driver?
Thanks & Regards,
Divick
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
> The default is to sync to the refresh rate. Try setting env var
> vblank_mode=0 to disable it.
>
Indeed with this, I see that the performance jumps to almost ~ 3850
fps. Thanks for pointing this out.
Thanks & Regards,
Divick
___
mesa-dev mailing list
On Mon, May 6, 2013 at 8:08 PM, Patrick Baggett
wrote:
> I don't think glxgears is the best benchmark for what is a "typical" OpenGL
> load (if there is a "typical"). The 60 FPS with your hardware driver sounds
> suspiciously like the refresh rate of your screen; perhaps it is
> synchronized with
Hi,
I am trying to build s/w only mesa driver. It seems that the
performance of software only renderer (compiled with
--with-driver=xlib) is higher than that of h/w drivers. Could someone
please help me understand what is causing this or if it is expected?
I see that dri based s/w renderer is
25 matches
Mail list logo
