As discussed below here's a page for listing your PPA for others to use.
https://wiki.linaro.org/DevelopersPPAs
Regards
Peter Pearse
---------- Forwarded message ----------
From: Alexandros Frantzis <alexandros.frantzis(a)linaro.org>
Date: Thu, Dec 2, 2010 at 11:17 AM
Subject: Re: Fwd: Tracking linaro PPAs
To: Peter Pearse <peter.pearse(a)linaro.org>
On Thu, Dec 02, 2010 at 09:58:50AM +0000, Peter Pearse wrote:
> Alexandros - did anything come of this?
>
> If not I'd be glad to start a wiki page to list usefule PPAs......
>
> Peter
>
>
Hi Peter,
although we (User Platforms) have created a team PPA, I am not sure if:
a. other teams have a similar policy
b. team members actually post everything in that PPA
So, I think the wiki page would be useful. I imagine such a page would
also assist in giving us a better overview of what is going on and
therefore help us to organize the PPAs better :)
Thanks,
Alexandros
All,
The weekly report for the Linaro Infrastructure team may be found at:-
Status report: https://wiki.linaro.org/Platform/Infrastructure/Status/2010-12-02
Burndown chart: This link is awaiting the production of new burndown charts.
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 8 work items in progress (8 last report), and 11 work items to undertake (11 last report). These are to be moved into the natty cycle if still required.
* arm-m-validation-dashboard; 0 work items completed since last report; 3 in progress; 7 to do
* arm-m-image-building-console; 0 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
In the natty cycle, the following lists the current active Blueprints, or Blueprints planned and not started. Currently there are 4 active Blueprints (4 from the last report), which are showing that there are 8 work items in progress (7 last report), 41 work items to undertake (46 last report), 2 work items postponed (0 last report) and 8 work items added (all items added last report).
* other-linaro-n-improve-linaro-media-create: 2 work items completed; 3 work items in progress; 8 work items to do; 2 work items added.
* other-linaro-n-test-result-display-in-launch-control: 8 work item completed; 1 work item in progress; 10 work items to do; 4 work items added
* other-linaro-n-patch-tracking: 0 work item completed; 2 work items in progress; 9 work items to do
* other-linaro-n-image-building: 2 work items in progress; 5 work items to do; 2 work items postponed; 2 work items added
* other-linaro-n-continuous-integration: Not started - awaiting a Hudson build server (RT#42278).
* other-linaro-n-package-development-tools: Not Started; 9 work items to do
Specifics accomplished this week include:-
* Offspring (which used to be known as LexBuilder) has now been open sourced.
* other-linaro-n-image-building: progress being made on hwpacks
* ImproveLinaroMediaCreate: the ports of "ensure_command" and "unpack_binary_tarball" to Python have been completed.
Please let me know if you have any comments or questions.
Kind Regards,
Ian
Here's what the toolchain group has been doing:
* Atomic memory operations are finishing up. Preparing a coverage
report of operations vs data type for GCC and llvm
* IFUNC support is almost complete
* Discussed how to be a good community member. Will start reviewing
patches, sending test results, participating on the mailing list, and
look at making the tree more readily available
* Discussed QEMU Users Conference. Decided to participate but not
present due to no compelling topics
* Discussed bugs, blueprints and visibility. Group will start
properly updating bug status, and will at least weekly update
blueprint status
* Would like to acquire Snapdragon based development boards to
monitor how well our A9 focused work works on Qualcomm parts
Weekly meeting minutes are at:
https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2010-11-29
Standup minutes are at:
https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2010-12-01
Audio is here:
http://tc.seabright.co.nz/toolchainwg/
-- Michael
I've written up my notes on network booting the sevenx OMAP3
StageCoach board here:
https://wiki.linaro.org/MichaelHope/Sandbox/StagecoachBringup
I'm not currently using the Linaro kernel as either need a kernel with
USB Ethernet and NFS root built in, or a way of combining uImage and
uInitrd into one. Perhaps next week...
-- Michael
I've now got a Gumstix Stagecoach with six NFS root OMAP3-based boards
up and running in my office. That brings the grand total up to ten
Cortex-A8 based boards on the local network.
Eventually these or something similar will go up into the data centre
but, until then, I might as well put them to use. Any suggestions?
If you'd like access then drop me a line.
-- Michael
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
Currently cpufreq transition latency value does not really reflect the actual
OMAP OPP transition delay. This patch has the actual latency value.
I did profile the DVFS latency on OMAP3430, OMAP3630 and OMAP4 for worstcase(MPU and Core together) and found that in none of these platforms, transiton value
goes beyong 10ms. Added a buffer of 20ms to avoid too frequent ondemand timer
expiry.
With this change, performance of ondemand governor is improved when tested
using cpufreqbench tool. Without this patch, cpufreq-bench reported ondemand
performance as 40% of performance governor, and with this patch it's around 70%
(using below procedure).
cpufreq-bench:
http://lwn.net/Articles/339862/http://ftp.riken.go.jp/archives/Linux/suse/people/ckornacker/cpufreq-bench/
Command used for performance testing:
cpufreq-bench -l 50000 -s 100000 -x 50000 -y 100000 -g ondemand -r 5 -n 5 -v
Signed-off-by: Vishwanath BS <vishwanath.bs(a)ti.com>
---
arch/arm/plat-omap/cpu-omap.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
mode change 100644 => 100755 arch/arm/plat-omap/cpu-omap.c
diff --git a/arch/arm/plat-omap/cpu-omap.c b/arch/arm/plat-omap/cpu-omap.c
old mode 100644
new mode 100755
index c47faf8..d3fc423
--- a/arch/arm/plat-omap/cpu-omap.c
+++ b/arch/arm/plat-omap/cpu-omap.c
@@ -158,8 +158,8 @@ static int __init omap_cpu_init(struct cpufreq_policy *policy)
policy->max = policy->cpuinfo.max_freq;
policy->cur = omap_getspeed(0);
- /* FIXME: what's the actual transition time? */
- policy->cpuinfo.transition_latency = 300 * 1000;
+ /* Program the actual transition time for worstcase */
+ policy->cpuinfo.transition_latency = 30 * 1000;
return 0;
}
--
1.7.0.4