linaro-dev April 2013

linaro-dev@lists.linaro.org

51 participants
55 discussions

Issue when running Snowball - GLES without X

by Hiep Pham

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_…) 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-request(a)lists.linaro.org wrote: > Send linaro-dev mailing list submissions to > linaro-dev(a)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-request(a)lists.linaro.org > > You can reach the person managing the list at > linaro-dev-owner(a)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 <eagles051387(a)gmail.com> > To: Nicolas Dechesne <nicolas.dechesne(a)linaro.org> > Cc: Linaro Dev <linaro-dev(a)lists.linaro.org> > Subject: Re: Suggestion > Message-ID: > <CAHdpx60hYtqb+kdthhr79mvcc5JnsWHuaV3psOMPyw-EPn2BHA(a)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.dechesne(a)linaro.org> wrote: > >> On Wed, Apr 17, 2013 at 6:21 AM, Jonathan Aquilina >> <eagles051387(a)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/Docume… >> >> nicolas >> > >

11 years

Mali-ization

by Andy Green

Hi - At the moment the Mali T624 OOT module sources I have do not build against 3.9-rcX / linux-linaro-core-tracking. A colleague checked it and it does build against 3.4. The problems I saw are around ION compatibility but they didn't look tremendously bad. I could work around the problems myself, but it seems to me this might be something that Linaro could solve centrally, dealing with it using the Androidization model - sync a Linaro repo against code drops coming from "upstream", ie, ARM, but keep it always building against llct inbetween. Perhaps even inside llct. I know we're not the only LT in this boat, Anmar mentioned Arndale acceleration is pending, a central Mali-ization tree will also solve that, especially if it's always there and always building in llct already. There may be stuff to take care about for support for different IP revision. But there aren't that many AFAIK. How does this sound to folks? -Andy -- Andy Green | Fujitsu Landing Team Leader Linaro.org │ Open source software for ARM SoCs | Follow Linaro http://facebook.com/pages/Linaro/155974581091106 - http://twitter.com/#!/linaroorg - http://linaro.org/linaro-blog

11 years

Re: [RFC PATCH] drm.h: Fix DRM compilation with bare-metal toolchain.

by Paul Sokolovsky

Hello, On Fri, 12 Apr 2013 18:28:26 -0500 Nishanth Menon <nm(a)ti.com> wrote: > From: Paul Sokolovsky <paul.sokolovsky(a)linaro.org> > > An ifdef in drm.h expects to be compiled with full-fledged Linux > toolchain, but it's common to compile kernel with just bare-metal > toolchain which doesn't define __linux__. So, also add __KERNEL__ > check. > > [nm(a)ti.com: port forward to 3.9-rc6 and post to dri devel for > feedback as RFC] Signed-off-by: Paul Sokolovsky > <paul.sokolovsky(a)linaro.org> --- > Paul, Dri devel list, > I picked up this patch from linaro tree: > https://git.linaro.org/gitweb?p=people/asac/android/kernel/lt-ti.git;a=patc… > Discussion thread: > http://lists.linaro.org/pipermail/linaro-dev/2011-June/thread.html#4874 > Seems to me as a valid fix even for upstream perhaps? Yes, IIRC, per the discussion you quote above, I sent this patch for review of our (Linaro's) kernel folks to see if it's ok (the patch is simple, story why it's needed may be not such, though I was positive it's needed). It might be forgotten somehow, thanks for picking it up! > Regards, Nishanth Menon > > include/uapi/drm/drm.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/include/uapi/drm/drm.h b/include/uapi/drm/drm.h > index 8d1e2bb..73a99e4 100644 > --- a/include/uapi/drm/drm.h > +++ b/include/uapi/drm/drm.h > @@ -36,7 +36,7 @@ > #ifndef _DRM_H_ > #define _DRM_H_ > > -#if defined(__linux__) > +#if defined(__KERNEL__) || defined(__linux__) > > #include <linux/types.h> > #include <asm/ioctl.h> -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

11 years

[ANNOUNCE] linux-linaro kernel schedule for 13.04 updated

by Andrey Konovalov

Greetings, This is a reminder that this wiki page: https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule - is now tracking the linux-linaro kernel rebuilds for 13.04. v3.9-rc6 based linux-linaro-core-tracking (llct) rebuild has just been published, the tag is llct-20130411.0. The next step is: April 12: ll rebuild based on llct-20130411.0. The last llct update for this cycle is scheduled on April 16, The last linux-linaro update for this cycle is scheduled on April 18. April 18 is the linux-linaro code freeze for 13.04 (only bug fixes allowed after this date). Thanks, Andrey

11 years

big.LITTLE MP status Apr 16, 2013

by David Zinman

