Hi there. I'm looking for areas where the toolchain could generate
faster code, and a good way of doing that is seeing how compiled code
does against the best hand-written code. I know of skia, ffmpeg,
pixman, Orc, and efl - what others are out there?
Thanks for any input,
-- Michael
Hi,
notes and actions from our Wednesday graphics working group call are
available on the wiki:
+ https://wiki.linaro.org/WorkingGroups/Middleware/Graphics/Notes/2011-04-06
Details about when and where of this meeting can be found here:
+ https://wiki.linaro.org/WorkingGroups/Middleware/Graphics#Weekly%20Public%2…
Summary
=======
* Started porting two example programs (cairogears and cairo-clock) to cairo-gles2.
* Benchmarks
* Test definitions
* Created out-of-tree abrek test definitions branch (+packaging) for WG
for glcompbench, cairo-traces and qt-traces and added them to
linaro-graphics-wg-tests.
* Had a meeting with infrastructure/platform team to align benchmarking needs.
* glcompbench : Finished profiler branch and pushed to trunk (lp:glcompbench)
* Skia
* segfault happens in arm_memset32() for Tegra2 as well as EfikaMX if
ARM_HAVE_NEON not enabled, bug created in skia upstream
* Need account in git.linaro.org for creating skia branch
* Kwin : kdelibs and kde-workspace mainline packages available in Kunal's PPA
https://launchpad.net/~goelkunal/+archive/multimedia, but ARM build still
not available
* DRI/Mali
* Investigated overall KMS architecture and functionality and need to investigate
the recent source which allows KMS to allocate a buffer without using DRM.
* Added support in glewinfo file to verify the entry point of the ES and EGL
extensions supported.
* Compiz
* Updated build system to disable building non-ported plugins and went through
all core plugins and verified they work correctly.
* Tested on efikamx, needs some changes for improper GL_BGRA support then doesn't
draw correctly.
Thanks,
--
- Alexandros
Hi,
As we near final release it is even more important that bugs which
effect the LEB's and other images are caught early and fixed as soon as
possible. To help aid the Linaro Release Team [1] in identifying and
dealing with these types of bugs the following procedure significantly
helps on projects which produce, or are installed on the images:
1) All bugs in a 'New' state should be sufficiently triaged to
determine their 'Importance'.
2) All bugs which are deemed 'High' or 'Critical' should be
highlighted to the Release Team. To do this use the 'Subscribe
someone else' link on the right hand side of the bug. When the
pop-up appears type 'linaro-release' into the box and select the
release team when it is found.
3) If the bug needs discussion please add it to the wiki page for the
current weeks Release meeting. The calendar for the Release
meeting can be found at:
https://wiki.linaro.org/Cycles/WeeklyReleaseMeeting
Meetings are currently on a Thursday so add the bug to the 'Bugs'
section of the next meeting. If possible please attend the meeting.
The Release Team will go through the list of bugs [2] regularly and help
to get fixes in place ready for milestone releases [3]. This information
can also be found on the wiki at:
https://wiki.linaro.org/Cycles/BugManagement
Regards,
Jamie.
--
Linaro Release Manager | Platform Project Manager
[1] https://launchpad.net/~linaro-release
[2] https://bugs.launchpad.net/~linaro-release
[3] https://wiki.linaro.org/Cycles/1105#Milestones