Linaro 11.05 weekly testing 2011-05-05
Hi, This is a message sent out once per week to call on our community to help test the Linaro evaluation builds we produce. If you have supported hardware, as found on: http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/ please help our initiative by testing the official Linaro Evaluation Build (LEB): Ubuntu Desktop: http://snapshots.linaro.org/11.05-daily/linaro-ubuntu-desktop/ and our Community images: Nano: http://snapshots.linaro.org/11.05-daily/linaro-nano/ ALIP: http://snapshots.linaro.org/11.05-daily/linaro-alip/ Developer Tools: http://snapshots.linaro.org/11.05-daily/linaro-developer/ Make your way to: http://wiki.linaro.org/Releases/DailyBuilds for an explanation on how to test and submit your results to the QA tracker at: http://qatracker.linaro.org For an explanation of how to use the qatracker please see: https://wiki.linaro.org/QA/QATracker Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 11.05 Beta-2 released
Hi, The Linaro team is pleased to announce the availability of the 11.05 Beta-2 images. These are still early developer images but we encourage all with supported hardware to use and test them by downloading from: http://releases.linaro.org/platform/linaro-n/ Highlights of this release include: * This milestone includes a first release of the Linaro Android evaluation images for Beagle XM and Panda. * Efforts from the Android team include: * Generic AOSP builds with Linaro components. * The Linaro Android 2.6.38 kernel. * Toolchain packages based on Linaro toolchain release of March. Initial benchmarks for this toolchain can be found at https://wiki.linaro.org/JimHuang/Sandbox/LinaroToolchainAndroidBenchmarking * An Android platform code branch for direct evaluation of the Linaro toolchain. * Initial low hanging fruit optimisations; integrated and upstreamed to AOSP (16 patch sets currently). * Mouse support for developer convenience on the Panda image. * The 0xBenchmark package comes pre-integrated into the builds for benchmarking and demos. * Four images based on Ubuntu 11.04 including ubuntu-desktop, nano, developer and ALIP. * linaro-image-tools support for installing Android images on an SDcard * Support for 11 different developer boards including the newly added Freescale iMX53 LoCo board. Using the Android-based images = The Android-based images come in three parts, system, userdata and boot. These need to be combined to form a complete Android install. For an explanation of how to do this please see: https://wiki.linaro.org/Platform/Android/InstallImages If you are interested in getting the source and building these images yourself please see the following pages: https://wiki.linaro.org/Platform/Android/GetSource https://wiki.linaro.org/Platform/Android/BuildSource Using the Ubuntu-based images = The Ubuntu-based images consist of two parts. A hardware pack which can be found under the ./hwpacks directory which contains hardware specific packages such as the kernel and bootloader. The second part is the roofs which is combined with the hardware pack to create a complete image. For information on how to create an image please see: http://wiki.linaro.org/Releases/MilestoneBuilds Comparisons === A comparison of packages from the ubuntu-desktop beta and beta2 images can be found at: http://people.linaro.org/~jamiebennett/comparisons/comparisons-linaro-11.05-beta-beta2.html Getting involved More information on Linaro in general and the 11.05 plans can be found at: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org * 11.05: http://wiki.linaro.org/Releases/1105 Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.linaro.org or irc.freenode.net #linaro-android irc.linaro.org or irc.freenode.net Issues with this release For any errata issues please see: http://wiki.linaro.org/Releases/1105/Beta2#Issues Bug reports for this release should be filed in Launchpad against the individual packages that are affected, if a suitable package cannot be identified, feel free to assign them to: http://www.launchpad.net/linaro Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Call for testing: Linaro 11.05 Beta-2 Candidate
Hi, In preparation for the release of Linaro 11.05 Beta-2 images on Thursday a suitable candidate has been selected for testing. The Beta-2 release is expected to be tested heavily and provide the most stable and feature-rich images to date this cycle. If you have supported hardware, as found at: http://releases.linaro.org/platform/linaro-n/hwpacks/latest/ please help our initiative by testing the official Linaro Evaluation Build (LEB): Ubuntu Desktop: http://releases.linaro.org/platform/linaro-n/ubuntu-desktop/latest/ and our Developer images: Nano: http://releases.linaro.org/platform/linaro-n/nano/latest/ ALIP: http://releases.linaro.org/platform/linaro-n/alip/latest/ Developer Tools: http://releases.linaro.org/platform/linaro-n/developer/latest/ As a side note, hwpacks that have an -lt- in their name are outputs from the Linaro Landing teams, using some of their components. Make your way to: http://wiki.linaro.org/Releases/MilestoneBuilds for an explanation of how to test and submit your results to the QA tracker at: http://qatracker.linaro.org For an explanation of how to use the qatracker please see: https://wiki.linaro.org/QA/QATracker Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 11.05 Beta-2
Hi, Currently there is no Ubuntu-based milestone image release between the Beta (2011-03-31) and Release Candidate (2011-05-21); this is a period of 51 days. In a fast moving project like Linaro, a lot can happen in 51 days. With this in mind and to help focus our testing initiative before RC the decision has been made to introduce a Linaro 11.05 Beta-2 milestone. The Beta-2 milestone will take advantage of the fact that the Ubuntu final release happens on 2011-04-28. Linaro 11.05 Beta-2 will be released on the same day, exactly one month before final and will incorporate all the Ubuntu final goodness. It is expected that this milestone will have the greatest test coverage, both manual and automated, of any release so far and will be a dry-run of what is expected in the run up to final release. On 2011-04-26 the Beta-2 candidate images will be selected and http://qatracker.linaro.org set up accordingly. If you have the appropriate hardware please help to test the images and report your results to qatracker using the instructions at: https://wiki.linaro.org/QA/QATracker An announcement will be made on 2011-04-26 to declare the images ready for consumption. Happy Testing ! Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 11.05 weekly image testing 2011-04-14
Hi, This is a message sent out once per week to call on our community to help test the Linaro evaluation builds we produce. If you have supported hardware, as found on: http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/ please help our initiative by testing the official Linaro Evaluation Build (LEB): Ubuntu Desktop: http://snapshots.linaro.org/11.05-daily/linaro-ubuntu-desktop/ and our Community images: Nano: http://snapshots.linaro.org/11.05-daily/linaro-nano/ ALIP: http://snapshots.linaro.org/11.05-daily/linaro-alip/ Developer Tools: http://snapshots.linaro.org/11.05-daily/linaro-developer/ Make your way to: http://wiki.linaro.org/Releases/DailyBuilds for an explanation on how to test and submit your results to the QA tracker at: http://qatracker.linaro.org For an explanation of how to use the qatracker please see: https://wiki.linaro.org/QA/QATracker Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Freeze dates and package changes for Linaro's Ubuntu-based images
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 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Release critical and important bugs
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 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 11.05 weekly image testing 2011-04-07
Hi, This is a message sent out once per week to call on our community to help test the Linaro evaluation builds we produce. If you have supported hardware, as found on: http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/ please help our initiative by testing the official Linaro Evaluation Build (LEB): Ubuntu Desktop: http://snapshots.linaro.org/11.05-daily/linaro-ubuntu-desktop/ and our Community images: Nano: http://snapshots.linaro.org/11.05-daily/linaro-nano/ ALIP: http://snapshots.linaro.org/11.05-daily/linaro-alip/ Developer Tools: http://snapshots.linaro.org/11.05-daily/linaro-developer/ Make your way to: http://wiki.linaro.org/Releases/DailyBuilds for an explanation on how to test and submit your results to the QA tracker at: http://qatracker.linaro.org For an explanation of how to use the qatracker please see: https://wiki.linaro.org/QA/QATracker Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[REMINDER] Weekly Release meeting 2011-04-07
Hi, The weekly Linaro Release Meeting will be held at 16:00 UTC today The agenda for the meeting can be found at: https://wiki.linaro.org/Cycles/WeeklyReleaseMeeting/2011-04-07 and previous action items were: * tgall_foo to try the methods outlined in 74 for fixing audio * mounir to ping arndb on 673820 If you have points to raise or bugs that need to be discussed please add them to the wiki page above. Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[NOTES] Android Platform team meeting 2011-04-06
Hi, The notes and actions for this weeks Android Platform Team meeting along with team activity reports are now available at: https://wiki.linaro.org/Platform/Android/Meetings/2011-04-06 = Actions Recorded = * asac to invite TI to Android weekly meeting * asac to chase TI on the mm bits * jim to create a the panda-gfx-integration-initial blueprint * Team to review what they are working on and document what isn't approved/doesn't have a Blueprint/is not targeted to discuss in next weeks meeting * patrikryd to try to push generic hook patch to upstream and see what happens * jserv-- to send email to android-platform telling folks about our toolchain package!! (marketing) and pointing out the build failures we get in platform and asking whether they want contributions to fix them properly * patrikryd to fill out summary on https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-platform-kernel-boottarball * patrikryd to fix work item syntax on https://blueprints.launchpad.net/linaro-android/+spec/linaro-android-platform-kernel-boottarball * asac and JamieBennett to talk to james_w about keeping android blueprints on android team radar * jeremy to add a more verbose summary to linaro-android-benchmark-suite-integration-into-lava and poke asac/jamie for approving * luse to fix work items and get linaro-android-toolchain-benchmark to approved state * luse/jserv-- to draft a new blueprint that is about integrating the google benchmarks itself this blueprint would come before linaro-android-toolchain-benchmark * asac to think about validation meta blueprint and what to do with that with jamie and jeremychang * jserv-- to fix linaro-android-toolchain-ndk WI syntax * patrik to add l-m-c update WI to boottarball spec and assgn that WI to jeremy; also add verification WI owned by him to test the complete "solution" * JamieBennett get the bug bot in here finally * JamieBennett to hunt down infrastructure projects and ensure they are properly covered by android team including bug driver powers etc. * patrikryd to sort out href8500 build situation Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 11.05 Beta Ubuntu images released
Hi, Linaro is pleased to announce that the 11.05 Beta Ubuntu images are now available to download. After much blood, sweat and tears we now have a total of 10 different boards supported (in our own unique hardware pack and board-neutral rootfs architecture) along with a more focused 4 different images to try out including the much coveted Ubuntu Unity interface on the Ubuntu Desktop image. This is in addition to the small nano image, the tools rich Developer image and the ARM Internet Platform (ALIP) image. A 2.6.38 kernel, state-of-the-art Linaro toolchain and a whole host of ARM-related improvements make for a thrilling release. What are you waiting for, go download it now! As always, if you have supported hardware, as found on: http://releases.linaro.org/platform/linaro-n/hwpacks/beta/ please help our initiative by testing the official Linaro Evaluation Build (LEB): Ubuntu Desktop: http://releases.linaro.org/platform/linaro-n/ubuntu-desktop/beta/ and our Developer images: Nano: http://releases.linaro.org/platform/linaro-n/nano/beta/ ALIP: http://releases.linaro.org/platform/linaro-n/alip/beta/ Developer Tools: http://releases.linaro.org/platform/linaro-n/developer/beta/ As a side note, hwpacks that have an -lt- in their name are outputs from the Linaro Landing teams, using some of their components. Make your way to: http://wiki.linaro.org/Releases/MilestoneBuilds for an explanation on how to test and submit your results to the QA tracker at: http://qatracker.linaro.org For an explanation of how to use the qatracker please see: https://wiki.linaro.org/QA/QATracker Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[REMINDER] Weekly Release meeting 2011-03-31
Hi, The weekly Linaro Release Meeting will be held at 16:00 UTC tomorrow (please note the change in time). The agenda for the meeting can be found at: https://wiki.linaro.org/Cycles/WeeklyReleaseMeeting/2011-03-31 and previous action items were: * JamieBennett to look into EDID support status If you have points to raise or bugs that need to be discussed please add them to the wiki page above. Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Call for testing: Linaro 11.05 Beta Candidate
Hi, In preparation for the release of Linaro 11.05 Beta images on Thursday a suitable candidate has been selected for testing. If you have supported hardware, as found on: http://releases.linaro.org/platform/linaro-n/hwpacks/beta/ please help our initiative by testing the official Linaro Evaluation Build (LEB): Ubuntu Desktop: http://releases.linaro.org/platform/linaro-n/ubuntu-desktop/beta/ and our Developer images: Nano: http://releases.linaro.org/platform/linaro-n/nano/beta/ ALIP: http://releases.linaro.org/platform/linaro-n/alip/beta/ Developer Tools: http://releases.linaro.org/platform/linaro-n/developer/beta/ As a side note, hwpacks that have an -lt- in their name are outputs from the Linaro Landing teams, using some of their components. Make your way to: http://wiki.linaro.org/Releases/MilestoneBuilds for an explanation on how to test and submit your results to the QA tracker at: http://qatracker.linaro.org For an explanation of how to use the qatracker please see: https://wiki.linaro.org/QA/QATracker Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Notice: Releases to Cycles
On 28 Mar 2011, at 15:43, Matt Waddel wrote: > Hi Dave, > > On 03/28/2011 07:34 AM, Dave Martin wrote: >> On Fri, Mar 25, 2011 at 6:20 PM, Joey Stanford >> wrote: >>> Hi, >>> >>> Kiko requested that we mass rename Releases to Cycles. This makes >>> sense since a release is a point in time event and we operate under a >>> larger cycle. >>> >>> This is now done and a redirect has been put into place. As you see >>> references which are incorrect in wiki pages, please consider doing >>> some drive-by clean-up/gardening. >> >> Hi there... >> >> Some of the milestone builds page seems to have gone missing... >> >> https://wiki.linaro.org/Cycles/MilestoneBuilds >> >> This could be due to a dangling reference -- I've not investigated in >> more depth. The page as it now appears isn't enough to explain to >> someone how to use our deliverables, though. > > This is fixed now. Thanks for pointing it out. Theres lots of other breakage including each Meeting notes page which will need renaming and the links on every page (at the top) changed. > --Matt Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro Ubuntu 11.05 Beta Freeze tomorrow
Hi, >From tomorrow the Beta Freeze restriction comes into effect for all packages that are in the Ubuntu main archive. This means that all uploads to the main archive will need to be manually approved by the Linaro and Ubuntu release teams as we prepare for Beta release. For an explanation of what the Beta Freeze is and how to get your changes into the archive from tomorrow onwards please see: http://wiki.linaro.org/Releases/BetaFreeze Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[NOTES] Infrastructure team meeting 2011-03-22
Hi, The notes and actions for this weeks Infrastructure team meeting along with team activity reports are now available at: https://wiki.linaro.org/Platform/Infrastructure/Meetings/2011-03-22 = Actions Recorded = * Salgado to review Android build system code Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[NOTES] Android Platform Team meeting 2011-03-23
Hi, The notes and actions for this weeks Android Platform Team meeting along with team activity reports are now available at: https://wiki.linaro.org/Platform/Android/Meetings/2011-03-23 == Actions Recorded == * jserv-- to document the linaro-android with framebuffer only investigations on the wiki * jserv-- to document the "linaro-android without GFX and use framebuffer only" investigations on the wiki * asac to review the Blueprint list at https://blueprints.launchpad.net/linaro-android and give feedback * JamieBennett to setup status.linaro.org for the Android team * asac to try android beagle on .38 kernel * patrikryd to push one safe gcc patch and see what happens * asac and jeremychang to talk through the lmc details and get this in today * jeremychang to try the 2.6.38 tree from jstultz * patrikryd to chase up Google contribution agreement Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[REMINDER] Weekly Release Meeting 2011-03-24
Hi, The weekly Linaro Release Meeting will be held at 17:00 UTC tomorrow. The agenda for the meeting can be found at: https://wiki.linaro.org/Releases/WeeklyReleaseMeeting/2011-03-24 and previous action items were: * JesseBarker to test gfx image and report back his findings to tgall_foo, slangasek and JamieBennett * JamieBennett to delete -rc images from releases.linaro.org If you have points to raise or bugs that need to be discussed please add them to the wiki page above. This meeting is for everyone to discuss issues that may affect the ability to showcase Linaro's efforts in the released images so please add anything to the agenda that you feel falls into this category. The full agenda is: * Announcements - Jamie Bennett with time for others to announce * Action Item Review - Jamie Bennett chasing * Image Status - Tom Gall and Patrik Ryd * Bugs - Jamie Bennett chair, others discuss * Team release-related reports (any team-focused release topics) * Any Other Business (AOB) Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[REPORT] 2011-03-17 Infrastructure team weekly report
Hi, The Infrastructure team weekly report for 2011-03-17 is now available and can be found at: https://wiki.linaro.org/Platform/Infrastructure/Status/2011-03-17 The report is also reproduced in full below. Regards, Jamie. -- Linaro Release Manager | Platform Project Manager -- * Period: (20110310-20110316) * PM: JamieBennett * Past reports : https://wiki.linaro.org/Platform/Infrastructure/Status * Burndown information : http://status.linaro.org/linaro-infrastructure.html * Stakeholder process: https://wiki.linaro.org/Platform/Infrastructure/CurrentProjects == Key Points for wider discussion == * A blog aggregator instance has been setup at planet.linaro.org, please take a look. * https://android-build.linaro.org/ is now feature complete and can be used by the Android team for requesting builds. == Team Highlights == * Initial investigations into how the Infrastructure team could help on the Validation LAVA scheduler have happened. No decision has been made to commit resources to this project at this time. * Work continues on svammel as fixes and functionality go into the branch. Some reviews and feedback have been given by the Developer Platform team. * The continuous integration work saw its first deployment on EC2 as Jenkins was installed and configured. More work is needed before this is useful. * Work on http://status.linaro.org is ramping down with a couple of fixes being worked on this week. == Upcoming Deliverables == * linaro-image-tools will be getting a release soon (likely before the monthly release date to ease the process of getting it in to Ubuntu) * Final patch metrics for the next member report. == Risks / Issues == * '''VERY HIGH IMPACT''': Mattias unable to work productively due to IT restrictions in ST-E (6 weeks): some progress. Has process now to request changes, but little response to his requests in more than 4 weeks. Mattias is working from home or over 3G in the meantime. * '''HIGH IMPACT''': PatchTracking requires deploying Patchwork (5 weeks): Discussion with IS, and it is not expected to take them long to do once they get to it. They have indicated that they may be able to start at the end of this week, or in the week after. * '''HIGH IMPACT''': Gerrit instance needed for Android (5 weeks): Co-ordination with IS has started. Waiting to hear from them if we can get it this month, and what we need to do to help with that. * '''MEDIUM IMPACT''': Deepti lacking hardware to work with her Panda board: Deepti has received the Panda board, but doesn't have a USB->serial cable for it, so is still unable to use it for much. Working on tasks that don't require it, but unable to participate in image testing. (many weeks). * '''MEDIUM IMPACT''': OurOwnOffspring is still being setup (many weeks) * '''MEDIUM IMPACT''': Want a Jenkins/Hudson instance for Continuous Integration purposes (many weeks): Discussions with IS, and they will provide one, but timeframe is unclear at this point. Will host ourselves until IS can provide. Work on an ec2 instance for this has started, and should be completed soon. * '''MEDIUM IMPACT''': Deepti and Avik are sharing one Panda board meaning some hardware specific work is being blocked (2 weeks). == Miscellaneous == * Guilherme at PyCon 10-15 March * James away 21st March ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[REPORT] 2011-03-17 Validation team weekly report
Hi, The Validation team weekly report for 2011-03-17 is now available and can be found at: https://wiki.linaro.org/Platform/Validation/Status/2011-03-17 The report is also reproduced in full below. Regards, Jamie. -- Linaro Release Manager | Platform Project Manager -- * Period: (20110310-20110316) * PM: JamieBennett * Past reports : https://wiki.linaro.org/Platform/Validation/Status * Burndown information : http://status.linaro.org/linaro-validation.html == Key Points for wider discussion == * Please take a look at http://validation.linaro.org/launch-control/ and give feedback. == Team Highlights == * launch-control 0.3 release candidate 3 was deployed on validation.linaro.org (http://validation.linaro.org/launch-control/). * QEMU continuous integration testing now boots some known-good test images every time there is a commit and a new build of QEMU in Jenkins. * Initial work on power management tests in abrek has begun. More discussions about next steps for those tests is underway. * Investigations into how to build and test android images in the validation farm are underway. Some modification of the master image is needed but the partitioning layout for Android is causing problems. == Upcoming Deliverables == * dashboard.linaro.org upgrade to 0.3. == Risks / Issues == * '''HIGH IMPACT''': The validation scheduler Blueprint continues to lag behind with 37 work items to complete (none completed so far) - https://launchpad.net/lava/+spec/linaro-n-validation-scheduler (several weeks). Discussions are on going to find a way to unblock this project. == Miscellaneous == * None. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[REPORT] 2011-03-17 Android team weekly report
Hi, The Android team weekly report for 2011-03-17 is now available and can be found at: https://wiki.linaro.org/Platform/Android/Status/2011-03-17 The report is also reproduced in full below. Regards, Jamie. -- Linaro Release Manager | Platform Project Manager -- * Period: (20110310-20110316) * PM: JamieBennett * Past reports : https://wiki.linaro.org/Platform/Android/Status == Key Points for wider discussion == * Are there Android related requirements from the Landing and Working Group teams for next cycle? == Team Highlights == * Noritsuna demonstrated a linaro-android powered robot. A video of it in action can be see at: http://www.youtube.com/watch?v=8EgfAk5RBVo * More details on the robot can be found at: http://www.siprop.org/ja/2.0/index.php?product/AutoChasingTurtle * Most of the Android related Blueprints were triaged and split up where necessary. A full list can be found at: https://blueprints.launchpad.net/linaro-android * Some benchmarking of Linaro GCC 4.5 with Android has been done with positive results. The full results can be found at: https://wiki.linaro.org/Platform/Android/Toolchain * The Linaro Evaluation Build of Android now fully supports the Beagle XM platform. More work is being done for the ST-E U8500 and TI Panda boards. * Work on the toolchain build system based on Googles own continues. Bug:731477 was fixed and code pushed upstream at https://review.source.android.com//#change,21761 * The consolidation of common code is being reviewed. Jeremy Chang sent several patches to the linaro-dev list which are now being merged. == Upcoming Deliverables == * None. == Risks / Issues == * '''HIGH IMPACT''': The recent earthquake and Tsunami in Japan has meant that work has stalled for some of the engineers. All are reported to be OK but KJ-nabe & An were worst affected as their company premises were badly hit. They may not be back for a couple of months (1 week). * '''HIGH IMPACT''': Currently the Linaro Android efforts are based on 2.6.37 but with Linaro moving to 2.6.38 and the upstream Android 2.6.38 kernel being available some rebasing efforts will be needed. John Stultz, Patrik Ryd and others need to discuss how this can be done in the smoothest way (4 weeks). Some amount of effort will be needed but that effort is unclear at this point. Will lower level after initial investigations if necessary. Investigations have started. * '''MEDIUM IMPACT''': Contribution agreements with Google for AOSP development still waiting to be approved for Alexander Sack and Patrik Ryd (2 weeks). * '''MEDIUM IMPACT''': Patrik’s Panda board is lost in the postal system atm. Sent by Mounir from IBM, Patrik is chasing tracking numbers (2 weeks). == Miscellaneous == * Wiki pages of note this week: * https://wiki.linaro.org/Platform/Android/Toolchain * http://wiki.linaro.org/Platform/Android/UpstreamNDK * https://wiki.linaro.org/Platform/Android/UpstreamToolchain ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[REPORT] 2011-03-17 Developer Platform team weekly report
Hi, The Developer Platform team weekly report for 2011-03-17 is now available and can be found at: https://wiki.linaro.org/Platform/DevPlatform/Status/2011-03-17 The report is also reproduced in full below. Regards, Jamie. -- Linaro Release Manager | Platform Project Manager -- * Period: (20110310-20110316) * PM: JamieBennett * Past reports : https://wiki.linaro.org/Platform/DevPlatform/Status * Burndown information : http://status.linaro.org/linaro-foundations.html == Key Points for wider discussion == * lttng changes to the kernel currently break OMAP4, a fix is needed soon. == Team Highlights == * lttng has been packaged into the kernel tree. It is reported working on on i.MX51 and OMAP3 but fails on OMAP4, in fact it breaks OMAP4 even when not enabled. Avik Sil is investigating. * Temporary 2.6.38 kernel has been created as John Rigby stages some changes before they go into Nicolas' tree. This can be found at: http://git.linaro.org/gitweb?p=people/jcrigby/linux-linaro-2.6.38-alt.git;a=summary * Support for the ST-E U8500 HREF board has been enabled in u-boot-linaro-next. After a round of feedback from the ST-E Landing Team this work will be pushed upstream. * linaro-graphical-engineering and linaro-multimedia-engineering are being built again. * Work continues on xdeb with some dependency graphing issues fixed. * Cross-toolchain glibc patches sent to the debian-glibc mailing list for review. * Initial multiarch support has landed in the Ubuntu archive. /lib/libc.so.6 is no more! dpkg, apt, gcc, eglibc, debhelper, pkg-config, cdbs all got pushed. * The latest upstream branch of ltrace has been merged into ubuntu/natty/ltrace to enable Thumb-2 support. == Upcoming Deliverables == * Beta Freeze 2011-03-24 * New build of Linaro Linux kernel * systemtap v1.3 + cherry-picked fixes * apt fixes to Ubuntu * New dpkg to Ubuntu that implements support for the final multi-arch library paths == Risks / Issues == * '''MEDIUM IMPACT''': Peter Pearce reports that bootstrapping & making cross-compile patches upstreamable are slowing the rate of package fixing. The (current) alip package list will not be complete for beta freeze * '''LOW IMPACT''': Multiarch has broken a few unexpected packages such as cmake, apt and linaro-image-tools. These are being worked on. * '''LOW IMPACT''': There is not much manual test coverage for U8500, Samsung Orion, iGEPv2, iMX51, Overo hardware. == Miscellaneous == * None. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 11.05 weekly testing 2011-03-17
Hi, This is a message sent out once per week to call on our community to help test the Linaro evaluation builds we produce. If you have supported hardware, as found on: http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/ please help our initiative by testing the official Linaro Evaluation Build (LEB): Ubuntu Desktop: http://snapshots.linaro.org/11.05-daily/linaro-ubuntu-desktop/ and our Community images: Nano: http://snapshots.linaro.org/11.05-daily/linaro-nano/ ALIP: http://snapshots.linaro.org/11.05-daily/linaro-alip/ Developer Tools: http://snapshots.linaro.org/11.05-daily/linaro-developer/ Make your way to: http://wiki.linaro.org/Releases/DailyBuilds for an explanation on how to test and submit your results to the QA tracker at: http://qatracker.linaro.org For an explanation of how to use the qatracker please see: https://wiki.linaro.org/QA/QATracker Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [PATCH-Android] [android/external/elfcopy] Modified to eliminate build errors using GCC 4.5/4.6.
On 16/03/11 at 05:31pm, Sachin Kamat wrote: > Hi Arnd, Alexander, > > Some of the work arounds are just make shift solutions so that those > dependent on the build can carry on with their work. > Meanwhile as you guys said, the underlying problem needs to be addressed and > fixed. This might take a while. Maybe a comment just above each of these 'make shift solutions' will help you a) locate them later to fix up and b) give commentary on why you are temporarily doing them. > Regards > Sachin Regards, Jamie. > On 16 March 2011 17:17, Arnd Bergmann wrote: > > > On Wednesday 16 March 2011, Sachin Kamat wrote: > > > --- a/elfcopy.c > > > +++ b/elfcopy.c > > > @@ -2456,7 +2456,6 @@ update_symbol_values(Elf *elf, GElf_Ehdr *ehdr, > > > out why and also figure out whether the zero > > value should have > > > been adjusted, after all. > > > */ > > > -ASSERT(!(shdr_info[sym->st_shndx].shdr.sh_flags > > & SHF_ALLOC)); > > > ASSERT(shdr_info[i].shdr.sh_type == SHT_SYMTAB); > > > } > > > > Like the -Werror changes that Alexander commented on, this change > > circumvents the error output, but does not address the underlying > > problem. If you remove an assertion, that at least needs a very > > good explanation why the assertion was incorrect in the first > > place. > > > >Arnd > > > > > > -- > With warm regards, > Sachin > ___ > linaro-dev mailing list > linaro-dev@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-dev ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [PATCH 2/2 android/device/linaro/common] mount mmc partitions instead of mtd partitions
On 14/03/11 at 10:28am, Paul Larson wrote: > On Mon, Mar 14, 2011 at 9:37 AM, Jeremy Chang wrote: > > > +# mount mmc partitions > > +mount ext4 mmc@blk0p3 /system > > +mount ext4 mmc@blk0p3 /system ro remount > > +mount ext4 mmc@blk0p5 /cache > > +mount ext4 mmc@blk0p6 /data > > +mount ext4 mmc@blk0p7 /sdcard > > > > In my understanding, this will require a very particular sd card partition > layout, which seems to use quite a few partitions. Is this documented > somewhere? I'm trying to think about whether it will be possible to make > this coexist with Linaro image testing in our validation environment where > we currently have 2 partitions for booting a master image, and two > partitions for booting a new linaro image we wish to test. The partition layout is described at: https://wiki.linaro.org/Platform/Android/DevBoards > Thanks, > Paul Larson Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[REPORT] 2011-03-10 Validation team weekly report
Hi, The Validation team weekly report for 2011-03-10 is now available and can be found at: https://wiki.linaro.org/Platform/Validation/Status/2011-03-10 The report is also reproduced in full below. Regards, Jamie. -- Linaro Release Manager | Platform Project Manager -- * Period: (20110302-20110309) * PM: JamieBennett * Past reports : https://wiki.linaro.org/Platform/Validation/Status * Burndown information : http://status.linaro.org/linaro-validation.html == Key Points for wider discussion == * A request for comments on the Debian Django packaging guide has been made. Please read and give comments on: http://wiki.debian.org/DjangoPackagingDraft. * Power Management tests are planned to be integrated into the test suite and visualisation tools. The best way to do this is under discussion and the team invites more comments. == Team Highlights == * The Django packaging guideline for Debian was produced and is available at http://wiki.debian.org/DjangoPackagingDraft. There are discussions ongoing on the debian-python mailing list for feedback. * A first (and second) release of the django-debian package was made for connecting django database settings to dbconfig-common. This is being used on the LAVA project for database integration. * Initial discussions have been made to integrate some of the work the Power Management Working Group is doing in to abrek (the test-suite framework) and launch-control (the test visualisation tool). The ability to automatically test and visualise the power consumption on boards will take the Validation team around 2-4 weeks to complete. * Work continues on LAVA with two new branches containing improvements done this week. * abrek gained the ability to save bundles at the end of a test run. == Upcoming Deliverables == * launch-control 0.3c2 deployed on validation.linaro.org == Risks / Issues == * '''HIGH IMPACT''': Zygmunt's Beagle Board C4 appears to have hardware issues (1 week). * '''HIGH IMPACT''': The validation scheduler Blueprint continues to lag behind with 37 work items to complete (none completed so far) - https://launchpad.net/lava/+spec/linaro-n-validation-scheduler (several weeks). Discussions are on going to find a way to unblock this project. == Miscellaneous == * Wiki pages of note this week: * http://wiki.debian.org/DjangoPackagingDraft ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[REPORT] 2011-03-10 Developer Platform team weekly report
Hi, The Developer Platform team weekly report for 2011-03-10 is now available and can be found at: https://wiki.linaro.org/Platform/DevPlatform/Status/2011-03-10 The report is also reproduced in full below. Regards, Jamie. -- Linaro Release Manager | Platform Project Manager -- * Period: (20110303-20110309) * PM: JamieBennett * Past reports : https://wiki.linaro.org/Platform/DevPlatform/Status * Burndown information : http://status.linaro.org/linaro-foundations.html == Key Points for wider discussion == * The process to produce and upstream ALIP cross-compile fixes is slow, what can we do to speed this up? * Multi-arch changes are still landing to the Ubuntu archive, lots of testing is needed here. * Panda display issues are now resolved so more testing of images on the Panda board is possible. * The Nano image needs to be slimmed down further. Tom has proposed some changes but others need to review and comment on them. == Team Highlights == * LTTng 0.245 has been ported to the linux-linaro-2.6.38 kernel. The changes are available at: http://git.linaro.org/gitweb?p=people/aviksil/linux-2.6-lttng-linaro.git;a=summary * Work continues on parts of kdelibs with the GL dependency removed from libplasma and kdebase-window-manager updated. * After many investigations the Panda non-display issue (bug:728603) has a fix. A config option change will enable the display to work with a knock-on effect of other bugs such as bug:720055 also being resolved. * A thumb2 enabled kernel build has been turned on after work by both the Kernel Working Group and the Developer Platform team. * Linaro's smallest full image, Nano, got reduced in size to 125mb installed. Proposed changes to eventually get closer to the 64mb installed target are currently in discussion. * libjpeg-turbo got further work this week as lintian errors were fixed. * Several more packages have been fixed for cross-compilation in the Ubuntu archive. * dpkg support for multiarch library installation is in the Ubuntu archive but needs another upload due to changes in the planned dpkg database format. There has also been some patches submitted to apt for the major multiarch blocker bugs as the team continue towards a true multi-arch solution. * Cross toolchain packages got reuploaded to the archive fixing recent issues. == Upcoming Deliverables == * Beta Freeze 2011-03-24 * New build of Linaro Linux kernel * systemtap v1.3 + cherry-picked fixes * apt fixes to Ubuntu * New dpkg to Ubuntu that implements support for the final multi-arch library paths == Risks / Issues == * '''MEDIUM IMPACT''': Peter Pearce reports that bootstrapping & making cross-compile patches upstreamable are slowing the rate of package fixing. The (current) alip package list will not be complete for beta freeze. * '''LOW IMPACT''': All multiarch work is landing past feature-freeze. Requires exception approval from the Ubuntu and Linaro release teams. == Miscellaneous == * Wiki pages of note this week: * http://wiki.debian.org/DebianBootstrap * https://wiki.linaro.org/Chromiumos/ChromeosWm ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 11.05 weekly testing 2011-03-10
Hi, This is a message sent out once per week to call on our community to help test the Linaro evaluation builds we produce. If you have supported hardware, as found on: http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/ please help our initiative by testing: Ubuntu Desktop: http://snapshots.linaro.org/11.05-daily/linaro-ubuntu-desktop/ Nano: http://snapshots.linaro.org/11.05-daily/linaro-nano/ ALIP: http://snapshots.linaro.org/11.05-daily/linaro-alip/ Developer Tools: http://snapshots.linaro.org/11.05-daily/linaro-developer/ Make your way to: http://wiki.linaro.org/Releases/DailyBuilds for an explanation on how to test and submit your results to the QA tracker at: http://qatracker.linaro.org For an explanation of how to use the qatracker please see: https://wiki.linaro.org/QA/QATracker Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Making linaro-nano smaller or Give Up Disk Space for Lent
On 10/03/11 at 09:20am, James Westby wrote: > On Wed, 9 Mar 2011 13:15:25 -0600, Tom Gall wrote: > > 3) linaro-media-create should have some kind of option (--nano) to > > clear out apt caches (saves ~40 meg of space) > > If you want this it should be an easy change to make. If its an easy change it seems like a good option to support. I would go with --clear-apt-caches or something similar instead of --nano though unless we are tagging other behaviour on to this option too. > Thanks, > > James Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[REPORT] 2011-03-10 Infrastructure team weekly report
Hi,
The Infrastructure team weekly report for 2011-03-10 is now available
and can be found at:
https://wiki.linaro.org/Platform/Infrastructure/Status/2011-03-10
The report is also reproduced in full below.
Regards,
Jamie.
--
Linaro Release Manager | Platform Project Manager
--
* Period: (20110303-20110309)
* PM: JamieBennett
* Past reports : https://wiki.linaro.org/Platform/Infrastructure/Status
* Burndown information :
http://status.linaro.org/linaro-infrastructure.html
* Stakeholder process:
https://wiki.linaro.org/Platform/Infrastructure/CurrentProjects
== Key Points for wider discussion ==
* A 'feature-complete' version of the Android build system front-end to
Jenkins is available at {{{https://android-build.linaro.org/mockup/}}}.
Builds can be done by members of the ~linaro-android-builders Launchpad
team and the actual Jenkins instance can be found at
{{{http://android-build.linaro.org/jenkins}}}. Please take a look and
give comments.
* svammel mass bug filing tool for build failures is progressing. Some
more improvements planned but initial reviews are favorable. Code
reviews are welcome.
== Team Highlights ==
* ec2 investigations continue to find the best solution for the
continuous integration service. An ebs instance either small or large
for the master and include slaves as when needed for builds seems the
most effective.
* Mattias and Deepti now have Panda boards although Deepti's is shared
at the moment.
* Initial patch tracking metrics have been given to management.
* Tracking bugs as work items on non-Ubuntu projects was enabled in the
status.linaro.org code.
* Initial work on a planet instance for Linaro has been undertaken. The
results can be found at
[[http://ec2-50-17-53-200.compute-1.amazonaws.com/]]
== Upcoming Deliverables ==
* linaro-image-tools will be getting a release soon (likely before the
monthly release date to ease the process of getting it in to Ubuntu)
* Final patch metrics for the next member report in two weeks.
== Risks / Issues ==
* '''VERY HIGH IMPACT''': Mattias unable to work productively due to IT
restrictions in ST-E (5 weeks): some progress. Has process now to
request changes, but little response to his requests in more than 4
weeks. Mattias is working from home or over 3G in the meantime.
* '''HIGH IMPACT''': PatchTracking requires deploying Patchwork (4
weeks): Discussion with IS, and it is not expected to take them long to
do once they get to it. They have indicated that they may be able to
start at the end of this week, or in the week after.
* '''HIGH IMPACT''': Gerrit instance needed for Android (4 weeks):
Co-ordination with IS has started. Waiting to hear from them if we can
get it this month, and what we need to do to help with that.
* '''HIGH IMPACT''': Deepti believes she has not been granted travel to
Linaro@UDS (2 weeks): She will attend remotely where possible.
* '''HIGH IMPACT''': A large portion of James' time is taken by project
management at the moment (several weeks): investigations are in progress
on how to move most of this work onto a PM.
* '''MEDIUM IMPACT''': Deepti lacking hardware to work with her Panda
board: Deepti has received the Panda board, but doesn't have a
USB->serial cable for it, so is still unable to use it for much. Working
on tasks that don't require it, but unable to participate in image
testing. (many weeks).
* '''MEDIUM IMPACT''': OurOwnOffspring lacking hardware (many weeks):
x86 for master is ready and waiting, XMs for slaves delivered to IS.
Awaiting setup from IS.
* '''MEDIUM IMPACT''': Want a Jenkins/Hudson instance for Continuous
Integration purposes (many weeks): Discussions with IS, and they will
provide one, but timeframe is unclear at this point. Will host ourselves
until IS can provide. Work on getting an ec2 instance for this has
started, and we should have it running in ec2 by next week.
* '''MEDIUM IMPACT''': Deepti and Avik are sharing one Panda board
meaning some hardware specific work is being blocked (1 week).
== Miscellaneous ==
* Guilherme at PyCon 10-15 March
* James away 21st March
* Deepti on vacation 11th March
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
[REPORT] 2011-03-10 Android team weekly report
Hi, The Android team weekly report for 2011-03-10 is now available and can be found at: https://wiki.linaro.org/Platform/Android/Status/2011-03-10 The report is also reproduced in full below. Regards, Jamie. -- Linaro Release Manager | Platform Project Manager -- * Period: (20110303-20110309) * PM: JamieBennett * Past reports : https://wiki.linaro.org/Platform/Android/Status == Key Points for wider discussion == * Framebuffer patches still need more discussion * Team is discovering and discussing Blueprints to work on this and next cycle. More input from other teams is encouraged. == Team Highlights == * Improvements to linaro-media-create (not merged yet) and basic validation of the Android images. * Working on delivering the first binary Linaro toolchain for Android. This will then be validated using existing validation tools and a report sent next week. * More work defining the Android LEB to clearly understand what needs to be delivered in our images. * Framebuffer and Power Management work continues with the former due to land next week. * Two Panda boards are destined for the team although there is a problem with one on them (see below). == Upcoming Deliverables == * None. == Risks / Issues == * '''HIGH IMPACT''': Kenjie Watanabe states that his company committed him to work in Linaro but he currently has no time for this. Noritsuna will discuss the problem with the president of his company next week (3 weeks). We have now been informed that they will get clearance to work on the Project in April. * '''HIGH IMPACT''': Currently the Linaro Android efforts are based on 2.6.37 but with Linaro moving to 2.6.38 and the upstream Android 2.6.38 kernel being available some rebasing efforts will be needed. John Stultz, Patrik Ryd and others need to discuss how this can be done in the smoothest way (3 weeks). Some amount of effort will be needed but that effort is unclear at this point. Will lower level after initial investigations if necessary. Tree still needs to be produced for any assessment can be made. * '''MEDIUM IMPACT''': Contribution agreements with Google for AOSP development still waiting to be approved for Alexander Sack and Patrik Ryd (1 week). * '''MEDIUM IMPACT''': Patriks Panda board is lost in the postal system atm. Sent by Mounir from IBM, Patrik is chasing tracking numbers (1 week). * '''MEDIUM IMPACT''': Patrik lost some time last week due to an internal project at ST-E. Need to monitor to ensure Patrik stays focused on Linaro. * '''LOW IMPACT''': jstultz lost some days last week due to sickness. He is focussing on kconfig work for Linaro atm. == Miscellaneous == * Wiki pages of note this week: * https://wiki.linaro.org/Platform/Android/CurrentProjects ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[REMINDER] Weekly Release Meeting 2011-03-10
Hi, The weekly Linaro Release Meeting will be held at 17:00 UTC tomorrow. The agenda for the meeting can be found at: https://wiki.linaro.org/Releases/WeeklyReleaseMeeting/2011-03-10 and previous action items were: * Mounir to investigate the status of the Panda display problem * Mounir to ask the kernel team to triage bugs at https://bugs.launchpad.net/linux-linaro If you have points to raise or bugs that need to be discussed please add them to the wiki page above. This meeting is for everyone to discuss issues that may affect the ability to showcase Linaro's efforts in the released images so please add anything to the agenda that you feel falls into this category. The agenda will change a little this week, we will have image reports for our target releases done by: * Ubuntu Desktop and others - Tom Gall * Linaro Android - Patrik Ryd (Jamie Bennett this week) The full agenda is: * Announcements - Jamie Bennett with time for others to announce * Action Item Review - Jamie Bennett chasing * Image Status - Tom Gall and Patrik Ryd * Bugs - Jamie Bennett chair, others discuss * Team release-related reports (any team-focused release topics) * Any Other Business (AOB) Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[NOTES] Android Platform Team meeting 2011-03-09
Hi, The notes and actions for this weeks Android Platform Team meeting along with team activity reports are now available at: https://wiki.linaro.org/Platform/Android/Meetings/2011-03-09 = Actions Recorded = * jserv-- to produce a Blueprint at http://launchpad.net/linaro-android to capture pandroid fbdev investigations * patrikryd to confirm https://android-build.linaro.org/job/android-u8500href/ tarballs work and fix if necessary * jserv-- and jeremychang to split up Validation Blueprints * jserv-- and jeremychang to split up Linaro toolchain Blueprint * jserv-- and jeremychang to split up Linaro Evaluation Builds for Android Blueprint into board specific Blueprints * jeremychang to check with jstultz on the status of android_omap4_defconfig Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Monthly component release candidate dates
On 2 Mar 2011, at 08:52, Michael Hope wrote: > On Wed, Mar 2, 2011 at 9:48 PM, Peter Maydell > wrote: >> On 2 March 2011 01:33, Michael Hope wrote: >>> On Wed, Mar 2, 2011 at 10:04 AM, Peter Maydell >>> wrote: >>> https://wiki.linaro.org/Releases/MonthlyMilestones >> That would be an annoying format change for toolchain group releases, which are already on a monthly schedule and currently use "2011.03" for milestone names, and "2011.03-0" (-1, -2 ...) for release versions. >> >>> Hi Peter. We'll keep the 2011.xx-y names for the products. Each >>> project has product series and a planning series. The product series >>> are ones like '4.5' or '4.4' for gcc-linaro, and 'trunk' for >>> qemu-linaro, and these then have milestones like '2011.03'. >> >> Is this a proposal to vary the proposed new milestone names, >> or a suggestion that the toolchain group should continue as >> it is and not worry about the inconsistency with other groups? > > There's no change from our product series/milestone naming point of > view. The dates will change to the end of the month to sync up across > Linaro. There will be a parallel and, unfortunately, largely > identical planning series with milestones as well. We talked more about this tonight and the takeaway was that we need to investigate the best possible way of tracking deliverables with the existing tools we use. This may not explicitly be dependant on a specific milestone name, rather its date but this is still in progress. I'll reply back when I have more information. > -- Michael Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro Alpha-3 Released
Hi, The Linaro team is pleased to announce the availability of the 11.05 Alpha-3 images. These are still very early developer images but we encourage all with supported hardware to use and test them by downloading from: http://releases.linaro.org/platform/linaro-n/ Highlights of this release include: * Added Samsung s5pv310, ST-E u8500 and EfikaMX support. * New Ubuntu Desktop build utilizing the latest Ubuntu Unity desktop. * New Nano image for smaller installations. * Kernel 2.6.38-rc5. The images consist of two parts. A hardware pack which can be found under the ./hwpacks directory which contains hardware specific packages such as the kernel and bootloader. The second part is the roofs which is combined with the hardware pack to create a complete image. For For information on how to create an image please see: http://wiki.linaro.org/Releases/MilestoneBuilds More information on Linaro in general and the 11.05 plans can be found at: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org * 11.05: http://wiki.linaro.org/Releases/1105 Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.linaro.org or irc.freenode.net For any errata issues please see: http://wiki.linaro.org/Releases/1105/Alpha3#Issues Bug reports for this release should be filed in Launchpad against the individual packages that are affected, if a suitable package cannot be identified, feel free to assign them to: http://www.launchpad.net/linaro Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Linking from the Linaro website
On 03/03/11 at 03:15pm, Dave Martin wrote: > Hi all, > > In connection with the recent discussion with the tools guys about how > to document the availability of binary toolchains, I wonder whether > www.linaro.org really links to the best pages on launchpad, the wiki > etc. > > Keeping these in sync and coherently structured is a maintenance > requirement, and we can't expect to eliminate that. > > But I'm wondering whether we have some way to track: > > a) HTTP requests with no Referrer > b) Pages reached directly from Google or some other search facility > (such as the wiki or launchpad search) Yes we do, we have web analytic software on both the linaro.org website and the wiki. > Pages reached in these ways indicate where developers are using a > shortcut and visiting pages directly (I know I do this) or where the > page is at least sufficiently hard to find that Google or the wiki > search is more efficient (I know I do this too). If we could come up > with a list of such pages and frequency of visits, this might give us > some interesting information about what we really should be linking to > from the main website. It might also help to flag up drift, where > activity hotspots move away from the pages accessible from the website > over time. Yes, the linaro.org website site should get some more love soon. > Cheers > ---Dave Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 11.05 Alpha-3 Candidate testing
Hi, The Linaro 11.05 Alpha-3 image [1] is set to be released on Thursday 3rd March (tomorrow [2]) and we need your help. In addition to our in-house validation testing we ask anyone with supported hardware, as found on: http://releases.linaro.org/platform/linaro-n/hwpacks/alpha-3-rc/ to test the Alpha-3 release candidates at: Linaro Ubuntu Desktop LEB (Linaro Evaluation Build): http://releases.linaro.org/platform/linaro-n/nano/alpha-3-rc/ Nano: http://releases.linaro.org/platform/linaro-n/nano/alpha-3-rc/ ALIP: http://releases.linaro.org/platform/linaro-n/alip/alpha-3-rc/ Developer Tools: http://releases.linaro.org/platform/linaro-n/developer/alpha-3-rc/ The Nano and Ubuntu Desktop LEB are both new for this milestone so extra testing would be appreciated. Also note that the headless image has been replace by the Nano (for small installations) and Developer (for a headless + developer tools solution). Netbook has similarly been replaced by the Linaro Ubuntu Desktop image. Please make your way to: http://wiki.linaro.org/Releases/DailyBuilds for an explanation on how to test and submit your results to the QA tracker at: http://qatracker.linaro.org For an explanation of how to use the qatracker please see: https://wiki.linaro.org/QA/QATracker Happy Testing ! Regards, Jamie. -- Linaro Release Manager | Platform Project Manager [1] https://wiki.linaro.org/Releases/1105/Alpha3 [2] https://wiki.linaro.org/Releases/1105/Schedule ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[NOTES] Android Platform Team meeting 2011-03-02
Hi, The notes and actions for this weeks Android Platform Team meeting along with team activity reports are now available at: https://wiki.linaro.org/Platform/Android/Meetings/2011-03-02 = Actions Recorded = * JamieBennett to see if we can allocate a Panda board for jstultz * patrikryd to back out battery support from the android/platform/frameworks tree * jeremychang and jserv-- to investigate why pandroid platform breaks with fbdev * patrikryd to confirm https://android-build.linaro.org/job/android-u8500href/ tarballs work and fix if necessary * JamieBennett to update meeting template for new format * Team to summarise what they are doing on http://wiki.linaro.org/Platform/Android/CurrentProjects and try to derive Blueprints from that * johncylee and asac to talk about merging his content into requirements * everyone to review requirements document and check if there is anthing we can better define * JamieBennett to talk to jstultz how the oesf team goes Regards, Jamie. -- Linaro Release Manager| Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[REMINDER] Weekly Release Meeting 2011-03-03
Hi, The weekly Linaro Release Meeting will be held at 17:00 UTC tomorrow. The agenda for the meeting can be found at: https://wiki.linaro.org/Releases/WeeklyReleaseMeeting/2011-03-03 and previous action items were: * nytowl to test s5pv310 hwpack and images * slangasek to raise the issue with debian-policy on whether or not we need e2fsprogs as Essential: yes * JamieBennett to invite nytowl to the release meeting * tgall_foo to email JamieBennett, slangasek about netbook image status If you have points to raise or bugs that need to be discussed please add them to the wiki page above. Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Monthly component release candidate dates
On 02/03/11 at 09:52pm, Michael Hope wrote: > On Wed, Mar 2, 2011 at 9:48 PM, Peter Maydell > wrote: > > On 2 March 2011 01:33, Michael Hope wrote: > >> On Wed, Mar 2, 2011 at 10:04 AM, Peter Maydell > >> wrote: > > > https://wiki.linaro.org/Releases/MonthlyMilestones > > > >>> That would be an annoying format change for toolchain group > >>> releases, which are already on a monthly schedule and currently > >>> use "2011.03" for milestone names, and "2011.03-0" (-1, -2 ...) > >>> for release versions. > > > >> Hi Peter. We'll keep the 2011.xx-y names for the products. Each > >> project has product series and a planning series. The product series > >> are ones like '4.5' or '4.4' for gcc-linaro, and 'trunk' for > >> qemu-linaro, and these then have milestones like '2011.03'. > > > > Is this a proposal to vary the proposed new milestone names, > > or a suggestion that the toolchain group should continue as > > it is and not worry about the inconsistency with other groups? > > There's no change from our product series/milestone naming point of > view. The dates will change to the end of the month to sync up across > Linaro. There will be a parallel and, unfortunately, largely > identical planning series with milestones as well. For status.linaro.org to correctly track your Blueprints and Work Items together with the rest of Linaro's outputs they must be targeted to a milestone named like in the wiki page. Status will group all projects together with the same milestone to get a picture of what is due for that date. Targeting Work Items or Blueprints to another milestone will mean they won't show up. > -- Michael Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Monthly component release candidate dates
On 01/03/11 at 01:25pm, Tom Gall wrote: > On Tue, Mar 1, 2011 at 9:49 AM, Jamie Bennett > wrote: > > Hi, > > > > Throughout Linaro we are looking at ways to better coordinate the > > deliverables that come from Linaro's Working Groups and Platform teams. > > The idea of Monthly Component releases, a fixed date in the month where > > each team would release their latest work fits well with what we do and > > to that end a wiki page proposing the exact dates has been produced at: > > > > https://wiki.linaro.org/Releases/MonthlyMilestones > > It makes sense and I like the concept. > > Will there be some method for groups to state their goals for what they plan > to contribute to various releases? Wiki page? Blueprint? Something else? If agreed I would propose that all projects use the milestone names and dates in the above link in their launchpad projects. Blueprints and work items can then target these milestones and because all projects will have a common naming scheme we can agregate this out to http://status.linaro.org to get a Linaro wide picture of what is delivered, when. > Regards, > Tom Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: purpose/description of various linaro snapshot images?
On 01/03/11 at 04:10pm, Peter Maydell wrote: > On 1 March 2011 16:03, Steve Langasek wrote: > > On Tue, Mar 01, 2011 at 03:04:54PM +, Peter Maydell wrote: > >> Hi. On snapshots.linaro.org/11.05-daily/ there are now the > >> following different kinds of snapshot image: > > >> ...but I can't find anything on the wiki which documents > >> what each of these images is actually for, which makes it > >> hard to know which one to choose. > > > > The documentation is here: https://wiki.linaro.org/Releases > > Aha, thanks. (That page doesn't actually include the full > names of the images "linaro-nano" etc which is why it didn't > come up in my wiki search...) Yes, the /Release page holds of wealth of information on the releases we currently produce but we are going through a period of change at the moment and the documentation and announcements are lagging a little behind. I will get the snapshots directory tidied up this week and look out for a announcement regarding images soon. In the meantime I will trawl the wiki and try to make things a little clearer. Thanks for pointing this out. > -- PMM Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Monthly component release candidate dates
Hi, Throughout Linaro we are looking at ways to better coordinate the deliverables that come from Linaro's Working Groups and Platform teams. The idea of Monthly Component releases, a fixed date in the month where each team would release their latest work fits well with what we do and to that end a wiki page proposing the exact dates has been produced at: https://wiki.linaro.org/Releases/MonthlyMilestones You will notice that the dates are fixed, always the third Thursday in the month promoting a unified consistency across the teams. Please note that the Linaro Ubuntu Evaluation Builds do not follow this schedule and will continue to be closely coupled with the Ubuntu schedule. Please take a look at the dates and highlight any problems that could arise from them. If there is positive feedback we can make these dates 'official' very soon meaning teams could start using this format next month. Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[REMINDER] Weekly Release Meeting 2011-02-24
Hi, The weekly Linaro Release Meeting will be held at 17:00 UTC today. The agenda for the meeting can be found at: https://wiki.linaro.org/Releases/WeeklyReleaseMeeting/2011-02-24 and previous action items were: * JamieBennett to email LT to test s5pv310 * lool to ping Marex to enquire about support for Efika netbook support in uboot for this cycle * slangasek to file rt for syncing nano image to snapshots and stop headless syncing * slangasek to raise the issue with debian-policy on whether or not we need e2fsprogs as Essential If you have points to raise or bugs that need to be discussed please add them to the wiki page above. Regards, Jamie. -- Linaro Release Manager | Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[NOTES] Android Platform Team meeting 2011-02-23
Hi, The notes and actions for this weeks Android Platform Team meeting along with team activity reports are now available at: https://wiki.linaro.org/Platform/Android/Meetings/2011-02-23 = Actions Recorded = * kjnabe to contribute framebuffer support back to jstultz' git.linaro.org tree * kjnabe to contribute beagle defconfig to jstultz git.linaro.org tree * JamieBennett to prod people for framebuffer and defconfig changes to go to jstultz' tree * jserv-- and jeremychang to test John's tree for battery support and report back * JamieBennett to investigate certificates on android-build.linaro.org * jeremychang to confirm https://android-build.linaro.org/job/android-panda/ tarballs work and fix if necessary * patrikryd to confirm https://android-build.linaro.org/job/android-u8500href/ tarballs work and fix if necessary * jserv-- to confirm https://android-build.linaro.org/job/android-beagle/ tarballs work and fix if necessary * jserv-- jeremychang and patrikryd to improve their weekly report before JamieBennett submits a team report to linaro-dev tomorrow * asac to produce a better standing agenda for the meetings Regards, Jamie. -- Linaro Release Manager| Platform Project Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Board Support Review deadline this Thursday 24th February
Hi, Along with Feature Freeze [1], Thursday sees Linaro's Board Support Review deadline. This deadline marks the start of the process to define exactly what hardware will be enabled in the final Linaro Evaluation Builds released at the end of the cycle [2]. This review is to ensure that the target hardware support is progressing as expected and that the final user experience will shine on these boards. For more information on the Board Support Review deadline please see the Linaro wiki at: https://wiki.linaro.org/Process/Cycle/BoardReview There will be another review on 2011-03-24 where the list will be refined if necessary. A list of boards that Linaro expects to enable this cycle will be circulated after the review. Regards, Jamie. -- Linaro Release Manager| Platform Project Manager Office: +44 1761 348 220 | Mobile: +44 7962 259 437 [1] http://lists.linaro.org/pipermail/linaro-dev/2011-February/002702.html [2] https://wiki.linaro.org/Releases/1105 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Feature Freeze this Thursday 24th February
Hi, Thursday 24th February is Feature Freeze. This is a point in the Engineering Cycle [1] where we stop taking new features and concentrate on fixing bugs. Please get your new features (as defined by new packages, API changes, additional features) proposed and uploaded to the archive as soon as possible. If you know of any features that will not make the deadline please make the Release Manager (me) aware of these and be prepared for the Feature Freeze Exception Process, an explanation of which can be found at: https://wiki.linaro.org/Process/Cycle/FreezeExceptionProcess To read more about the Feature Freeze deadline head on over to: https://wiki.linaro.org/Process/Cycle/FeatureFreeze Regards, Jamie. -- Linaro Release Manager [1] https://wiki.linaro.org/Releases/1105/Schedule ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: /latest link now active on snapshots.linaro.org
On 02/14/11 at 06:39pm, Amit Kucheria wrote: > On 11 Feb 08, Steve Langasek wrote: > > Hi Jamie, > > > > On Tue, Feb 08, 2011 at 01:10:46PM +, Jamie Bennett wrote: > > > > > There is now a much easier way to download the daily Linaro images and > > > hardware packs, the /latest link. Inside each build directory a /latest > > > link will always point to the latest successful build. The following > > > urls are currently setup: > > > > > http://snapshots.linaro.org/11.05-daily/linaro-alip/latest > > > http://snapshots.linaro.org/11.05-daily/linaro-developer/latest > > > http://snapshots.linaro.org/11.05-daily/linaro-headless/latest > > > http://snapshots.linaro.org/11.05-daily/linaro-netbook-efl/latest > > > > Thanks for making this happen! > > > > +1 to Loïc's comment that this should link directly to the latest build, not > > just the latest day. > > The currently link needs the following navigation: > > http://snapshots.linaro.org/11.05-daily/linaro-developer/latest/0/images/tar/linaro-n-developer-tar-20110214-0.tar.gz > > Perhaps it's also be possible to simply that to > > http://snapshots.linaro.org/11.05-daily/linaro-developer/latest/linaro-n-developer.tar.gz > ? > > (note change to filename) This is beyond the capabilities of the current scripts we have for syncing images from Offspring to the snapshots server. The Infrastructure team have this on their plate to investigate whether or not we can add this to Offspring itself. I'll keep you informed. > /Amit > Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [linaro-android][PATCH] Make adbd listen on network interface
On 02/14/11 at 01:31pm, Alexander Sack wrote: > On Mon, Feb 14, 2011 at 12:52 PM, Jeremy Chang wrote: > > From dbeb9e14eb4b5d70775426a370681c90928d4d84 Mon Sep 17 00:00:00 2001 > > From: Jeremy Chang > > we should get you your @linaro.org address asap. > > > Date: Mon, 14 Feb 2011 11:28:12 +0800 > > Subject: [PATCH] Make adbd listen on network interface > > please indicate against what repo this is supposed to land; so here it > would be something like: > > [PATCH] device/linaro/beagleboard: make adbd listen on network interface > > Also while its OK to do things like this for now, we should soonish > come up with a mechanism that allows us to add these things either in > one "device/linaro/common-devboard" tree or a mechanism that allows us > to track what was added to what board - so our board features don't go > out of sync. These patches should also be cc'd to patc...@linaro.org > - Alexander Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 11.05 Weekly Testing 2011-02-10
Hi, This is a message sent out once per week to call on our community to help test the Linaro evaluation builds we produce. If you have supported hardware, as found on: http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/ please help our initiative by testing: Headless: http://snapshots.linaro.org/11.05-daily/linaro-headless/ ALIP: http://snapshots.linaro.org/11.05-daily/linaro-alip/ Netbook: http://snapshots.linaro.org/11.05-daily/linaro-netbook-efl/ Developer Tools: http://snapshots.linaro.org/11.05-daily/linaro-developer/ Make your way to: http://wiki.linaro.org/Releases/DailyBuilds for an explanation on how to test and submit your results to the QA tracker at: http://qatracker.linaro.org For an explanation of how to use the qatracker please see: https://wiki.linaro.org/QA/QATracker Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
/latest link now active on snapshots.linaro.org
Hi, There is now a much easier way to download the daily Linaro images and hardware packs, the /latest link. Inside each build directory a /latest link will always point to the latest successful build. The following urls are currently setup: http://snapshots.linaro.org/11.05-daily/linaro-alip/latest http://snapshots.linaro.org/11.05-daily/linaro-developer/latest http://snapshots.linaro.org/11.05-daily/linaro-headless/latest http://snapshots.linaro.org/11.05-daily/linaro-netbook-efl/latest Please note that the headless and netbook-efl images will be replaced by the Nano and Evaluation Ubuntu Desktop builds soon. The following hardware packs are also built: http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/igep/latest/ http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/imx51/latest/ http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/lt-s5pv310/latest http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/omap3/latest/ http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/omap3-x11-base/latest/ http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/overo/latest/ http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/panda/latest/ http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/vexpress/latest/ Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Minutes and actions Multimedia working group meeting on 1st Feb 2011
On 02/04/11 at 02:03pm, Sachin Gupta wrote: > Hi All, > >Please find enclosed link to minutes and actions for multimedia wg > meeting on 1st Feb 2011. > > https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/Notes/2011-02-01 Can you include a summary of the meeting in these emails? It means that readers can see the interesting parts and click the link if they want to find out more. > Thanks > Sachin Regards, Jamie. -- Linaro Release Manager| Platform Project Manager Office: +44 1761 348 220 | Mobile: +44 7962 259 437 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 11.05 Alpha-2 Released
Hi, The Linaro team is pleased to announce the availability of the 11.05 Alpha-2 images. These are still very early developer images but we encourage all with supported hardware to use and test them by downloading from: http://releases.linaro.org/platform/linaro-n/ Highlights of this release include: * Added Gumstix Overo support. * New Developer image including console base developer tools. * Complete rewrite of the installation tools (linaro-image-tools) to improve the user experience. * A staggering 141 out of 160 packages have been upgraded since Alpha-1. The images consist of two parts. A hardware pack which can be found under the ./hwpacks directory which contains hardware specific packages such as the kernel and bootloader. The second part is the roofs which is combined with the hardware pack to create a complete image. For For information on how to create an image please see: http://wiki.linaro.org/Releases/MilestoneBuilds More information on Linaro in general and the 11.05 plans can be found at: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org * 11.05: http://wiki.linaro.org/Releases/1105 Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.linaro.org or irc.freenode.net For any errata issues please see: http://wiki.linaro.org/Releases/1105/Alpha2#Issues Bug reports for this release should be filed in Launchpad against the individual packages that are affected, if a suitable package cannot be identified, feel free to assign them to: http://www.launchpad.net/linaro Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 11.05 Alpha-2 (part 2) candidate testing
Hi, Due to an xserver issue in the Ubuntu archive (xserver packages built against old xserver-xorg-core) the Alpha-2 images have been re-rolled and are ready for your testing. The links are: Hardware Packs: http://releases.linaro.org/platform/linaro-n/hwpacks/alpha-2-rc2/ Headless: http://releases.linaro.org/platform/linaro-n/headless/alpha-2-rc2/ ALIP: http://releases.linaro.org/platform/linaro-n/alip/alpha-2-rc2/ Netbook: http://releases.linaro.org/platform/linaro-n/netbook/alpha-2-rc2/ Developer Tools image: http://releases.linaro.org/platform/linaro-n/developer/alpha-2-rc2/ As always, for an explanation of how to test the images on your hardware head on over to: http://wiki.linaro.org/Releases/DailyBuilds and submit your results to: http://qatracker.linaro.org For an explanation of how to use the qatracker please see: https://wiki.linaro.org/QA/QATracker Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 11.05 Alpha-2 Candidate testing
Hi, The Linaro 11.05 Alpha-2 image [1] is set to be released on Thursday 3rd February (in two days !) [2] and we need your help. In addition to our in-house validation testing we ask anyone with supported hardware, as found on: http://releases.linaro.org/platform/linaro-n/hwpacks/alpha-2-rc/ to test the Alpha-2 release candidates at: Headless: http://releases.linaro.org/platform/linaro-n/headless/alpha-2-rc/ ALIP: http://releases.linaro.org/platform/linaro-n/alip/alpha-2-rc/ Netbook: http://releases.linaro.org/platform/linaro-n/netbook/alpha-2-rc/ and our new image, Developer Tools image: http://releases.linaro.org/platform/linaro-n/developer/alpha-2-rc/ Please note that due to a lack of committed support the Plasma image has been dropped from our list of regularly tested images. If you would like to see the Plasma image return and can give support to the maintenance and testing of this image please get in contact with me. Please make your way to: http://wiki.linaro.org/Releases/DailyBuilds for an explanation on how to test and submit your results to the QA tracker at: http://qatracker.linaro.org For an explanation of how to use the qatracker please see: https://wiki.linaro.org/QA/QATracker Regards, Jamie. -- Linaro Release Manager [1] https://wiki.linaro.org/Process/Cycle/Alpha1Release [2] https://wiki.linaro.org/Releases/1105/Schedule ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Community image testing
On 01/27/11 at 12:50pm, Jamie Bennett wrote: > Hi, > > In addition to our in-house validation and testing this is a call for > help in testing the images Linaro produces. If you have supported > hardware, as found on: > > http://snapshots.linaro.org/10.11-daily/linaro-hwpacks/ Of course this should of been: http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/ It seems I am living in the past, sorry for the confusion. Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Community image testing
Hi, In addition to our in-house validation and testing this is a call for help in testing the images Linaro produces. If you have supported hardware, as found on: http://snapshots.linaro.org/10.11-daily/linaro-hwpacks/ and are willing to test, please make your way to: http://wiki.linaro.org/Releases/DailyBuilds for an explanation on how to test and submit your results to the QA tracker at: http://qatracker.linaro.org For an explanation of how to use the qatracker please see: https://wiki.linaro.org/QA/QATracker Community testing is essential if we are to produce well integrated and robust Linux on ARM images, with your help we can get there. Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[REMINDER] Weekly Release Meeting tomorrow, 17:00 UTC
Hi, The weekly Linaro Release Meeting will be held tomorrow, Thursday 27th January 2011 in the #linaro-meeting room on freenode. The agenda for this weeks meeting can be found at: https://wiki.linaro.org/Releases/WeeklyReleaseMeeting/Current This week we will be introducing per-team responsibility for high priority bugs. I've separated important bugs into logical groups, can the PM group and tech leads ensure that these bugs are on the radar for your teams? Please take a look at the current list on the above page. If you would like anything brought up at the meeting please also add your items to the above page. For people who had action items from last week please update your status at the top of the page. Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Call for opinion: Linaro 'Developer' Image
On 24 January 2011 20:49, Michael Hudson-Doyle wrote: > On Fri, 21 Jan 2011 13:22:45 +0000, Jamie Bennett > wrote: > >> The current thoughts are to increase the package count and download >> size by adding a number of developer focused packages. > > Once we have the smaller image and this developer image (both of which I > see the need for), what is the use case for the current headless image? Basically Headless would go away. These two images are being proposed to replace the Headless image which is neither small nor feature-ful. Hopefully the new images will address the specific needs of two different target audiences better. > Cheers, > mwh Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Call for opinion: Linaro 'Nano' Image
On 21 Jan 2011, at 15:42, Loïc Minier wrote: > On Fri, Jan 21, 2011, Jamie Bennett wrote: >> Currently we are reassessing whether or not the Headless image meets >> the requirements for a small, fast, useable image for board >> verification. Just for information the current stats as of 2011-01-21 >> are: >> >> * Download Size: 64M >> * Download size with OMAP3 hwpack: 100M >> * Package count: 260 >> >> The list of package currently on the image can be found at: >> >> https://wiki.linaro.org/Platform/Foundations/Specs/HeadlessImage#Package List >> >> The current thoughts are to cut this image down as much as possible >> whilst still retaining the ability to boot to a command prompt. The >> new image would be a 'nano' image and would be useful for verifying >> that the hardware boots. For a more complete console-only image for >> developers a full-featured developer image would be created. See my >> other email entitled "Call for opinion: Linaro 'Developer' Image" >> for that. >> >> Is anyone *really* against this idea and is satisfied with the >> Headless image in its current state? Opinions? Thoughts? Criticisms? > > Could we do with an initrd instead of an image? I mean, busybox + > small set of tools is probably enough for validation, and will be quite > small. > > There is inherent bloat as soon as we add a package manager in the mix Right, current thoughts after some IRC discussion are: * busybox * no package manager * max size of 30mb (without kernel) * some further removal of packages I think with this in place you will get a ~30mb compress rootfs, we could even go further if necessary. > Loïc Minier Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Call for opinion: Linaro 'Developer' Image
Hi, Currently we are reassessing whether or not the Headless image meets the requirements for a console-only developer focused image usable for kernel, boot loader, power management and other types of non-gui development. Just for information the current stats as of 2011-01-21 are: * Download Size: 64M * Download size with OMAP3 hwpack: 100M * Package count: 260 The list of package currently on the image can be found at: https://wiki.linaro.org/Platform/Foundations/Specs/DeveloperImage#Package List The current thoughts are to increase the package count and download size by adding a number of developer focused packages. The initial list of additional packages can be found at: https://wiki.linaro.org/Platform/Foundations/Specs/DeveloperImage#Design Is there anything missing? A more stripped down 'nano' image will be produced for board bring-up and verification, see my other email entitled "Call for opinion: Linaro 'Nano' Image" for more information. Is anyone *really* against this idea and is satisfied with the Headless image in its current state? Opinions? Thoughts? Criticisms? Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Call for opinion: Linaro 'Nano' Image
Hi, Currently we are reassessing whether or not the Headless image meets the requirements for a small, fast, useable image for board verification. Just for information the current stats as of 2011-01-21 are: * Download Size: 64M * Download size with OMAP3 hwpack: 100M * Package count: 260 The list of package currently on the image can be found at: https://wiki.linaro.org/Platform/Foundations/Specs/HeadlessImage#Package List The current thoughts are to cut this image down as much as possible whilst still retaining the ability to boot to a command prompt. The new image would be a 'nano' image and would be useful for verifying that the hardware boots. For a more complete console-only image for developers a full-featured developer image would be created. See my other email entitled "Call for opinion: Linaro 'Developer' Image" for that. Is anyone *really* against this idea and is satisfied with the Headless image in its current state? Opinions? Thoughts? Criticisms? Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Reminder: Weekly Linaro Release Meeting tomorrow
Hi, The weekly Linaro Release Meeting will be held at 17:00 UTC tomorrow (Thursday). Please note the change of day which is due to a resolution in meeting conflicts meaning the release meeting can return to its normal slot. The agenda for the meeting can be found at: https://wiki.linaro.org/Releases/WeeklyReleaseMeeting/2011-01-20 Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Linaro Infrastructure Team Weekly Report (2010-12-17 to 2010-12-23)
On 24 Dec 2010, at 11:14, Ian Smith wrote: > All, > > The weekly report for the Linaro Infrastructure team may be found at:- > Status report: > https://wiki.linaro.org/Platform/Infrastructure/Status/2010-12-23 > Burndown chart: This link is awaiting the production of new burndown charts. Needs to be checked for completeness but there is a burndown for Infrastructure at: http://people.linaro.org/~linaro/workitems/natty/linaro-infrastructure.html > The Infrastructure related blueprints from the maverick cycle, of which > currently there are 4 active ones (4 from the last report), are showing that > there are 9 work items in progress (8 last report), and 10 work items to > undertake (11 last report). These are to be moved into the natty cycle if > still required. I've seen this comment for several weeks now, can you arrange to move them to the natty cycle or mark them as Implemented/Deferred in the new year? Regards, Jamie. -- Linaro Release Manager| ARM Technical Liaison Engineer Office: +44 1761 348 220 | Mobile: +44 7962 259 437 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Weekly Release Meeting Cancelled
Hi, Due to the holiday season many key people are on vacation at the moment. For this reason the weekly Release Meeting has been cancelled. The next meeting will be Wednesday 5th January 2010. Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: autobuild system of linaro
On 15 Dec 2010, at 08:48, Alexander Sack wrote: > On Wed, Dec 15, 2010 at 9:39 AM, Alexander Sack wrote: >> Hi Paul, >> >> On Wed, Dec 15, 2010 at 9:28 AM, Paul Li wrote: >>> Hi, >>> >>> >>> >>> If I want to build the system from scratch, what should I do? I >>> mean, where to get the deb binary packages of Linaro? Where to get the image >>> creator tool? etc. thank you. >> >> most of the content for that should be linked from >> https://wiki.linaro.org/Source ... let us know if there is anything >> missing to get a start. > > One thing we seem to be missing there is a comprehensive > "Source/BuildingHwpacks" wiki page. The details for that are available > in the spec: > https://wiki.linaro.org/Platform/UserPlatforms/Specs/10.11/HardwarePacks Not in a great place on the wiki, feel free to move it but: https://wiki.linaro.org/HardwarePacks > - Alexander Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Linaro Infrastructure Team Weekly Report (2010-12-03 to 2010-12-09)
On 10 Dec 2010, at 13:56, Ian Smith wrote: > * Also finished porting the work items tracker to use the launchpad > APIPlease let me know if you have any comments or questions. Just to make it clear, this work has not been completed and is still in progress. Currently no code changes have landed to the work items tracker but James is doing a stella job trying to investigate fixes. > Kind Regards, > > > Ian Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Landing team pages?
On 7 Dec 2010, at 05:20, Michael Opdenacker wrote: > Hi, > > I can't find any details about the landing teams on the wiki, except > this https://wiki.linaro.org/LandingTeams > > It would be useful to have a Wiki page per landing team, showing the > team members and the corresponding Launchpad pages (if any). There will be when each Landing Team is established. The only one currently active is the ST-E one and Lee (tech lead) has been asked to create http://wiki.linaro.org/LandingTeams/ST-E. > For example, I wanted to reply to a forum question > (http://www.linaro.org/linux-bsps/show/15), but didn't find any link to > the OMAP landing team. That's because there currently isn't one. > Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 11.05 Alpha-1 Released
Hi, The Linaro team is pleased to announce the availability of the 11.05 Alpha-1 images. These very early developer images build on the great work done during the 10.11 cycle and can be downloaded from the following location: http://releases.linaro.org/platform/linaro-n/ The images consist of two parts. A hardware pack which can be found under the ./hwpacks directory contains hardware specific packages such as the kernel and bootloader. The second part is the rootfs which is combined with the hardware pack to create a complete image. For information on how to create an image please see: http://wiki.linaro.org/Releases/MilestoneBuilds More information on Linaro in general and the 11.05 plans can be found at: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org * 11.05: http://wiki.linaro.org/Releases/1105 Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.freenode.net For any errata issues please see: http://wiki.linaro.org/Releases/1105/Alpha1#Issues Bug reports for this release should be filed in Launchpad against the individual packages that are affected, if a suitable package cannot be identified, feel free to assign them to: http://www.launchpad.net/linaro Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro Release Meeting tomorrow
Hi, Just a reminder to say that the weekly Linaro release meeting will be held tomorrow at 17:00 UTC in the #linaro-meeting irc channel on freenode. The wiki page for the meeting can be found at: https://wiki.linaro.org/Releases/WeeklyReleaseMeeting/2010-12-02 If you have something to add to the discussion either reply directly to this email or add you notes to the wiki page above. See you there. Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Call for testing: Linaro Alpha-1
Hi, Tomorrow Linaro will release the Alpha-1 images. In anticipation of this the release candidate has been produced and is ready for testing. If you have supported hardware and are willing to test please head on over to: http://releases.linaro.org/platform/linaro-n and select an image type. Please take the files from the alpha-1-rc directory and combine them with a alpha-1-rc hardware pack from the hwpack directory at the same location. Instructions on how to do this can be found at: http://wiki.linaro.org/Releases/MilestoneBuilds The QA tool, qatracker, has been setup ready for test results and can be found at: http://qatracker.linaro.org and instructions on how to test are available on the wiki at: http://wiki.linaro.org/QA/QATracker Alpha-1 is a very early snapshot of Linaro's development progress for the 11.04 release. It *will* contain bugs but with the help of our testers, these bugs will be squished as the development cycle progresses. Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Notes & Actions: Linaro User Platform Weekly Status Meeting 11/24
On 29 Nov 2010, at 19:16, Tom Gall wrote: > Greetings, > > Enclosed you'll find a link to the agenda, notes and actions from the > Linaro User Platforms Weekly Status meeting dated November 24th held in > #linaro-meeting on irc.freenode.net at 13:00 UTC. > > https://wiki.linaro.org/Platform/UserPlatforms/WeeklyStatus/2010-11-24 Just a clarification from the notes, images for ALIP, Netbook and Headless are available for testing at http://snapshots.linaro.org/11.05-daily/. Plasma is currently not build-able due to a QT issue which is being worked on, I hope to have more news on that in the coming days. Regards, Jamie. > Status Summary: > * Good progress on discussions with upstream Cairo team > * Confirmed with upstream Unity team that there is no plan to add > gles2 support to compiz/nux > * Focus continues in refining Blueprints and Specifications across > Multimedia and Graphics WGs > * Seeds for linaro-development, linaro-multimedia-engineering and > linaro-graphical-engineering either merged or in a proposed state in > prep for natty-alpha-1 > > Regards, > Tom (tgall_foo) > User Platforms Team > > "We want great men who, when fortune frowns will not be discouraged." > - Colonel Henry Knox > w) tom.gall att linaro.org > w) tom_gall att vnet.ibm.com > h) tom_gall att mac.com > > ___ > linaro-dev mailing list > linaro-dev@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-dev ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro Alpha-1 Freeze next week
Hi, According to the 11.05 release schedule [1] the Linaro Alpha-1 release will be made next Thursday. To help prepare and test the images developers are asked to refrain from uploading changes to the archive from Tuesday 30th November until Thursday 2nd December. >From Tuesday onwards the release candidate image for Alpha-1 will be selected and available for testing. The Linaro QA tracking tool [2] will be available for submission of results at the same time so please test, submit your results and report bugs either in the project the bug occurs or if in doubt, to the Linaro project at http://bugs.launchpad.net/linaro. For more information on the Linaro 11.05 release please see the wiki page at: http://wiki.linaro.org/Releases/1105/ Regards, Jamie. -- Linaro Release Manager [1] http://wiki.linaro.org/Releases/1105/Schedule [2] http://qatracker.linaro.org ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Linaro Infrastructure Team Weekly Report (2010-11-12 to 2010-11-18)
On 18 Nov 2010, at 11:46, Ian Smith wrote: > All, > > The weekly report for the Linaro Infrastructure team may be found at:- > Status report: > https://wiki.linaro.org/Platform/Infrastructure/Status/2010-11-18 > Burndown > chart:http://people.canonical.com/~pitti/workitems/maverick/linaro-infrastructure.html This is the burndown chart from last cycle and has been static for quite some time. New burndown charts are yet to be set up. > > The Infrastructure related blueprints, of which currently there are 4 active > ones (4 from the last report), are showing that there are 8 work items in > progress (11 last report), and 11 work items to undertake (12 last report). > > arm-m-validation-dashboard;0 work items completed since last report; > 3 in progress;7 to do > arm-m-image-building-console; 1 work items completed since last report; > 3 in progress;3 to do > arm-m-automated-testing-framework; no change in status from last report; 1 > in progress;0 to do > arm-m-testsuites-and-profilers;no change in status from last report; 1 in > progress;1 to do Will these be moved to the n-series to be re-tracked this cycle? > The focus for the team in the past week has remained on preparing Blueprints > for the next cycle and holding the review conference call on Monday > (2010-11-15). > > The team had two new members join this week. > > Specifics accomplished this week include:- > >* A number of new PPAs were produced this week, including an improved > linaro-json package and a stable API for working with dashboard bundles. >* Work started on ImproveLinaroMediaCreate >* Two bugs were fixed for Linaro Image Tools covering apt-get running in > rootfs and replacing "sfdisk -l"with "fdisk -l" to give more useful > information. Neither of these changes have landed and are currently waiting approval to be merged. > Please let me know if you have any comments or questions. > > Kind Regards, > > > Ian Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Problems with BeagleBoard installation
On 11 Nov 2010, at 13:53, Pawel Moll wrote: You were so close. https://wiki.linaro.org/Releases has instructions on how to obtain and use the Linaro images. Oh sure! Just to be clear - I found it before, searching wiki. But this time I just tried to pretend a fresher - say one of my Olympia colleagues - and follow the big links :-) I have also asked for a big download link to be prominent on either the And that's exactly what I was talking about - the huge "Downloads" link is great. https://wiki.linaro.org/Releases/1011"; leads to "/Releases/1011" not > to "/Releases/1011/Final"... And as far as I can say there is no link > from the former to the latter? There is a table at the bottom with all the release pages. Uh, you're right - I found it with Ctrl-F. But not before, even if I knew what I was looking for ;-) To summarize, if I may suggest anything - changing the "https://wiki.linaro.org/Releases/1011"; link on the "Downloads" page so it points directly to "/Releases/1011/Final" would do the job, I believe. Thats for Michael to do but for the meantime I'll added explicit download links on the https://wiki.linaro.org/Releases/1011 page. Cheers! Paweł Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Problems with BeagleBoard installation
On 11 Nov 2010, at 13:17, Pawel Moll wrote: There's a "get started" link on the new http://www.linaro.org/ page. It could be clearer, but I think it's better than what used to be there. Any help? Oh, it's much better only, if only with the big "Downloads" link on the frontpage :-) The only thing I could complain now about is that I didn't find any visible link to "how to prepare a card with the image" (I mean "how to use linux-media-create"). But maybe I just missed it somewhere? I looked at the http://www.linaro.org/downloads/ and https://wiki.linaro.org/Releases/1011 pages). You were so close. https://wiki.linaro.org/Releases has instructions on how to obtain and use the Linaro images. I have also asked for a big download link to be prominent on either the linaro.org site or we could add it to the wiki. Cheers! Paweł Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Problems with BeagleBoard installation
On 11 Nov 2010, at 13:30, Pawel Moll wrote: For instructions on obtaining and installing the release, you can visit https://wiki.linaro.org/Releases/1011/Final and click on the link under "Instructions" All this can be found by following links from "Getting started" on http://www.linaro.org/ ... Well, can it? ;-) What I see is that the "Getting started" leads me to the "Downloads" page, then there is this frame on the right side - "Download Linaro for your board", right? The problem is that the link which is given there: "More information on the development release as well as download and installation instructions can be found at: https://wiki.linaro.org/Releases/1011"; leads to "/Releases/1011" not to "/Releases/1011/Final"... And as far as I can say there is no link from the former to the latter? There is a table at the bottom with all the release pages. Probably just a mistake? Cheers! Paweł Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 10.11 Final released
Hi, The Linaro team is pleased to announce the release of Linaro 10.11. 10.11 is the first public release that brings together the huge amount of engineering effort that has occurred within Linaro over the past 6 months. In addition to officially supporting the TI OMAP3 (Beagle Board and Beagle Board XM) and ARM Versatile Express platforms, the images have been tested and verified on a total of 7 different platforms including TI OMAP4 Panda Board, IGEPv2, Freescale iMX51 and ST-E U8500. The advances that have happened in this cycle are numerous but include a completely rebuilt archive using GCC 4.4.4 and the latest ARM optimised tool chain, the Linux kernel version 2.6.35, support for cross-compiling, a new hardware pack way of building images, 3D acceleration improvements, u-boot enhancements and initial device tree support, a new QA tracking structure, the list goes on. For a full break-down of what was scheduled for the 10.11 release please see: http://wiki.linaro.org/Releases/1011/Blueprints Thanks to everyone involved who made this happen. Here's looking forward to a sucessful 11.05 release. To get Linaro 10.11 --- The 10.11 release can be found at: http://releases.linaro.org/platform/linaro-m/headless/final/ and when combined with a hwpack from: http://releases.linaro.org/platform/linaro-m/hwpacks/final/ using the instructions from: http://wiki.linaro.org/Releases/MilestoneBuilds a installable image is produced. For any errata issues please see: http://wiki.linaro.org/Releases/1011/Final#Issues Bug reports for this release should be filed in Launchpad against the individual packages that are affected, if a suitable package cannot be identified, feel free to assign them to: http://www.launchpad.net/linaro The team has also produced 3 other non-supported images as part of a community effort, they are: * ALIP * http://releases.linaro.org/platform/linaro-m/alip/final/ * EFL based netbook * http://releases.linaro.org/platform/linaro-m/netbook/final/ * KDE based plasma handset * http://releases.linaro.org/platform/linaro-m/plasma/final/ These need to be combined with a hardware pack as above. Next Steps -- Engineering effort has already started on the 11.05 cycle. For more information on what Linaro will be doing this cycle please see: http://wiki.linaro.org/Releases/1105 Getting involved If you would like to help shape the Linux on ARM space and Linaro in particular please take a look at: http://wiki.linaro.org/GettingInvolved About Linaro More information on Linaro in general and the 10.11 release can be found at: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org * 10.11: http://wiki.linaro.org/Releases/1011 Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.freenode.net Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
re: Call for testing: Linaro 10.11 FINAL
Hi, It has been pointed out that due to a failure in the build system the following image link is wrong. > EFL Netbook image: > http://snapshots.linaro.org/10.11-daily/linaro-netbook-efl/20101108/2/ Please use the image at EFL Netbook image: http://snapshots.linaro.org/10.11-daily/linaro-netbook-efl/20101108/1/ For your testing. Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Weekly Release Meeting Cancelled
Hi, Due to the Linaro 10.11 final release happening tomorrow and blueprints still being ironed out, the next two weeks of release meetings have been cancelled. Normal release meetings will commence on 2010-11-25. This date is a US holiday but I expect our non-US friends to join us. Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Problems with BeagleBoard installation
On 8 Nov 2010, at 15:52, Alexander Sack wrote: On Mon, Nov 8, 2010 at 12:20 PM, Dave Martin wrote: Dave Martin also gave me this link https://wiki.linaro.org/Source/ImageInstallation, but it doesn't exist anymore. I'm pretty sure the link was there before. Now I can't find any installation instructions page for Beagle at all. Does anyone know where it went (and why?) I assume Jamie refactored something. Found that there is now GettingInstallingTesting ... I removed the page as it had outdated information on there that was actually causing people to not be able to install images. I've rolled all that information in to the DailyBuilds (and MileStoneBuilds) pages. I am not sure I like the new multi-purpose naming. How about we resurrect Source/ImageInstallation (or under Release/) and <> that page in the Releases/GettingInstallingTesting page? The GettingInstallingTesting page is linked in from the other build pages and should not be used on its own. Its the common part of image building that the other pages use instead of duplicating the information. See: http://wiki.linaro.org/Releases#Obtaining and Testing Linaro Images Specifically: http://wiki.linaro.org/Releases/DailyBuilds http://wiki.linaro.org/Releases/MilestoneBuilds - Alexander Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Ubuntu ARM and the linaro kernels
Hi Oliver, Answers in-line below. On 8 Nov 2010, at 15:12, Oliver Grawert wrote: hi, at UDS we discussed the possibility of using linaro kernels for some of the ubuntu ARM flavours (currently for omap3 images but there might be more to come) where we seem to have duplicated efforts in kernel team and linaro ... there were some open questions that require further discussion with a wider audience which i'd like to bring up in this mail: * linaro kernels used in ubuntu ARM would need to move to the supported package set (main) which makes them fall under all freeze restrictions the kernel team sets for ubuntu (only SRUs post kernel freeze, patches and changes all need to go through the ubuntu-kernel mailing list etc) I think we can deal with the via the SRU process. We have already been using the SRU process this cycle for kernel changes so its a non-issue. * configuration changes in the linaro kernels would have to happen to match the ubuntu distro kernel configs in all places where they do not match yet (this also implies that ubuntu sauce needs to be added to the linaro kernels for making all distro features available) I'm not sure Linaro want to carry the Ubuntu sauce and match configs. Linaro's continued effort to consolidate and stream-line kernels rather than expand options to cover all eventualities may conflict, this would need to be carefully investigated. * someone has to commit to do security support for these kernels to match the 18 months security support we provide for ubuntu images (can the ubuntu kernel team and the ubuntu security team commit to that ?) This would be a problem for Linaro. Currently we have no support options that look like what you describe above. The only option at the moment would be for the Ubuntu Security Team to provide security support for the kernels once they come out of Linaro unless Linaro change their model. if not all of the above bulletpoints (please shout if i missed any that are obvious) can be fulfulled we can not take linaro kernels for our images and another solution needs to be found. I would love to see the sharing of kernels here. We need to come up with a good solution of which I don't have at the moment. I've cc'd linaro-dev in to solicit more comments from the Linaro side. ciao oli Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Call for testing: Linaro 10.11 FINAL
Hi, We are just one day away from the Linaro 10.11 release and with a bit of luck, a strong down-wind and lots of testing from the community we can release on time and in good shape. If you have the required hardware available *please* test the final image candidates which can be found as follows: Headless (console only) image: http://snapshots.linaro.org/10.11-daily/linaro-headless/20101108/2 ALIP image: http://snapshots.linaro.org/10.11-daily/linaro-alip/20101108/2/ EFL Netbook image: http://snapshots.linaro.org/10.11-daily/linaro-netbook-efl/20101108/2/ KDE Plasma image: http://snapshots.linaro.org/10.11-daily/linaro-handset-plasma/20101108/2 Please select the 20101109 hwpack for your board at: http://snapshots.linaro.org/10.11-daily/linaro-hwpacks/ To install the image please see: http://wiki.linaro.org/Releases/DailyBuilds and report your results at: http://qatracker.linaro.org/ Failing any major last minute bugs this snapshot will become the final image tomorrow. Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 10.11 Release Candidate available
Hi, We are nearly there! In 9 days the 10.11 Final image will be released to the world and in preparation for this the Release Candidate image is now available. Please download and test as much as possible to ensure the final release is of the highest quality. This milestone release is the first to utilise the new build process of separate hardware packs and generic images. To build a complete image one hardware pack and one generic image is combined with the linaro-media-create tool. Please take the time to read the installation instructions for more information: http://wiki.linaro.org/Releases/MilestoneBuilds More Information on this development release as well as download and installation instructions can be found at: http://wiki.linaro.org/Releases/1011/ReleaseCandidate More information on Linaro in general and the 10.11 plans can be found at: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org * 10.11: http://wiki.linaro.org/Releases/1011 Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.freenode.net For any errata issues please see: http://wiki.linaro.org/Releases/1011/ReleaseCandidate#Issues Bug reports for this release should be filed in Launchpad against the individual packages that are affected, if a suitable package cannot be identified, feel free to assign them to: http://www.launchpad.net/linaro Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: lin...@uds: Where can I get the note of each Linaro sessions?
On 10/27/10 at 08:57pm, Jason Hui wrote: > Hi, Tom > > On Wed, Oct 27, 2010 at 8:40 PM, Tom Gall wrote: > > Hi Jason, > > > > I don't know that I would say gobby is ubuntu specific. All you need > > do is apt-get install gobby-0.5 and connect to gobby.ubuntu.com. > > Yes, I know. But you know that a lot of atendees not using ubuntu OS but MS. Gobby works on Linux, Mac and Windows. http://gobby.0x539.de/trac/ Regards, Jamie. > > > > Now you're quite right to lament that gobby has been a little less > > than stable at the conference. :-( When it is working tho I think > > you'll find it's trivial to get to the raw notes. > > Yes, currently it is not stable. > > > > > > Regards, > > Tom > > > > On Wed, Oct 27, 2010 at 7:22 AM, Jason Hui wrote: > >> Hi, Jamie > >> > >> On Wed, Oct 27, 2010 at 7:58 PM, Jamie Bennett > >> wrote: > >>> On 10/27/10 at 05:35pm, Jason Hui wrote: > >>>> As title. > >>> > >>> I'm not sure what you are asking. Are you asking about the schedule of > >>> the sessions themselves or the notes that come from the sessions? If its > >>> the former, the sessions schedule is at: > >>> > >>> http://uds.ubuntu.com > >>> > >>> If the latter then the notes from each sessions should be added to the > >>> blueprints specification page shortly after the sessions. You can also > >>> get the raw notes by installing gobby on your system and connecting to > >>> gobby.ubuntu.com. > >> > >> I mean what you said 'later case'. You know that a lot of attendee of > >> Linaro is not from cononical. > >> So, we want to see the session note in a more convenient way like wiki > >> page or something else. > >> > >>> > >>>> BR, > >>>> Jason Liu > >>> > >>> Regards, > >>> Jamie. > >>> > >> > >> ___ > >> linaro-dev mailing list > >> linaro-dev@lists.linaro.org > >> http://lists.linaro.org/mailman/listinfo/linaro-dev > >> > > ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: lin...@uds: Where can I get the note of each Linaro sessions?
On 10/27/10 at 05:35pm, Jason Hui wrote: > As title. I'm not sure what you are asking. Are you asking about the schedule of the sessions themselves or the notes that come from the sessions? If its the former, the sessions schedule is at: http://uds.ubuntu.com If the latter then the notes from each sessions should be added to the blueprints specification page shortly after the sessions. You can also get the raw notes by installing gobby on your system and connecting to gobby.ubuntu.com. > BR, > Jason Liu Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
maverick-proposed queue freeze
Hi, According to the Linaro release process [1] the maverick-proposed queue will be frozen tomorrow. After this date no uploads should be accepted for -proposed until the queue unfreezes on 8th November 2010 without consultation with the Linaro release team [2]. The total freeze time will be 12 days. The freeze process was agreed at the platform sprint in Prague and has benefits for both Ubuntu and Linaro. This period should be used to flush the -proposed queue, testing, verifying and promoting to maverick-updates what is currently there. If you have an update that really must be added to the queue in the next 12 days please email the team[3] for feedback. The Linaro Release Candidate images will be created on the 1st November and the images will be verified until Final Release on the 10th November. With your help we can get the -proposed queue flushed and produce rock-solid Linaro images, carrying the great work Ubuntu has done to more ARM based platforms. Regards, Jamie. -- Linaro Release Manager [1] http://wiki.linaro.org/Process/Cycle/PostUbuntuReleaseProcess [2] http://www.launchpad.net/~linaro-release [3] linaro-rele...@lists.launchpad.net ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Weekly Linaro image testing - part 4
Hi, We are nearly there ! Today marks the fourth installment of the weekly testing saga, the last before lin...@uds happens. The -proposed queue will be frozen on the 27th October to flush out any outstanding changes before the release candidate image is produced on November 1st. As always, If you have supported hardware and are willing to test the images, please make your way to: http://wiki.linaro.org/Releases/DailyBuilds for an explanation on how to test and submit your results to the QA tracker at: http://qatracker.linaro.org Happy Testing ! Regards Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Weekly Linaro image testing - part 3
Hi, Today marks the third week of "Weekly Linaro image testing" and as usual this is a call for help. If you have supported hardware and are willing to test the images, please make your way to: http://wiki.linaro.org/Releases/DailyBuilds for an explanation on how to test and submit your results to the QA tracker at: http://qatracker.linaro.org In the past week we have been squishing bugs and making the tools to create images better, hopefully you will see this in your testing. Another notable change is that these images enable the maverick-proposed repository, sucking in all the goodness that is coming in from the SRU process. Please try to verify if any SRU changes have adversely affected the images in any way. Happy Testing ! Regards, Jamie. -- Linaro Release Manager ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Problems with headless rootfs image lh build
On 14 Oct 2010, at 04:19, Shawn Guo wrote: > On Thu, Oct 14, 2010 at 4:58 AM, Michael Hudson > wrote: >> You can fix this by adding 'Defaults env_keep += "http_proxy"' to >> /etc/sudoers btw. >> > It works. Thanks, Michael. > > Hi Jamie, > > I'm running into the following problem with latest headless lh config. > Other repositories seem ok, and it only fails on maverick-proposed. > > Err http://ports.ubuntu.com maverick-proposed/main armel Packages > 404 Not Found > Err http://ports.ubuntu.com maverick-proposed/universe armel Packages > 404 Not Found > W: Failed to fetch > http://ports.ubuntu.com/dists/dists/maverick-proposed/main/binary-armel/Packages.gz > 404 Not Found > > W: Failed to fetch > http://ports.ubuntu.com/dists/dists/maverick-proposed/universe/binary-armel/Packages.gz > 404 Not Found > > Any suggestion? Thanks. It was a mis-configured apt line. Its now been fixed and is in the process of being re-built. Should be ready soon. > Regards, > Shawn Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Cortex A9 vexpress MMC I/O problems.
On 11 Oct 2010, at 23:08, Matt Waddel wrote: > Hi Jamie, > > On 10/11/2010 03:03 PM, Jamie Bennett wrote: >> On Mon, Oct 11, 2010 at 01:13:40PM +0100, Harry Liebel wrote: >>> I've had mixed results. When the box completes the boot the basic systems >>> seem to work ok (I can get an IP and poke the filesystem). It still takes >>> several minutes to get to a prompt as mentioned on the wiki page. >>> >>> It happens quite often that the box does not get to a prompt at all. It >>> fails to read the MMC properly. Below is two separate cases where reading >>> the partition table fails. In the first case it finds one partition and in >>> the second case it fails to find any partitions. The boot monitor has no >>> problem reading uboot, kernel or initrd from the MMC when writing to >>> internal FLASH. >>> >>> I've also tried a different SD card with similar results. Sometimes it >>> works fine and other times it reports I/O errors. I've tried the daily >>> builds for 6, 8 and 10 October. Is this a known issue? >> >> I can't fix your problem but for extra brownie points you could >> register this in launchpad as a bug and we can push for the right >> people to investigate. >> >> Please file a bug at: >> >> http://bugs.launchpad.net/linux-linaro >> >> (sounds like a kernel related issue) and we will take it from there :) > > We've already opened a bug on this issue: > > https://bugs.launchpad.net/ubuntu/+source/linux-linaro/+bug/632798 Great, thanks. > --Matt Regards, Jamie. >> >>> - >>> >>> mmc0: host does not support reading read-only switch. assuming write-enable. >>> mmc0: new SD card at address 8fe4 >>> mmcblk0: mmc0:8fe4 SD02G 1.84 GiB >>> mmcblk0: >>> Freeing init memory: 160K >>> p1ding, please wait... >>>p2 >>> udev[497]: starting version 163 >>> port 1 high speed >>> Begin: Loading essential drivers ... done. >>> Begin: Running /scripts/init-premount ... done. >>> Begin: Mounting root file system ... Begin: Running /scripts/local-top ... >>> done. >>> usb 1-1: new high speed USB device using isp1760 and address 2 >>> port 1 high speed >>> usb 1-1: New USB device found, idVendor=0471, idProduct=3526 >>> usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 >>> usb 1-1: Product: ISP1520 >>> usb 1-1: Manufacturer: Philips Semiconductors >>> mmcblk0: retrying using single block read >>> mmcblk0: error -5 transferring data, sector 0, nr 8, card status 0xb00 >>> hub 1-1:1.0: USB hub found >>> hub 1-1:1.0: 3 ports detected >>> end_request: I/O error, dev mmcblk0, sector 0 >>> Buffer I/O error on device mmcblk0, logical block 0 >>> >>> - >>> >>> mmc0: host does not support reading read-only switch. assuming write-enable. >>> mmc0: new SD card at address 8fe4 >>> mmcblk0: mmc0:8fe4 SD02G 1.84 GiB >>> mmcblk0: >>> TCP cubic registered >>> NET: Registered protocol family 10 >>> lo: Disabled Privacy Extensions >>> NET: Registered protocol family 17 >>> port 1 high speed >>> VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 0 >>> Registering SWP/SWPB emulation handler >>> rtc-pl031 mb:rtc: setting system clock to 2010-10-11 10:49:28 UTC >>> (1286794168) >>> usb 1-1: new high speed USB device using isp1760 and address 2 >>> Freeing init memory: 160K >>> port 1 high speed >>> mmcblk0: retrying using single block read >>> Loading, please wait... >>> usb 1-1: New USB device found, idVendor=0471, idProduct=3526 >>> usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 >>> udev[493]: starting version 163 >>> Begin: Loading eusb 1-1: Product: ISP1520 >>> mmcblk0: error -5 transferring data, sector 2, nr 6, card status 0x900 >>> end_request: I/O error, dev mmcblk0, sector 2 >>> ssential driversusb 1-1: Manufacturer: Philips Semiconductors >>> ... done. >>> Begin: Runnimmcblk0: error -5 transferring data, sector 3, nr 5, card >>> status 0x900 >>> ng /scripts/initend_request: I/O error, dev mmcblk0, sector 3 >>> -premount ... done. >>> Begin: Mounting root file system ... hub 1-1:1.0: USB hub found >>> hub 1-1:1.0: 3 ports detected >>> Begin: Running /scripts/local-tommcblk0: error -5 transferring data, sector >>> 5, nr
Re: Cortex A9 vexpress MMC I/O problems.
On Mon, Oct 11, 2010 at 01:13:40PM +0100, Harry Liebel wrote: > I've had mixed results. When the box completes the boot the basic systems > seem to work ok (I can get an IP and poke the filesystem). It still takes > several minutes to get to a prompt as mentioned on the wiki page. > > It happens quite often that the box does not get to a prompt at all. It fails > to read the MMC properly. Below is two separate cases where reading the > partition table fails. In the first case it finds one partition and in the > second case it fails to find any partitions. The boot monitor has no problem > reading uboot, kernel or initrd from the MMC when writing to internal FLASH. > > I've also tried a different SD card with similar results. Sometimes it works > fine and other times it reports I/O errors. I've tried the daily builds for > 6, 8 and 10 October. Is this a known issue? I can't fix your problem but for extra brownie points you could register this in launchpad as a bug and we can push for the right people to investigate. Please file a bug at: http://bugs.launchpad.net/linux-linaro (sounds like a kernel related issue) and we will take it from there :) Regards, Jamie. > - > > mmc0: host does not support reading read-only switch. assuming write-enable. > mmc0: new SD card at address 8fe4 > mmcblk0: mmc0:8fe4 SD02G 1.84 GiB > mmcblk0: > Freeing init memory: 160K > p1ding, please wait... > p2 > udev[497]: starting version 163 > port 1 high speed > Begin: Loading essential drivers ... done. > Begin: Running /scripts/init-premount ... done. > Begin: Mounting root file system ... Begin: Running /scripts/local-top ... > done. > usb 1-1: new high speed USB device using isp1760 and address 2 > port 1 high speed > usb 1-1: New USB device found, idVendor=0471, idProduct=3526 > usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 > usb 1-1: Product: ISP1520 > usb 1-1: Manufacturer: Philips Semiconductors > mmcblk0: retrying using single block read > mmcblk0: error -5 transferring data, sector 0, nr 8, card status 0xb00 > hub 1-1:1.0: USB hub found > hub 1-1:1.0: 3 ports detected > end_request: I/O error, dev mmcblk0, sector 0 > Buffer I/O error on device mmcblk0, logical block 0 > > - > > mmc0: host does not support reading read-only switch. assuming write-enable. > mmc0: new SD card at address 8fe4 > mmcblk0: mmc0:8fe4 SD02G 1.84 GiB > mmcblk0: > TCP cubic registered > NET: Registered protocol family 10 > lo: Disabled Privacy Extensions > NET: Registered protocol family 17 > port 1 high speed > VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 0 > Registering SWP/SWPB emulation handler > rtc-pl031 mb:rtc: setting system clock to 2010-10-11 10:49:28 UTC (1286794168) > usb 1-1: new high speed USB device using isp1760 and address 2 > Freeing init memory: 160K > port 1 high speed > mmcblk0: retrying using single block read > Loading, please wait... > usb 1-1: New USB device found, idVendor=0471, idProduct=3526 > usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 > udev[493]: starting version 163 > Begin: Loading eusb 1-1: Product: ISP1520 > mmcblk0: error -5 transferring data, sector 2, nr 6, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 2 > ssential driversusb 1-1: Manufacturer: Philips Semiconductors > ... done. > Begin: Runnimmcblk0: error -5 transferring data, sector 3, nr 5, card status > 0x900 > ng /scripts/initend_request: I/O error, dev mmcblk0, sector 3 > -premount ... done. > Begin: Mounting root file system ... hub 1-1:1.0: USB hub found > hub 1-1:1.0: 3 ports detected > Begin: Running /scripts/local-tommcblk0: error -5 transferring data, sector > 5, nr 3, card status 0xb00 > p ... done. > end_request: I/O error, dev mmcblk0, sector 5 > unable to read partition table > > - > > Thanks, > Harry > > > > -- IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > > ___ > linaro-dev mailing list > linaro-dev@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-dev ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Weekly Linaro image testing - part 2
Hi, Its that time again, today is Linaro image testing day. If you have supported hardware and are willing to test the images, please make your way to: http://wiki.linaro.org/Releases/DailyBuilds for an explanation on how to test and submit your results to the QA tracker at: http://qatracker.linaro.org This week we have completely removed all hardware specific pieces from the images at http://snapshots.linaro.org meaning that you will *need* to combine your chosen 'flavor' (headless, ALIP, netbook, plasma) with a hardware pack for you board. Thanks to your help last week we identified several bugs which have now been fixed and the images are getting closer to release standard. October 31st is our Release Candidate followed 10 days later by Final Release so ironing out the last remaining bugs is essential. Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Weekly Linaro image testing
On 6 Oct 2010, at 10:19, Shawn Guo wrote: > On Wed, Oct 6, 2010 at 3:04 PM, Jamie Bennett > wrote: >> If you read the guide, especially the hardware pack section, you should get >> an idea of what to do. You need to grab the headless image from >> snapshots.linaro.org and combine it with the imx hardware pack from >> jameswestby.net to produce an image for your board. The instructions on how >> to do this are on the page you mentioned. >> >> If you have any problems doing this please get back in contact and I'll help >> you through it. >> > Actually, I do not have problem to set up imx51 image for myself, > since I'm building rootfs from lh build with some changes on the > headless config. But I think a pre-built linaro-headless-imx51 should > be more straight-forward for people on imx51 to go, and better for > everyone testing imx51 on the same page. (Just a thought) Your right, it would be easier. The problem lies with the number of platforms we support and the number of 'flavours' we produce. Lets take a look. Currently we have support in some shape or form for: Beagle Board C3/4 IGEPv2 (slight customisation due to wireless driver) Beagle XM ARM Versatile Express Samsung Ux500 iMX51 We also have these flavours: Headless Netbook ALIP Plasma So if we were to release pre-built images for each board with each flavour, we would need to produce a staggering 24 image and this number is only going to rise. Having a tool to take one board specific part and combine it with one flavour is the most future-proof way of making images. > -- > Regards, > Shawn Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Weekly Linaro image testing
If you read the guide, especially the hardware pack section, you should get an idea of what to do. You need to grab the headless image from snapshots.linaro.org and combine it with the imx hardware pack from jameswestby.net to produce an image for your board. The instructions on how to do this are on the page you mentioned. If you have any problems doing this please get back in contact and I'll help you through it. Regards, Jamie On 6 Oct 2010 03:08, "Shawn Guo" wrote: > On Wed, Sep 29, 2010 at 3:53 PM, Jamie Bennett wrote: >> On Tue, Sep 28, 2010 at 06:50:03PM -0300, Christian Robottom Reis wrote: >>> On Tue, Sep 28, 2010 at 11:28:26AM +0100, Jamie Bennett wrote: >>> > OK, I put together: >>> > >>> > http://wiki.linaro.org/Process/ReleaseTesting >>> >>> Could we add some links to either that page or >>> https://wiki.linaro.org/Releases/1011/WeeklyTesting that explain how >>> testing is supposed to be carried out? >> >> I've added a few links to the Process/ReleaseTesting page which should >> help explaining how to test the images. >> > Great guide on https://wiki.linaro.org/Releases/DailyBuilds. But I > can not find image like linaro-headless-imx51 on > http://snapshots.linaro.org/10.11-daily/ to start testing on imx51. > > -- > Regards, > Shawn ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Proposal: linaro-testdrive script...
On Thu, Sep 30, 2010 at 09:42:27AM +0300, Amit Kucheria wrote: > The problem, IMO, is that these are scattered all over the place and > there are too many variations as we add new support. So the > documentation will always be out of date. > > Here is an example: > > I find out that snapshots.linaro.org provides dailies. But I want to > test the official beta. Where are the milestone releases? > Ok, lets go to wiki.linaro.org, click on Developer, scroll down to the > bottom, click on Beta milestone, find nothing there, come back, click > on Releases/1011/Beta >Scenario 1: only Beagleboard and Versatile express images listed > there. Hmm, i thought we supported IGEPv2 as well. Abort. (Obviously, > I don't read the NEWS section) >Scenario 2: I want to test my i.MX51 Babbage board, doesn't seem to > be supported easily. Abort (I read NEWS, but have no clue how to > modify the image) >Scenario 3: I want to test my beagleboard. Takes me to a completely > different website (releases.linaro.org) The solution to the use cases you describe above should now be: * Go to http://wiki.linaro.org * Click the Developers link * Read a couple of paragraphs, especially the "Obtaining and Testing Linaro Images" section. * Choose whether you want to test daily builds: * http://wiki.linaro.org/Releases/DailyBuilds * Milestone builds: * http://wiki.linaro.org/Releases/MilestoneBuilds * Or the official releases: * http://wiki.linaro.org/Releases/OfficalReleases These pages show (in graphical format) how to obtain, install and test the images. There are links off to the various pages that make sense where appropriate. We could extend the pages by having explicit sections on exactly how to install on a particular platform, but these sections would grow as more and more platforms are supported. I don't have a problem with that but I would hope that linaro-media-create can handle board specifics so we don't have to document them. Take a look. Is this any better? How can it be improved? > Regards, > Amit Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Proposal: linaro-testdrive script...
On Thu, Sep 30, 2010 at 09:42:27AM +0300, Amit Kucheria wrote: > On Thu, Sep 30, 2010 at 3:10 AM, Christian Robottom Reis > wrote: > > On Wed, Sep 29, 2010 at 11:07:27AM -0400, Scott Bambrough wrote: > >> This script should ask some basic questions and just do the right > >> thing. This should be a separate script from linaro-media-create. > > > I'm not sure this problem is actually that big. I mean, I expect as a > > community developer I'm either interested in the latest release, the > > latest development milestone, or a nightly, and those are just 3 links > > to directories -- you there choose the image type, and pull in the right > > hardware pack. > > The problem, IMO, is that these are scattered all over the place and > there are too many variations as we add new support. So the > documentation will always be out of date. [snip] You make some good points and if we are failing at documenting the procedure to actually install our images then thats bad and should be fixed ASAP. There are a couple of problems here: * We are adding support for more hardware and failing to keep up with documentation. * Some hardware may need special tweaks or installation instructions, this knowledge is usually with the engineer(s) who are enabling the board. It would be better if they contributed to the wiki pages as well outlining any extra steps needed, special test cases e.t.c. * Some boards are partially supported. You gave an example of iMX. This is a good example of a board that was requested to be supported, has pending changes in the media-create script and no one responsible for iMX has stepped up to document the test-cases or installation instructions yet. * You mentioned VExpress and OMAP as the only supported platforms really documented at the moment. That was our goal at the start of the cycle, to enable these two platforms. The fact that other platforms are starting to come online is great but again, the documentation is lagging behind. As a stop-gap I will go through the wiki pages today that deal with board support and installation. I'll produce a top-level page which will link off to the various platform specific instructions and documentation so at least we will have one link to navigate from. The discussion about whether we need a wrapper tool, which will need to be update for each board (very much like the wiki I suppose), is another topic. > Regards, > Amit Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Weekly Linaro image testing
On Tue, Sep 28, 2010 at 06:50:03PM -0300, Christian Robottom Reis wrote: > On Tue, Sep 28, 2010 at 11:28:26AM +0100, Jamie Bennett wrote: > > OK, I put together: > > > > http://wiki.linaro.org/Process/ReleaseTesting > > > > As we are starting to produce a number of images now, I've split them up > > into two categories, 'Primary' and 'Secondary'. Of course it would be > > nice if all images were tested but if we can get through the Primary > > ones each week that would be great. > > Awesome; I've added myself (and done some minor wiki reshuffling in the > process) and will be around this Thursday to sync up. > > Could we add some links to either that page or > https://wiki.linaro.org/Releases/1011/WeeklyTesting that explain how > testing is supposed to be carried out? I've added a few links to the Process/ReleaseTesting page which should help explaining how to test the images. > > As a side note, test cases still need to be written for a number of > > architectures and images. Currently we only have Headless OMAP and > > Headless Versatile Express. If you can contribute by adding a test case > > wiki page that would be awesome. > > Sure. Are those supposed to be kept under /Boards? Having links to those > is also a good idea. Currently they reside under Platform/QA/TestCases, whether this is the best place for them is another matter. One could argue that they belong under /Boards, /Bugs, /Process or where they are now, I'm not of a strong opinion for a particular one and I'm open to them being moved. > Christian Robottom Reis | [+55] 16 9112 6430 | http://launchpad.net/~kiko Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Weekly Linaro image testing
On Mon, Sep 27, 2010 at 07:12:28PM -0300, Christian Robottom Reis wrote: > Great initiative! > > On Mon, Sep 27, 2010 at 09:56:10PM +0100, Jamie Bennett wrote: > > * OMAP3 Headless > > * OMAP3 ALIP > > * OMAP3 Plasma Handset > > * OMAP3 EFL Netbook > > * Versatile Express Headless > > * UX500 Headless > > > > and in conjunction with a hardware pack from: > > > > http://jameswestby.net:8080/ > > > > * OMAP4 Headless > > * iMX51 Headless > > * OMAP3 X11 Base > > Does the OMAP3 version support the IGEPv2? > > Maybe you want to actually list the boards we intend to support, as > OMAP3 and iMX51 are available in a few different incarnations, and not > all of them are known to work, right? > > Could we register people that are willing to test in a wikipage and have > a synchronization meeting on #linaro at the end of the UTC day where we > tally up results? OK, I put together: http://wiki.linaro.org/Process/ReleaseTesting As we are starting to produce a number of images now, I've split them up into two categories, 'Primary' and 'Secondary'. Of course it would be nice if all images were tested but if we can get through the Primary ones each week that would be great. I encourage anyone who has hardware to join in testing this Thursday (and subsequent Thursdays) and add your name to the page listed above. As a side note, test cases still need to be written for a number of architectures and images. Currently we only have Headless OMAP and Headless Versatile Express. If you can contribute by adding a test case wiki page that would be awesome. > Christian Robottom Reis | [+55] 16 9112 6430 | http://launchpad.net/~kiko Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Weekly Linaro image testing
On 27 Sep 2010, at 23:12, Christian Robottom Reis wrote: > Great initiative! > > On Mon, Sep 27, 2010 at 09:56:10PM +0100, Jamie Bennett wrote: >> * OMAP3 Headless >> * OMAP3 ALIP >> * OMAP3 Plasma Handset >> * OMAP3 EFL Netbook >> * Versatile Express Headless >> * UX500 Headless >> >> and in conjunction with a hardware pack from: >> >> http://jameswestby.net:8080/ >> >> * OMAP4 Headless >> * iMX51 Headless >> * OMAP3 X11 Base > > Does the OMAP3 version support the IGEPv2? Yes. > Maybe you want to actually list the boards we intend to support, as > OMAP3 and iMX51 are available in a few different incarnations, and not > all of them are known to work, right? Good idea, I'll capture this information on a wiki page and post back the URL when it's done. > Could we register people that are willing to test in a wikipage and have > a synchronization meeting on #linaro at the end of the UTC day where we > tally up results? I'll add that to the wiki page too. > Christian Robottom Reis Regards, Jamie. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