https://wiki.linaro.org/projects/big.LITTLE.MP Work Items for functional completion: https://wiki.linaro.org/projects/big.LITTLE.MP/WorkItems Roadmap Cards: Epic big.LITTLE MP card - http://cards.linaro.org/browse/CARD-190 Main Project page: https://launchpad.net/linaro-big-little-system Announcement ============== Please welcome Serge Broslavsky as the new big.LITTLE project manager who will be taking over from David Zinman as the project moves forward. Serge will add this project on top of his duties as project manager for the Power Management team and the Virtualization project. Development ============= Big.LITTLE MP is following a two-track development: A Reference (stable) patchset: https://git.linaro.org/gitweb?p=arm/big.LITTLE/mp.git;a=shortlog;h=refs/hea… and an upstream (work in progress) patchset: https://git.linaro.org/gitweb?p=arm/big.LITTLE/mp.git;a=shortlog;h=refs/hea… Automated benchmarking code is ready (reviewing), permissions to be added. - Authentication is being added to the API. - Still having dependency on Android/LAVA teams Blueprint Update ------------------------- * - https://blueprints.launchpad.net/linaro-big-little-system/+spec/big-little-… - No issues, moving forward - https://blueprints.launchpad.net/linaro-big-little-system/+spec/cpuidle-add… - Postpone to the next month. - https://blueprints.launchpad.net/linaro-big-little-system/+spec/small-task-… - Preparing a more aggressive packing small tasks patchset version - Discussion around fix patches (rt task issue and nr_busy_cpus issue): almost ok now - Prototype should be available this week - https://blueprints.launchpad.net/linaro-big-little-system/+spec/cpu-hot-plu… - kernel crash happens when test enables function trace; reported this issue and updated blueprint. <https://launchpad.net/~daniel-lezcano> - https://blueprints.launchpad.net/linaro-big-little-system/+spec/document-bl… - produced a draft - https://blueprints.launchpad.net/linaro-big-little-system/+spec/sched-coope… - Long-lasting BP (6+ month to get something), just starting *QA === big.LITTLE MP LAVA Dashboard http://validation.linaro.org/lava-server/dashboard/image-reports/linaro-and… Testing: #Cases #Run Pass Fail Absolute pass rate Regression 20 19 19 0 100 % mpbasicsuite 14 10 10 0 100 % mpcoresuite 10 6 5 1 90 % mpextendedsuite 20 10 6 4 60 % mploadbalance 2 2 2 0 100 % http://lists.linaro.org/pipermail/linaro-dev/2013-April/015793.html Bugs: https://bugs.launchpad.net/linaro-big-little-system/+bugs?field.tag=bl-mp -- David Zinman, Project Manager Linaro.org | Open source software for ARM SoCs

11 years

Question relating to arm

by Jonathan Aquilina

>From my research I gather arm is just an architecture or chip producer as well? As i have a project, that might do sufficiently running on a dev board, or even a custom developed arm based board. I have been trying to find a contact email at arm but to no avail. Any help and information would be greatly appreciated. -- Jonathan Aquilina

11 years

[PATCH powerdebug] display proper error message

by Sanjay Singh Rawat

- bug : https://bugs.launchpad.net/linaro-powerdebug/+bug/1014667 Signed-off-by: Sanjay Singh Rawat <sanjay.rawat(a)linaro.org> --- display.c | 4 +++- powerdebug.c | 2 +- regulator.c | 4 +++- tree.c | 4 +++- 4 files changed, 10 insertions(+), 4 deletions(-) diff --git a/display.c b/display.c index f06387c..39a8e71 100644 --- a/display.c +++ b/display.c @@ -593,8 +593,10 @@ int display_register(int win, struct display_ops *ops) { size_t array_size = sizeof(windata) / sizeof(windata[0]); - if (win < 0 || win >= array_size) + if (win < 0 || win >= array_size) { + printf("error: invalid window"); return -1; + } windata[win].ops = ops; diff --git a/powerdebug.c b/powerdebug.c index 073fd42..ca04fab 100644 --- a/powerdebug.c +++ b/powerdebug.c @@ -243,7 +243,7 @@ int main(int argc, char **argv) } if (regulator_init()) { - printf("not enough memory to allocate regulators info\n"); + printf("failed to initialize regulator\n"); options->regulators = false; } diff --git a/regulator.c b/regulator.c index 0da924a..68c686f 100644 --- a/regulator.c +++ b/regulator.c @@ -218,8 +218,10 @@ static int fill_regulator_cb(struct tree *t, void *data) struct regulator_info *reg; reg = regulator_alloc(); - if (!reg) + if (!reg) { + printf("error: unable to allocate memory for regulator\n"); return -1; + } t->private = reg; /* we skip the root node but we set it expanded for its children */ diff --git a/tree.c b/tree.c index d331c60..686e846 100644 --- a/tree.c +++ b/tree.c @@ -121,8 +121,10 @@ static int tree_scan(struct tree *tree, tree_filter_t filter, bool follow) int ret = 0; dir = opendir(tree->path); - if (!dir) + if (!dir) { + printf("error: unable to open directory %s\n", tree->path); return -1; + } while (!readdir_r(dir, &dirent, &direntp)) { -- 1.7.9.5

