Please disregard previous draft a few minutes ago, it was sent in error.
Greetings,
This is a mail sent to remind you the coming release dates:
* Linaro 11.12 Toolchain WG release December 8, 2011.
* Linaro 11.12 Platform/WGs/LTs is December 15, 2011.
* Linaro 11.12 Release Candidate is December 19, 2011.
* Linaro 11.12 Release images is December 22, 2011
(early due to Christmas holiday).
* Linaro 11.12 release is UTC 16:00, December 22, 2011.
Components release will be announced this week.
The release dates and deliveries information is available from the release
dashboard: http://wiki.linaro.org/Cycles/1112/Release/Dashboard
--
David Zinman
Linaro Release Manager | Project Manager
Linaro.org | Open source software for ARM SoCs
Greetings,
This is a mail sent to remind you the coming release dates:
* Linaro 11.11 components release is November 17th, 2011.
* Linaro 11.10 RC images is November 21st, 2011.
* Linaro 11.10 Release images is November 21st, 2011 (due to holiday
on Nov 24).
* Linaro 11.10 release is UTC 16:00, November 24th, 2011.
Components release will be announced this week.
The release dates and deliveries information is available from the release
dashboard: http://wiki.linaro.org/Cycles/1111/Release/Dashboard
--
David Zinman
Linaro Release Manager | Project Manager
Linaro.org | Open source software for ARM SoCs
Hi Angus & Grant,
Because the Linaro Android 11.11 release has been done successfully, I have
some time to continue to work on device tree topic, here is my blue print
for it:
https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-origen…
Therefore, I would like to know what I can do for this in the 11.12 cycle -
from now to the 18th December 2011. For Samsung Origen Android build, the
latest kernel version I got is still 3.0.4+, so I think there is no any
device tree stuff in it.
@Angus, Would you give me a brief about the device tree support status on
our current 3.0.4+ kernel? Will you upgrade it to the 3.1 in 11.12 cycle?
@Thomas, In this blue print:
https://blueprints.launchpad.net/linaro-android/+spec/linaro-platforms-lc4.…,
Tony mentioned that you has upstreamed the initial support for device tree.
However, it depends on the 3.1 kernel upgrade. I would like to know that is
there any possible that I can do something without the kernel upgrade?
I currently feel that this work highly depends on the outcome of landing
team and kernel group, so before I get something from them, I'm afraid that
I can't do any "real" work on this.
Thank you all for your help!
BR
Botao Sun
Hi All,
In ppa: tom-gall/packages I've published an updated version live-build
(version a40-1linaro10) for maverick, natty, oneiric, and precise.
This version of live-build includes the ability to cross build root
file systems with multistrap. As it turns out to cross build our
precise linaro images for nano and developer, one only needs to change
one parameter to enable cross builds.
The "beta" instructions are as follows:
1) add-apt-repository ppa:tom-gall/packages
2) apt-get update
3) apt-get install live-build
This will work for maverick, natty, oneiric and precise. It will
install version: ~a40-1linaro10
4) mkdir dirforbld ; cd dirforbld
5) bzr branch lp:~linaro-maintainers/linaro/live-helper.config.precise.nano
config
or bzr branch lp:~linaro-maintainers/linaro/live-helper.config.precise.developer
config
6) cp config/conf_create.sh .
7) edit conf_create.sh : change parameter to --bootstrap from
debootstrap to multistrap
8) add / remove packages listed in
config/package-lists/nano.chroot.list which is a text file. One
package per line.
9) sh ./conf_create.sh
10) lb build
11) When rebuilding use the command : lb clean --all ; lb clean
--cache; rm -rf .stage/* ; lb build
--
Regards,
Tom
"Where's the kaboom!? There was supposed to be an earth-shattering
kaboom!" Marvin Martian
Multimedia Tech Lead | Linaro.org │ Open source software for ARM SoCs
w) tom.gall att linaro.org
w) tom_gall att vnet.ibm.com
h) tom_gall att mac.com
Hi -
Alexander was asking how linaro-androidization-tracking is maintained
(hope you are feeling better Alexander).
I made a 90-slide presentation about it at the last Connect, you can
find the slides here
http://people.linaro.org/~andygreen/lttools-introduction.pdf
and the tools here
http://git.linaro.org/gitweb?p=people/andygreen/lt-tools.git;a=summary
In a nutshell common-3.0 from Google is a history tree, so detecting new
patches on there is clear enough. John Stultz saw it had come back
recently and dropped me a note it had been updated. I asked Jassi to
isolate the new patches and send them to me.
I use lt-tools to distribute any new patches between the topics, then
reapply it to my android-ready branch and confirm it builds and works
before pushing.
lt-tools also takes care of the tracking action, it's important
everything is on the same Linus HEAD basis so I routinely rebase
linaro-androidization-tracking along with my other tracking branches, as
of last week it's on 3.2-rc4.
Actually, l-a-t is low maintainence since it's far from every day new
patches are coming on common-3.0, and so far on 3.2 cycle there was no
serious uplevel conflict between the androidization patch load and Linus
HEAD changes.
If we have someone else now who wants to maintain it, I think that's
fine with the provisos we should maintain the topic structure and look
at further refactor there, and we need a new approach to deal with
rebase points that more than one tree can rendezvous at --->
Right now when my tracking branches are in as reasonable a shape on one
Linus HEAD basis as they will get, I randomly pull a new basis from what
happens to be on Linus' tree that moment, and rebase everything on my
side against that (including up until now l-a-t at the same time). That
won't really scale to other LTs and WGs all randomly sampling Linus HEAD
at different random points as their basis.
Scott mentioned that there's a desire to see more KWG content at least
on tracking, I think that's a great idea. One way to solve both those
problems would be to no longer have LTs base off Linus HEAD but from a
new tree which is Linus HEAD + "linux-linaro-tracking", as it were, with
these other topics already merged in. So long as this rebases against
Linus HEAD really often, like daily at least in the early -rcs, carrying
its topic content with it, and matching linaro-androidization-tracking
is available, that would be a good way for all the LT trees to both get
any Linaro-specific content and increase their chances of having a
common "rendezvous" basis where multiple LT trees can be bound together.
-Andy
--
Andy Green | TI 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
A request has been received to discontinue Linaro's support for the
Beagleboard and Beagleboard-xM hardware.
The following conditions will be applied for the 2012.01 release cycle:
* There will be no more LEB or Linaro Developer builds.
* No more testing will be applied by Linaro to the boards at all,
and no quality assurance will be performed.
* No more bugs will be filed against these boards assigned to
Linaro resources.
* All currently filed bugs will be re-targeted to the appropriate
community resource.
* Landing team support is no longer needed or expected.
* Linaro Release notes will no longer refer to Beagleboard.
--
David Zinman
Linaro Release Manager | Project Manager
Linaro.org | Open source software for ARM SoCs
Since there is code duplication in different mach-board.c file it is better
to set default clock rate of xusbxti clock in plat-s5p/clock.c file.
The patches are based on following commit on Kukjin's for-next branch.
Pankaj (1):
ARM: S5P: Set default rate of xusbxti clock
Pankaj Dubey (2):
ARM: EXYNOS: Removed code for setting clock rate of xusbxti
ARM: S5PV210: Removed code for setting clock rate of xusbxti
arch/arm/mach-exynos/mach-nuri.c | 1 -
arch/arm/mach-exynos/mach-origen.c | 1 -
arch/arm/mach-exynos/mach-smdk4x12.c | 2 --
arch/arm/mach-exynos/mach-smdkv310.c | 1 -
arch/arm/mach-s5pv210/mach-goni.c | 1 -
arch/arm/plat-s5p/clock.c | 1 +
6 files changed, 1 insertions(+), 6 deletions(-)
--
1.7.4.1