Hi folks.
So there's been some justified uproar about me moving some stuff to
github without asking. I wanted to let you all know that we have a
Linaro organization on github (ping danilos to get your github account
included there). I've created the validation team there and allowed it
to push/pull to https://github.com/Linaro/lava-deployment-tool I also
have my own fork.
I wanted to give you a few reasons why I wanted to use github instead
of bzr (note, we've got a bzr mirror setup on launchpad so you can
always get the code from there)
1) Linaro uses git a lot and not all of us are fluent in it. Using git
on a small project is an excellent way to learn it without affecting a
ton of things
2) Github is IMHO arguably a much much much better place for code than
launchpad, this is a personal feeling but one I wanted to explain
better below.
3) With the git model I can keep all my branches in one repo, that is
a nice feature (I still prefer to work with many directories but the
annoyance of syncing them all is bigger than the adjustment to single
working directory model)
So having said that, those are the things that I prefer on github over
their launchpad counterparts:
* Github has hands down better UI, it is more pleasant to use and I
found myself to be a happier person. It has a ton of tiny things that
matter (like automatic archives, tarballs, zips etc, for all the tags
in your code, no more manual releases!)
* I like the social aspects of github, ability to follow on other
people's code and get notified. Launchpad feels like a corporate world
in comparison.
* Github has great code review UI, ability to do merges straight from
the web, better commenting on code pieces (apart from UI)
* Github still has an integrated bug tracker if you wanted to jump all
the way there. It also shares the niceness of the UI compared to LP
* Github does better stuff at presenting your projects, it can display
the README file (with nice formatting) by default, it can store your
wiki and your arbitrary static HTML site for free as well. It feels
much more complete compared to launchpad's "bring your own for those
two quite essential topics"
* Github has an _awesome_ integration with bazillion 3rd party tools
(for us we could get post-commit hooks for readthedocs for example,
something that is just not possible with launchpad). There are many
possibilities we could use for our own workflow (commit in production
branch gets deployed automatically, etc etc). While it is possible to
do such stuff with launchpad is always requires painful polling with
the python LP api.
So there you have it.
Best regards
ZK
Hi there,
The linux-arm-kernel[1] project on patches.l.o was using the following source
tree
http://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cur/linux-2.6-arm.git
to track committed patches, but fetching that repo seems to have become
ridiculously slow, causing git to take ages to update the local copy or get a
new one. So I'm wondering if there's any mirror of that repo (served via
HTTP as we can't fetch git:// URLs from the machine that runs patches.l.o)
somewhere with a bigger pipe? If not, would it be ok to change the source
tree of linux-arm-kernel to Linus' tree?
[1] http://patches.linaro.org/project/linux-arm-kernel/
--
Guilherme Salgado <https://launchpad.net/~salgado>
Updated weekly dashboard for Graphics (NEW!) with more details and links
[1]:
https://wiki.linaro.org/WorkingGroups/Middleware/Graphics/WeeklyReport
Last weekly meeting notes:
https://wiki.linaro.org/WorkingGroups/Middleware/Graphics/Notes/2011-12-07
Highlights:
- Jesse's blog post attracted more than 7500 visits since its upload
- glmark2: ready for the release and also has a prototype working for
LAVA dashboard
- glproxy: Finishing EGL support
- glcompbench: Adapting glproxy branch to use the new EGL support
- dmabuf rework based on comments from list
- API trace - sent patches upstream. Some have landed in master. Some
are pending/under discussion
Issues:
- Unity/NUX/Compiz:
* though NUX code is merged upstream there has not been a new version of
NUX from DX (plus it would need a new version of Unity to show the new
features). This is expected 2nd week of January.
* Also Compiz/Unity: they were blocked from DX side because of the need
to put test automation and build infrastructure - This is now done for
Unity, not done for Compiz.
* Worst case scenario: we release the last working versions for Linaro's
builds, until all 3 are unblocked from DX. We are following up with DX
closely - Priority: resolve the framebuffer object issues (as per
Travis's suggestion)
Release: The release is in good shape overall. However for
Compiz/Nux/Unity there is a risk as indicated above. We are checking
with Ricardo Salveti, whether we can at least update the compiz packages
to add recent bugfixes and some other changes, if there are no breakages
in Unity code.
Comments/Questions? Please send them across :-)
[1]: I have updated the layout of the weekly report, experimentally, in
an attempt to improve readability. It should give a highlight now at a
glance. One can dig into the blueprints for more information or ask via
email/IRC if there are deeper questions. Feel free to comment.
--
Ilias Biris ilias.biris(a)linaro.org
Project Manager, Linaro
M: +358504839608, IRC: ibiris Skype: ilias_biris
Linaro.org│ Open source software for ARM SoCs
Hi,
Another package that was requested to be able to cross-compiled was
chromium. Now this is possible also, following the instructions at:
https://wiki.linaro.org/Platform/DevPlatform/CrossCompile/ChromiumCrossComp…
The starting point was chromium not building on arm at all,
fortunately it was quite easy to fix. While easy, it was time
consuming as I had to build chrome a few times natively. With builds
taking around 20h on panda. Meanwhile, on dual-core (hypertheaded, so
kinda 4-core) Intel i5 M 520, cross-compile took around 1.5h. When the
native builds were failing at the final linking stage, the value of
cross-compiling was surely becoming clear ;)
Cheers,
Riku
Hi LAVA users
We'll be taking the system down for a brief maintenance session.
We will be running a stale database migration to address the issues of
https://bugs.launchpad.net/lava-dashboard/+bug/892562 specifically to run
the migration we did not run two days ago due to a special one-off upgrade
process.
Best regards
Zygmunt Krynicki
Greetings,
This e-mail is for Linaro community members (Linaro engineers have
already been notified).
We are currently working on re-organizing the wiki to make it more
useful to you Linaro contributors and developers. Though we have our own
ideas, it's *very important* to us to make sure we understand how you
are using the pages, how you get to the information, as well as what you
would like to see improved upon and more. We can't fix what we don't
know is broken.
If you already are a contributor to Linaro, I'm sure you have experience
with our wiki. Again, please let us know about your opinions about the
wiki and how you use it by answering the on-line survey created by Amber
Graner: http://www.surveymonkey.com/s/C7XVGT5
The survey is anonymous and should take at most 15 minutes to complete
if you have comments to make. Be careful that the survey with close on
Monday, December 12, 24:00 UTC.
If you are new to Linaro, but still interested in helping us, you could
still help us by having a fresh look at http://wiki.linaro.org,
exploring it and eventually taking the survey to let us know what you think.
Thanks for your support.
Michael.
--
Michael Opdenacker - Community Manager
Linaro, http://linaro.org
Phone: +33 484 253 396
IRC: 'opm' in #linaro on irc.freenode.net
Hi
I think we should document the current LAVA upgrade plan.
Please review this page if you are interested in this topic.
There are some ISSUES and unfinished parts, please post your ideas about
that.
https://wiki.linaro.org/Platform/Validation/DevOps/LavaProductionUpgrade
Best regards
ZK
The deployment of LAVA using Ubuntu packages is deprecated in favor of the
dedicated LAVA deployment tool [1]. LAVA installation is tested and supported
on Ubuntu host from version 10.10 to 11.10 (Maverick to Oneiric) [2].
>From 11.12 cycle, the following conditions will be applied:
* Linaro Validation PPA [3] won't be updated with latest LAVA releases.
* Bugs affecting packages won't be fixed.
We plan to provide LAVA deployment tool from Linaro Validation PPA.
[1] http://launchpad.net/lava-deployment-tool
[2] Ubuntu 10.04 LTS (Lucid) isn't supported due to a bug with upstart
[3] http://launchpad.net/~linaro-validation/+archive/ppa
--
Fathi Boudra
Linaro Release Manager | Validation Project Manager
Linaro.org | Open source software for ARM SoCs
Hi all,
I would like to just mention to anyone that's interested that Genesi's
Ahmed Ammar and Steev Klimaszewski, managed to get Android ICS running
on the EfikaMX Smarttop (no Smartbook yet, working on it), along with
3D acceleration. Details are here:
http://www.powerdeveloper.org/forums/viewtopic.php?p=15539
As noted in the post, it's pre-alpha software, and a work in progress,
but it's good for a tech demo or for testing purposes.
Also, some of you might already have noticed that there is a iMX53
developer program started:
http://www.powerdeveloper.org/forums/viewtopic.php?t=2092
Last year Genesi gave away around 100 iMX51 Smartbooks and Smarttops
to projects like Debian, Ubuntu, Linaro, Fedora, Gentoo, etc. We would
like to repeat that -although with slight differences, eg. priority
will be given to people that have already contributed to previous
projects with the iMX51 Smart* devices. In short we will always
consider nice projects for inclusions in the program, and of course
being part of Linaro is an added bonus -though the program is not
restricted to Linaro engineers only.
Please read the thread for details on how to apply for the iMX53 Efika.
Thanks
Konstantinos Margaritis
hats: Genesi, Linaro, Debian.
Hi,
Just to let you all know, due to the ongoing multiarch work, it is not
possible to cross-compile
relatively complex packages in ubuntu. For example, following the
instructions[1], Firefox. While
building on oneiric, patched packages from the linaro-maintainers
overlay are needed, many of
those patches are on precise, and rest should get there during the next cycle.
Cheers,
Riku
[1] https://wiki.linaro.org/Platform/DevPlatform/CrossCompile/FirefoxCrossCompi…