The Linaro project has a script that started as your setup_sdcard.sh
called linaro_media_create. As part of our release process we need to
have licenses for our files and since our script is based on yours,
your choice of license affects what choices we have. So long story
short, your file has no license included so care to add one or just
tell us what the license is so we can give our script a compatible if
not identical one?
I'd like to mirror and test the latest build of
but I have two issues with this:
* having some kind of direct link to the latest image so that I don't
need to parse the HTML to get the latest build; something like
/latest/ or /current/ would help here
* having a constant name for the data as to be rsync friendly; that is,
if the image is named linaro-m-headless-tar-20100923-0.tar.gz and
linaro-m-headless-tar-20100924-0.tar.gz the next day, it's hard to
convince rsync that the data file from the 24th can be mostly
inferred from the contents of the 23th; if it was named
linaro-m-headless-tar.tar.gz, I would have no problem
Where should I be filing bugs to track these requests, and who should I
harass to get these resolved? :-)
I finally got to this and wrote up a summary of the contents of the ST-E BSP
that we are mirroring on the Linaro git server:
I did not write up my recommendations of how to proceed, but it should give
an idea of the work in front of us/them.
Linus, if you see any significant omissions or mistakes, please correct me.
I've created a wiki page at https://wiki.linaro.org/LiveHelper/Hacking
to describe the various steps for building your own linaro images on
arm hardware using live helper. This also includes the steps to
modifying seeds to add/subtrack packages to suite your own goals
whatever they might be.
"We want great men who, when fortune frowns will not be discouraged."
- Colonel Henry Knox
w) tom.gall att linaro.org (Linaro User Platforms Team)
w) tom_gall att vnet.ibm.com
h) tom_gall att mac.com
We have only 43 (or 42 depending on your timezone) days until the Linaro final release  and
as we get closer, the need for more structured testing is essential. An idea that has been
incubating for some time is to have a weekly 'test day' where individuals can spend a couple
of hours downloading, installing and testing a Linaro image on their hardware. Which image(s)
you can test will obviously depend on the hardware available but currently we produce:
* OMAP3 Headless
* OMAP3 ALIP
* OMAP3 Plasma Handset
* OMAP3 EFL Netbook
* Versatile Express Headless
* UX500 Headless
and in conjunction with a hardware pack from:
* OMAP4 Headless
* iMX51 Headless
* OMAP3 X11 Base
Starting this Thursday (30th) I propose that each and every Thursday leading up to the final
release is a 'Linaro Image Test Day'. If you have any of this hardware available, please
spend a little time testing and reporting bugs. As an experiment, we will be setting up the
Linaro qatracker each Thursday morning, UTC, with the information for that days images. If
you find it useful, please report your testing results at:
For information on how to install the images on your hardware please take a look at:
Linaro Release Manager
This patch series has some clean up in OMAP3 sleep code.
Patches have been rebased to latest kevin's pm branch.
Vishwanath BS (2):
OMAP3 PM: move omap3 sleep to ddr
OMAP3 PM: sleep code clean up
arch/arm/mach-omap2/pm34xx.c | 9 +-
arch/arm/mach-omap2/sleep34xx.S | 377 ++++++++++++++---------------
arch/arm/plat-omap/include/plat/control.h | 2 +
3 files changed, 190 insertions(+), 198 deletions(-)
Official proposal for stakeholder process for the following idea.
Anyone can contribute.
Amit Kucheria has suggested we create a script called linaro-testdrive
to ease the knowledge required to download images and create bootable
In his opinion as we continuously add support for more platforms and
even more boards, it will become untenable to maintain the wiki pages
describing. Something similar to 'testdrive' for Ubuntu is required for
the next cycle.
This script should ask some basic questions and just do the right
thing. This should be a separate script from linaro-media-create.
Questions would be:
- What SoC?
- What board?
- What release (milestone)?
- Image type (headless, alip, qemu, etc.)
Each of these would be a multiple choice question. This should get rid
of the several levels of indirection required just to download all the
right components before trying to prepare an image.
The should be easily data driven. A data file could contain all of the
information required for the questions above. And with the right
packaging, upgrades to linaro-testdrive will continually add support
for new platforms and boards.
Amit Kucheria <amit.kucheria(a)linaro.org>
Scott Bambrough <scott.bambrough(a)linaro.org>
Time estimate: Likely two-three weeks in all.
Scott Bambrough <scott.bambrough(a)linaro.org>
Linaro Infrastructure Team Lead
Hello, I have been lurking here and on irc for a while and felt like it was
time to introduce myself.
I have a BB-C4 with all the trimmings and have been booting SD flash with
the daily builds and trying different configurations. I have also signed up
for weekly testing on the BB.
>From the wiki, it looks like I would be most interested in either the
Platform Engineering or Working Groups Engineering Units. Specifically, I'd
really like to start playing with sound/multimedia, but really anywhere that
I can help.
Is there any interest in a Middleware:Audio working group? Or does this fit
better with the Platform Engineering User Platforms group? I helped form the
Linux Foundation (OSDL at the time) Desktop Architects Sound and Multimedia
workgroup and could help with that.
Regards, Kurt Taylor (krtaylor irc)