Hi all, I'm trying GLES on Snowball board with Mali GPU, without X.
The board was installed linaro-nano 12.07 (with mali400-dev package installed) and had been connected with an TV via HDMI cable; After booting up, I run "hdmistart" command and /dev/fb0 appeared; HDMI ran fine with "cat /dev/urandom > /dev/fb0" command. However, when testing GLES with sample codes from Mali SDK (http://malideveloper.arm.com/downloads/Mali_OpenGL_ES_2.0_SDK_for_Linux_On_ARM_v1.2.0.9310_Linux.tar.gz) I got following error: Error: eglGetError(): 12288 (0x3000) Error: No EGL Display available at /root/Mali_OpenGL_ES_2.0_SDK_for_Linux_On_ARM_v1.2.0/simple-framework/src/EGLRuntime.cpp:105 The argument of eglGetDisplay is EGL_DEFAULT_DISPLAY: EGLDisplay display = eglGetDisplay(EGL_DEFAULT_DISPLAY); So I wonder if Mali can works without X or not? Any help will be greatly appreciate, --- Hiep On 04/17/2013 06:26 PM, linaro-dev-requ...@lists.linaro.org wrote: > Send linaro-dev mailing list submissions to > linaro-dev@lists.linaro.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.linaro.org/mailman/listinfo/linaro-dev > or, via email, send a message with subject or body 'help' to > linaro-dev-requ...@lists.linaro.org > > You can reach the person managing the list at > linaro-dev-ow...@lists.linaro.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of linaro-dev digest..." > > > Today's Topics: > > 1. Re: Suggestion (Jonathan Aquilina) > 2. Re: Suggestion (Jon Medhurst (Tixy)) > 3. Re: [RFC PATCH] drm.h: Fix DRM compilation with bare-metal > toolchain. (Arnd Bergmann) > 4. Re: [RFC PATCH] drm.h: Fix DRM compilation with bare-metal > toolchain. (Jon Medhurst (Tixy)) > 5. Re: Mali-ization (Tushar Behera) > 6. Re: Mali-ization (Jon Medhurst (Tixy)) > 7. Re: [RFC PATCH] drm.h: Fix DRM compilation with bare-metal > toolchain. (Rob Clark) > 8. Re: Mali-ization (Andy Green) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 17 Apr 2013 09:54:11 +0200 > From: Jonathan Aquilina <eagles051...@gmail.com> > To: Nicolas Dechesne <nicolas.deche...@linaro.org> > Cc: Linaro Dev <linaro-dev@lists.linaro.org> > Subject: Re: Suggestion > Message-ID: > <cahdpx60hytqb+kdthhr79mvcc5jnswhuav3psompyw-epn2...@mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Totally under stand :). Hopefully come summer I will be able to get my > hands on a board and start contributing :) > > > On Wed, Apr 17, 2013 at 9:51 AM, Nicolas Dechesne < > nicolas.deche...@linaro.org> wrote: > >> On Wed, Apr 17, 2013 at 6:21 AM, Jonathan Aquilina >> <eagles051...@gmail.com> wrote: >>> Doesnt email run the risk of a patch slipping through the cracks? >> as highlighted by Deepak above, each project will use the >> processes/methods inherited from its 'upstream'. That's why gerrit is >> being used for Android activities for example. many successful open >> source projects are using solely email for patch submission and >> review, and that happens to work fine. yes, that makes lots of emails, >> and patches can be lost, but the general rule is that it's up to the >> patch author to follow-up and potentially resubmit when such things >> happen. for example, the Linux kernel documentation says this: >> >> >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SubmittingPatches?id=refs/tags/v3.9-rc7#n262 >> >> nicolas >> > > _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
