Hi,
Beta Freeze [1] is now in effect. All uploads to the main archive must be approved by a member of the
release team so if changes are needed, please get them in as soon as possible. Uploads to other
archives do not need to be acknowledged by the release team and can continue to be pushed, with
an eye to quality and bug fixing, as normal. Once the Beta milestone [2] has been reached Feature
Freeze [3] comes back into effect.
We are now less than one week away from Beta Release. Please take the time between now and
then to test the images as much as possible to ensure that this release is as polished and stable as
possible. A Beta release candidate image will be selected soon following the documented steps [4]
and the release will be made next Thursday.
Regards,
Jamie.
--
Linaro Release Manager
[1] http://wiki.linaro.org/Releases/BetaFreeze
[2] http://wiki.linaro.org/Releases/BetaRelease
[3] http://wiki.linaro.org/Releases/FeatureFreeze
[4] http://wiki.linaro.org/Releases/MakeARelease
Hi there,
Power management WG is invistigating on a tool named PowerTOP, which can
spit out real time data on various aspects of a running system, in terms of
power related information.
However, occasionally some PowerTOP features need kernel patch. We'd like
users to be able to use these latest features without having to wait up to 3
months for Linus to make a release with the kernel portion -- as the
original patch developer(s) said.
There are totally 3 patches which I had already enclosed them in the
attachment. Except vfs.patch, the rest two are original and can be applied
on linaro kernel without any changes. vfs.patch is changed a little from
original one to adapt current linaro kernel.
Hope John would give it a thought to merge these patch in Linaro kernel.
Yong
Hi there. I got two new IGEPv2 boards over the weekend. They're now
happily running linux-linaro 2.6.35-1001.5.
I made the following changes:
* Statically link USB mass storage support so that I can use my USB
HDD as a rootfs
* Statically link in SMSC911x/921x support for future use as a NFS root
* Turn off CONFIG_FIXED_PHY to prevent a sysfs conflict with the
network card driver
* Strip back the kernel features to fit within the default 3 MB NAND partition
The NAND partitions are a bit messy. I know we want to be compatible,
but the small kernel partition and lack of a initrd partition are
messy.
-- Michael
Sorry - previous mail had an incorrect link.
The weekly report for the Linaro Infrastructure team may be found at:
Status report:https://wiki.linaro.org/Platform/Infrastructure/Status/2010-08-26
Burndown chart:http://people.canonical.com/~pitti/workitems/maverick/arm-infrastruct…
Progress:
* Finished up packaging branch for Abrek
* Started a branch to remove abrek list-results and replace it with
a 'results' command with various subcommands to operate on locally
stored results. Mostly complete, but a bit of cleanup to do still
* Got Ara to create an isotracker instance for us to use, and
qatracker.linaro.org now points to it
* Wrote up a set of tests to post on qatracker for the headless
image, sent to asac for review
* arm-m-derived-archive-rebuild: Made some progress on writing the
SQL queries to delete certain things.
* hardware-packs: improved the spec and asked questions about
parts that were under-specified.
* other: reviewed lots of branches, wrote a blog post, debugging
and fixing bzr-builddeb and bzr-builder issues that were blocking
colleagues, debugged a test issue.
* (arm-m-image-building-console)
* "Check dependencies for licensing concerns": DONE
* "Check if we're carrying patches to dependencies": DONE
* "Implement dependency management": Continued buildout spike, also
implemented a spike using virtualenv.
* "Resolve timezone patch to django issue": Made a branch to do this
with a monkey patch instead of textual patch.
* (arm-m-private-archive-hosting-infrastructure)
* "Choose which views we must provide for the basic services": DONE
* arm-m-private-archive-hosting-infrastructure
* Change to accept binary uploads: got it through review and just
need the reviewer to check some incremental changes before I land it.
* Custom Image/Icing folders that extend Launchpad's ones with the
vostok-specific resources: postponed as we have no use for it yet
Please let me know if you have any questions.
Kind Regards,
Ian
The weekly report for the Linaro Infrastructure team may be found at:
Status report:https://wiki.linaro.org/Platform/Infrastructure/Status/2010-08-12
Burndown chart:http://people.canonical.com/~pitti/workitems/maverick/arm-infrastruct…
Progress:
* Finished up packaging branch for Abrek
* Started a branch to remove abrek list-results and replace it with
a 'results' command with various subcommands to operate on locally
stored results. Mostly complete, but a bit of cleanup to do still
* Got Ara to create an isotracker instance for us to use, and
qatracker.linaro.org now points to it
* Wrote up a set of tests to post on qatracker for the headless
image, sent to asac for review
* arm-m-derived-archive-rebuild: Made some progress on writing the
SQL queries to delete certain things.
* hardware-packs: improved the spec and asked questions about
parts that were under-specified.
* other: reviewed lots of branches, wrote a blog post, debugging
and fixing bzr-builddeb and bzr-builder issues that were blocking
colleagues, debugged a test issue.
* (arm-m-image-building-console)
* "Check dependencies for licensing concerns": DONE
* "Check if we're carrying patches to dependencies": DONE
* "Implement dependency management": Continued buildout spike, also
implemented a spike using virtualenv.
* "Resolve timezone patch to django issue": Made a branch to do this
with a monkey patch instead of textual patch.
* (arm-m-private-archive-hosting-infrastructure)
* "Choose which views we must provide for the basic services": DONE
* arm-m-private-archive-hosting-infrastructure
* Change to accept binary uploads: got it through review and just
need the reviewer to check some incremental changes before I land it.
* Custom Image/Icing folders that extend Launchpad's ones with the
vostok-specific resources: postponed as we have no use for it yet
Please let me know if you have any questions.
Kind Regards,
Ian
Greetings,
Enclosed you'll find a link to the agenda, notes and actions from the
Linaro User Platforms Weekly Status meeting dated 8/25 held in
#linaro-meeting at 13:00 UTC.
https://wiki.linaro.org/Platform/UserPlatforms/WeeklyStatus/2010-08-25
Regards,
Tom (tgall_foo)
User Platforms Team
Hello,
I have another question related to cross compilation...
I am still trying to setup a functional cross compilation environment
for our packages. I want to be able to build without xdeb, using debuild
command (this is mainly because we use other tools such as
git-buildpackage).
When I build a package which has dependency on another .so file, my
./configure script fails, pkg-config complains that it cannot find my
package config file (which is available in
/usr/arm-linux-gnueabi/lib/pkgconfig.
If I set PKG_CONFIG_LIBDIR to /usr/arm-linux-gnueabi/lib/pkgconfig, then
my build is fine, e.g. debuild
-ePKG_CONFIG_LIBDIR=/usr/arm-linux-gnueabi/lib/pkgconfig -b -aarmel -us -uc.
Is that expected? I was looking around in xdeb, and I don't find where
this is being done, and I am sure it would be needed too since it ends
up calling debuild... In this process I noticed that xdeb is also
passing /etc/dpkg-cross/cross-config.armel to debuild. Should I do this to?
I would appreciate any feedback on this.
thanks,
nicolas
note: I am using a maverick chroot, and Marcin's cross compiler.