RAG:
Red:
Amber:
Green: good progress on A15 vexpress system model
Current Milestones:
|| || Planned || Estimate || Actual ||
||cp15-rework || 2012-01-06 || 2012-02-20 || ||
||initial-a15-system-model || 2012-01-27 || 2012-01-27 || ||
||qemu-kvm-getting-started || 2012-03-04?|| 2012-03-04?|| ||
(for blueprint definitions: https://wiki.linaro.org/PeterMaydell/QemuKVM)
Historical Milestones:
||a15-usermode-support || 2011-11-10 || 2011-11-10 || 2011-10-27 ||
||upstream-omap3-cleanup || 2011-11-10 || 2011-12-15 || 2011-12-12 ||
== cp15-rework ==
* estimate shifted back since it turns out we can do something useful
in initial-a15-system-model without this as a prerequisite, so that's
a better order to do things in
== initial-a15-system-model ==
* I now have a working vexpress-a15 board model, and enough of the a15
private peripheral region and CPU definition that we can boot a
kernel compiled for A15-without-LPAE
* patchseries mostly looks ok to upstream but there are some loose ends
to fix up involving SMP secondary boot CPU protocol and making sure
the right one of the two graphics controllers gets to display things;
also it depends on some patches in the Calxeda/Samsung patchseries
== other ==
* patch review: Calxeda now basically ready to commit, another round
with Samsung
* made qemu-linaro 2012.01 release
* usual round of meetings etc
==Progress===
* Backported one part of the partial-partial PRE patch . Still looking into it.
* Investigate PR48308 - a bug where combine was generating incorrect
transformations.
* Reopened PR50313 - a bug which I originally thought was a dup of PR48308.
* Looked at upstream bugzilla for sometime and triaged a few bugs.
* Linaro patch review.
=== Plans ===
* Continue looking at partial-partial PRE and try and understand it further.
* Look at PR50313 further
* Upstream patch review.
* Finish submitting PGO patch and ABI tests patch
* Look at Andrew's patches for neon shifts -
Absences.
* Feb 6-10 : Linaro Connect Q1.12.
* Feb 13- 18 : Holiday.
==Progress===
* Short week - 4 days only after the bank holiday monday.
* Investigated PR48308 for a bit.
* Caught up with emails after vacation.
* Looked at fate an automatic tester for libav to validate my fixed
to fp conversions . Need to finish that off.
* 1 more bug with output_move_double ICE looked at briefly. Appears
to be memory corruption but valgrinding didn't find the issue.
Prioritizing PR48308 above this.
=== Plans ===
* Look at PR48308 a bit more seriously.
* Finish my long standing patches.
Absences.
* Feb 6-10 : Linaro Connect Q1.12.
* Feb 13- 18 : Holiday.
Amber noticed this on her Twitter feed: a L4 microkernel based
para-virtualisation that runs on the A9:
http://l4dev.org/
They're currently running the 11.12 LEB on a Versatile Express. The
project overview:
http://l4dev.org/codezero_overview
talks about their 'hyperswitch' method to reduce the
para-virtualisation overhead and reduce the number of changes to the
Linux kernel.
-- Michael
The GCC release tested up just fine. The branch is now open for commits.
The next release is Thursday the 9th of February. Note that this is
in the middle of Connect.
-- Michael
The Linaro Toolchain Working Group is pleased to announce the 2012.01
release of Linaro GCC 4.6 and Linaro GCC 4.5.
No changes were made in Linaro GDB this month and, as such, no release
has been made.
Linaro GCC 4.6 2012.01 is the eleventh release in the 4.6 series.
Based off the latest GCC 4.6.2+svn182894 release, it contains a few
bug fixes from over the Christmas break.
Interesting changes include:
* Updates to 4.6.2+svn182894
Fixes:
* PR51301 ICE in vectorised widening multiplies
* LP: #897583 Code generation bug with -O2 (-foptimize-sibling-calls)
* LP: #736661 armel FTBFS due to compiler ICE
Linaro GCC 4.5 2012.01 is the seventeenth release in the 4.5 series.
Interesting changes include:
* Updates to 4.5.3+svn182893
Fixes:
* LP: #736661 armel FTBFS due to compiler ICE
The source tarballs are available from:
https://launchpad.net/gcc-linaro/+milestone/4.6-2012.01https://launchpad.net/gcc-linaro/+milestone/4.5-2012.01
Downloads are available from the Linaro GCC page on Launchpad:
https://launchpad.net/gcc-linaro
More information on the features and issues are available from the
release page:
https://launchpad.net/gcc-linaro/4.6/4.6-2012.01https://launchpad.net/gcc-linaro/4.5/4.5-2012.01
Mailing list: http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Bugs: https://bugs.launchpad.net/gcc-linaro/
Questions? https://ask.linaro.org/
Interested in commercial support? inquire at support(a)linaro.org
-- Michael
The Linaro Toolchain Working Group is pleased to announce the
release of Linaro QEMU 2012.01.
Linaro QEMU 2012.01 is the latest monthly release of
qemu-linaro. Based off upstream (trunk) QEMU, it includes a
number of ARM-focused bug fixes and enhancements.
New in this month's release:
- Several bug fixes which reinstate support for running on ARM hosts
- Support for previously missing *xattr syscalls in usermode emulation
- A (dummy) model of the L2x0/PL310 L2 cache contrnoller (thanks to
Rob Herring and Mark Langsdorf of Calxeda)
Known issues:
- Graphics do not work for OMAP3 based models (beagle, overo)
with 11.10 Linaro images.
The source tarball is available at:
https://launchpad.net/qemu-linaro/+milestone/2012.01
More information on Linaro QEMU is available at:
https://launchpad.net/qemu-linaro
Hi Åsa. Well, the first proposals have arrived. I've cc'ed this to
linaro-toolchain so we have a record.
First, visit:
http://ex.seabright.co.nz/helpers/proposals
and see there are new merge requests from Ulrich with new results.
Next, login:
http://ex.seabright.co.nz/helpers/login
Your login is your Launchpad OpenID login "https://launchpad.net/~asa-sandahl"
After logging in, go back to the proposals page.
See that the fwprop-subreg merge request has a i686 and x86_64 result.
The i686 one is fine so click 'Record' and follow your nose. The
x86_64 is interesting - the fault might be real. Click 'Record'.
Note the subject line has 'regressed' in it. Ulrich will have to
investigate.
The lp-879725 results look fine so record both of those. Scanning
down the page shows that everything else is recorded so you're done!
The tool is a bit slow so don't be surprised if an operation takes ~10
s. The tool is backed by a cache so you won't see the results for ~2
hours.
-- Michael
Hi Michael,
I can't remember if I told you before, but I shall be away at the
CodeSourcery (Ok, Mentor Graphics's ESD TOOLS) annual meeting most of
next week.
I ought to be back at work on Friday. In the meantime I shall be reading
email, but not spending much time on Linaro work.
I can probably still get the GCC release process done, but if you'd
prefer Ramana did it this month then that's fine with me.
Andrew