11 years

[PATCH powerdebug] handle winch signal

by Sanjay Singh Rawat

- handle winch to display window properly - bug: https://bugs.launchpad.net/linaro-powerdebug/+bug/827828 Signed-off-by: Sanjay Singh Rawat <sanjay.rawat(a)linaro.org> --- display.c | 5 +++++ powerdebug.c | 4 ++++ 2 files changed, 9 insertions(+) diff --git a/display.c b/display.c index 39a8e71..e9f4bf6 100644 --- a/display.c +++ b/display.c @@ -137,6 +137,11 @@ int display_refresh_pad(int win) 0, 2, 0, maxy - 2, maxx); } +void sigwinch_handler(int signo) +{ + display_refresh(current_win, true); +} + static int display_show_unselection(int win, int line, bool bold) { if (mvwchgat(windata[win].pad, line, 0, -1, diff --git a/powerdebug.c b/powerdebug.c index dd6ac04..4ee7f7d 100644 --- a/powerdebug.c +++ b/powerdebug.c @@ -20,6 +20,7 @@ #include <stdio.h> #include <errno.h> #include <ncurses.h> +#include <signal.h> #include "regulator.h" #include "display.h" #include "clocks.h" @@ -28,6 +29,8 @@ #include "mainloop.h" #include "powerdebug.h" +extern void sigwinch_handler(int); + void usage(void) { printf("Usage: powerdebug [OPTIONS]\n"); @@ -207,6 +210,7 @@ static struct powerdebug_options *powerdebug_init(void) return NULL; memset(options, 0, sizeof(*options)); + signal(SIGWINCH, sigwinch_handler); return options; } -- 1.7.9.5

11 years

[PATCH] omap4.conf: Disable OMAP2 support

by Peter Ujfalusi

When the kernel is built with CONFIG_ARCH_OMAP2 it will select CPU_V6 and other dependencies which causes issues in user space. For example when clients try to connect to PulseAudio they will crash with: Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting. Remove support for OMAP2 for now. Signed-off-by: Peter Ujfalusi <peter.ujfalusi(a)ti.com> --- Hi Andrey, Can you take a look at this patch? In the latest hwpack for panda (with 3.9 kernel) PulseAudio clients all asserts with the following error: Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting. The same userspace works fine (well, mostly) with 3.8 based hwpacks. It turns out that this is cased by the CONFIG_ARCH_OMAP2, if we disable it PA clients no longer assert. Since the config in question is for OMAP4, I see no issue removing the OMAP2 support since in this way we can get PA working. One issue still remain with PA: None of float resample method works: speex-float-[0-10] However speex-fixed-[0-10] and ffmpeg seams to be working, but it is not perfect. I'll try to figure out why we have this failure since on my Gentoo FS all resample method works fine with the same kernel. Regards, Peter linaro/configs/omap4.conf | 1 + 1 file changed, 1 insertion(+) diff --git a/linaro/configs/omap4.conf b/linaro/configs/omap4.conf index 59e9f23..82c9365 100644 --- a/linaro/configs/omap4.conf +++ b/linaro/configs/omap4.conf @@ -11,6 +11,7 @@ CONFIG_OMAP_RESET_CLOCKS=y CONFIG_OMAP_MUX_DEBUG=y CONFIG_ARCH_OMAP2PLUS=y CONFIG_SOC_OMAP5=y +CONFIG_ARCH_OMAP2=n CONFIG_ARCH_VEXPRESS_CA9X4=y CONFIG_ARM_THUMBEE=y CONFIG_ARM_ERRATA_411920=y -- 1.7.10.4

11 years

big.LITTLE MP Scheduler test summary-week-15

by Naresh Kamboju

Hi, Release test report big.LITTLE MP week-15: Here is test result summary for big.LITTLE MP Scheduler test on TC2 platform with Android image sched_tests.git No of Test Cases Tests Run Tests Pass Tests Fail Absolute pass rate (%) Failure Analysis/Comments Regression 20 19 19 0 100 % mpbasicsuite 14 10 10 0 100 % mpcoresuite 10 6 5 1 90 % mpextendedsuite 20 10 6 4 60 % mploadbalance 2 2 2 0 100 % Android Build: https://android-build.linaro.org/builds/~linaro-android/vexpress-linaro-mp/… Linux kernel: Linux version 3.9.0-rc5-00238-g2b23d54 (jenkins-build@ip-10-226-9 7-251) (gcc version 4.7.3 20130226 (prerelease) (Linaro GCC 4.7-2013.03) ) #1 SMP Wed Apr 10 04:53:19 UTC 2013 Results spread sheet: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0Ai9ggMs8bsGJdER3a… Best regards Naresh Kamboju

11 years

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev April 2013