Hi,
As we come towards the end of the Linaro 11.05 cycle, Ubuntu is reaching
its release one month sooner. This provides unique challenges for our
Ubuntu-based images; Ubuntu LEB, developer, nano and ALIP. In order to
help alleviate any confusion surrounding freeze dates and archive uploads
the follow rules and dates apply:
2011-04-14 : The Ubuntu main archive and seeded packages are frozen.
Only important bug fixes will be allowed to packages that
are included in the Ubuntu images. Packages that are in
main, universe, multiverse, and overlays that are not part
of an Ubuntu image can continue to be uploaded.
2011-04-21 : Only Ubuntu release blocking bugs will be fixed from this
period onwards. Changes to non-seeded packages can
continue to be made as before.
2011-04-26 : Changes to unseeded universe and multiverse packages are
frozen. Changes to overlays can continue.
2011-04-28 : Ubuntu final release (Natty).
2011-04-29 : Changes to Natty archive packages can be made using the
natty-updates archive. Fixes first go into natty-proposed
and when tested and verified are uploaded to
natty-updates to be included in Linaro images. Both
natty-proposed and natty-updates are enabled on the
Linaro images for testing.
2011-05-19 : Linaro Release Candidate images are selected. All updates
to packages need to be tested and in the natty-updates
archive by this date. natty-proposed is disabled from the
images.
2011-05-21 : Linaro Release Candidate made. Only critical bug fixes
will be made from this period onwards using either the
natty-updates mechanism or overlays if no over solution
is available.
2011-05-28 : Linaro 11.05 final images released
This information is available on the Linaro wiki at:
http://wiki.linaro.org/Cycles/1105/Schedule
If you have further question please do not hesitate to get in contact.
Regards,
Jamie.
--
Linaro Release Manager | Platform Project Manager
Hi,
In the context of systemtap testsuite, I had some compilation issues
"invalid lvalue output in asm 1". I have root-caused that to code in
the tool that is a (old) duplicate of arch/arm/include/asm/uaccess.h
macro __put_user_asm_dword(x, __pu_addr, err) => 64bits storage.
__pu_addr is storage address
The xxx_byte/half/word versions are OK. The main difference is that
__pu_addr is only read while read and write in dword version (inline
assembly "+r" modifier)
#define __stp_put_user_asm_dword(x,__pu_addr,err) \
__asm__ __volatile__( \
"1: str " __reg_oper1 ", [%1], #4\n" \ ->
__pu_addr is read but also written for next operation
"2: str " __reg_oper0 ", [%1], #0\n" \
...
: "+r" (err), "+r" (__pu_addr) \ ->
"r" (__pu_addr) for other versions
: "r" (x), "i" (-EFAULT) \
: "cc")
As my knowledge of inline assembly is poor, I am checking if this
reminds anything to anyone (compilation option, out of date syntax,
...) before investigating deeper.
I have put most recent code version from kernel in the tool but still
it fails. However, looking again at kernel code while writing this
mail, macro may be used only if CONFIG_MMU is not defined. I will
cross-check tomorrow.
Regards
Fred
Hi Nicolas,
I could not find this changes in the latest 2.6.38 Linaro kernel. Please
merge the patch from the below
mentioned samsung maintainers next link as this is required for the PM
Linaro release.
Thanks,
Amit Daniel
On 5 April 2011 01:36, Amit Kachhap <amit.kachhap(a)linaro.org> wrote:
> Hi Nicolas,
>
> Please take this cpuidle commit from the samsung tree needed for Linaro new
> rebuilt tree.
>
>
> http://git.kernel.org/?p=linux/kernel/git/kgene/linux-samsung.git;a=commit;…
>
>
> Thanks,
> Amit Daniel
>
>
>
>
Hi all,
In the scope of my work on systemtap, I would like to have a look to
its user-space instrumentation capabilities. Systemtap relies on
uprobes+utrace for that purpose so has anyone some feedback/global
view on these with regards to ARM ?
utrace did not make it into the mainline and would need more to
convince Linux. I have also seen that a utraceless uprobe is emerging.
There is also a PPA with a utrace enabled kernel but this is not covering ARM.
I am in parallel seeking info on utrace-devel mailing list.
thanks for any help
Regards
Fred
hmm,
https://review.source.android.com/#change,22239
>From a quick look, it appears to be doing a similar thing as GEM..
although as a stand-alone driver rather than coupled with display
driver (drm).
BR,
-R
Hi Everyone,
The introduction to Linaro@UDS presentations will start tomorrow:
13 April 2011 4:00 UTC (For Asia, India and Australia timezones)
14 April 2011 15:00 UTC (For US and European timezones)
The meeting will be a brief presentation of these slides with a
question/answer session after:
https://docs.google.com/present/edit?id=0AdTXkLTDIrbnZGZnNTM0YmdfMjFmNDl0OW…
If you didn't receive an invite to one of the meetings and want
to attend, you can access the Linaro calendar and go to one of the
dates listed above then add your name to the invitees list.
If you can't see the Linaro calendar, just dial in to one of
the conference numbers listed below and use this access code:
23068 60813#
Canada 1 866 352 2710
Taiwan 0800 265 855
UK Freephone 0800 026 0166**
UK Local +44 207 630 2405
US Toll Free 1 866 352 2709
US Local +1 781 761 9450
Argentina 800 444 2926
Australia 1 800 700 575
Brazil 0800 881 0038
Chile 1 230 020 2450
China (North) 10 800 152 1873
China (South) 10 800 852 1873
Denmark 8040 4904
Finland 800 523 103
France 0 805 980 044
Germany 800 589 0993
Hungary 680 204 991
India 000 800 100 7944
Ireland 1800 719 827
Isle of Man 800 026 0216
Israel 1 809 452 928
Italy 800 089 718
Japan 2096 1857
Lithuania 880 073 532
Netherlands 800 020 5895
New Zealand 800 452 290
Peru 800 53115
Poland 800 331 1398
Russia 800 500 9237
Spain 900 900 867
Thailand 1 800 852 6026
Ukraine 880 050 1138
Cheers,
Matt
Enclosed you'll find a link to the agenda, minutes, actions and IRC logs
from the
Linaro kernel working group weekly meetings of April 11, 2011.
https://wiki.linaro.org/WorkingGroups/KernelConsolidation/Meetings/2011-04-…
== Summary ==
* ARM Programmer's guide
* ARM is sharing with us an early version of a book on ARM
architecture
* Needs feedback back to ARM from Linaro as an expert group on ARM
and opensource
* Send feedback to David Rusling and/or to Loic
* Validation: what the KWG would need in terms of validation for next
cycle
* Support for the desired monthly release. For instance, automated
builds & automated boot
* Automated builds and tests for tree merges.
* Wider testing than an individual can do by the validation group will
be helpful
* It would be very helpful if the test suite and boards were available
to anyone to test code changes
* TSC was OK with refusal to rewrite the smc driver.
* TR's for next cycle, seem we have more than we can handle in 6 months
* Unlikely to get to the low priority items and medium items are at risk
* Discussion about bug 664477, need more info how to reproduce it and owner
to handle and/or submit it upstream
Regards,
Mounir